The reviewed setup runbook supports Cursor, Codex, Claude Code, OpenCode, Hermes, and Pi. Your agent inspects the host first, proposes the host-specific skill directory, asks before writing, and then verifies that the host discovers visualize.
Use the installation guide for the one-line setup request. The machine-readable setup runbook owns the exact host paths and approval rules so they do not drift between prose pages.
Image routes depend on the active host
The deterministic fake route is characterized for contract testing, not creative output. Claude Code's configured general Codex MCP session bridge and an authenticated Codex CLI bridge are characterized for creative output. The explicitly selected OpenAI and Gemini API adapters are also characterized; runtime availability still depends on the configured provider account and model access, not key presence alone.
Native Codex and Antigravity routes, other MCP transports, and the Antigravity CLI bridge remain candidate interfaces awaiting file-producing acceptance. An installed executable, callable-looking tool, or configured key does not release one of those routes.
Every route still requires explicit availability and selection checks. Native and bridge routes may consume host-plan allowance; API use may incur charges under the selected provider account. A generated file is not complete until the active agent opens and visually inspects it.