Connect coding tools
Launch qualified Codex or Claude Code builds, or install persistent RouteKit client settings.
Connect coding tools
Use this guide after RouteKit has at least one working route. Verify that first:
routekit status
routekit models listUse a qualified client build
The supported builds are Codex CLI 0.146.0 and Claude Code 2.1.216 or
2.1.220. Other versions are unqualified, not necessarily incompatible, and
RouteKit does not reject them at runtime. See
client compatibility for evidence and
the requalification policy.
Choose an integration
Launch Codex with an explicit RouteKit model:
routekit codex openai/gpt-5.5Native arguments belong after --:
routekit codex openai/gpt-5.5 -- --full-autoOmit the model to use the configured default when the client supports it.
--effort <id> selects a discovered reasoning effort, and --cwd <dir> sets
the tool working directory.
Use another gateway
The launch commands accept --gateway-url, --auth-token or
--auth-token-env, and --cwd. Authenticated non-loopback gateways must use
HTTPS. Before spawning Codex or Claude Code, RouteKit confirms that the native
binary is on PATH.
Install persistent configuration
Use native-client installation when you want the client to retain a RouteKit
profile or model picker without launching it through routekit each time:
routekit codex install
routekit claude installCodex gets one additive routekit profile. Start it with
codex --profile routekit and choose from the RouteKit-backed model picker.
Claude Code gets RouteKit-owned gateway settings and native availableModels
entries. Existing configuration, MCPs, skills, plugins, and history remain
owned by the native client.
Each install issues a dedicated gateway token and stores it in macOS Keychain,
or in a private 0600 RouteKit secret file on other platforms. Codex and Claude
retrieve it on demand through their native credential helper settings, so
terminal, IDE, and GUI launches need no shell changes. Reinstalling the same
target keeps its token; use --rotate-token to replace it. Use --shell only
as a compatibility fallback for an older client.
Claude's --bare mode intentionally ignores normal user settings, including
apiKeyHelper; use a normal launch or pass its settings file explicitly.
Use externally managed credentials
Pass --no-token when another environment owns credential injection:
routekit codex install --no-token
routekit claude install --no-tokenThis writes only RouteKit-owned client configuration. It does not issue,
register, change, or revoke a gateway token. Supply ROUTEKIT_GATEWAY_TOKEN
for Codex or ANTHROPIC_AUTH_TOKEN for Claude in the client environment.
--no-token cannot be combined with --rotate-token.
For a configured integration that needs explicit shell exports, run:
routekit token shell --tool codex
routekit token shell --tool claudeRemove the integration
routekit codex uninstall
routekit claude uninstallUninstall removes only RouteKit-owned settings and revokes the tracked dedicated token.
Verify and continue
Open the client's model picker or send a small prompt, then inspect the returned
x-routekit-model-call-id with routekit calls inspect <call-id>.