Is T3Code compatible with OpenRouter?

[Giovarco]

Hi! I'm new here, I wanted to try T3Code with OpenRouter, but I couldn't find out if it's compatible with it.

[LVLAaron]

Not that I can tell. You can use openrouter, with opencode, and T3 code can connect to opencode as a provider, but that seems to be broken right now. About to post about this

[Giovarco]

Thanks for the feedback! So probably I won't use T3C any time soon. It's really a shame.

I'm using ZooCode right now which is good enough, but hopefully I can try T3C some time soon and maybe contribute to T3C at some point

[Erfouni]

Yes, through the Claude provider. T3 Code doesn't call OpenRouter itself; it drives Claude Code, and Claude Code can use OpenRouter as its API endpoint. T3 Code lets you set environment variables per provider instance, so it can all be done in the app:

1. Settings → Providers → Add provider instance, pick Claude, and give it a label such as OpenRouter. Your normal Claude instance stays as it is.

2. In the new instance's Environment section, add:

   Variable	Value
   ANTHROPIC_BASE_URL	https://openrouter.ai/api
   ANTHROPIC_AUTH_TOKEN	your OpenRouter key (leave this one Sensitive)
   ANTHROPIC_API_KEY	(empty — it has to be set, but blank)
   CLAUDE_CONFIG_DIR	~/.claude-openrouter

   The first three are exactly what OpenRouter's Claude Code guide prescribes. CLAUDE_CONFIG_DIR is optional, but I'd set it if you're also logged in to Claude Code with an Anthropic account. That guide warns that a cached Anthropic login conflicts with the gateway token (you'd otherwise have to /logout), and a separate config dir keeps this instance clean without touching your normal login. T3 Code expands the ~ for this variable.

3. Pick the model. Under the instance's Models section you can add a custom model with an OpenRouter slug (e.g. ~anthropic/claude-sonnet-latest, or anything from openrouter.ai/models). T3 Code passes slugs it doesn't know to Claude Code unchanged. You can also add ANTHROPIC_DEFAULT_SONNET_MODEL / _OPUS_ / _HAIKU_ in the same Environment section. Claude Code uses those for its own background and sub-agent calls.

When it's working, the instance should show as ready with "Claude API Key" as the auth method (that's how T3 Code labels an ANTHROPIC_AUTH_TOKEN login), and the requests appear in your OpenRouter activity page.

One caveat from OpenRouter's own docs: Claude Code through OpenRouter is only guaranteed with Anthropic models served by Anthropic. Non-Anthropic models can work, but tool use may misbehave, since Claude Code is tuned for Claude.

[Giovarco]

Yes, through the Claude provider. T3 Code doesn't call OpenRouter itself; it drives Claude Code, and Claude Code can use OpenRouter as its API endpoint. T3 Code lets you set environment variables per provider instance, so it can all be done in the app:

1. Settings → Providers → Add provider instance, pick Claude, and give it a label such as OpenRouter. Your normal Claude instance stays as it is.

2. In the new instance's Environment section, add:

   Variable
   Value

   ANTHROPIC_BASE_URL
https://openrouter.ai/api

   ANTHROPIC_AUTH_TOKEN
   your OpenRouter key (leave this one Sensitive)

   ANTHROPIC_API_KEY
   (empty — it has to be set, but blank)

   CLAUDE_CONFIG_DIR
~/.claude-openrouter

   The first three are exactly what OpenRouter's Claude Code guide prescribes. CLAUDE_CONFIG_DIR is optional, but I'd set it if you're also logged in to Claude Code with an Anthropic account. That guide warns that a cached Anthropic login conflicts with the gateway token (you'd otherwise have to /logout), and a separate config dir keeps this instance clean without touching your normal login. T3 Code expands the ~ for this variable.

3. Pick the model. Under the instance's Models section you can add a custom model with an OpenRouter slug (e.g. ~anthropic/claude-sonnet-latest, or anything from openrouter.ai/models). T3 Code passes slugs it doesn't know to Claude Code unchanged. You can also add ANTHROPIC_DEFAULT_SONNET_MODEL / _OPUS_ / _HAIKU_ in the same Environment section. Claude Code uses those for its own background and sub-agent calls.

When it's working, the instance should show as ready with "Claude API Key" as the auth method (that's how T3 Code labels an ANTHROPIC_AUTH_TOKEN login), and the requests appear in your OpenRouter activity page.

One caveat from OpenRouter's own docs: Claude Code through OpenRouter is only guaranteed with Anthropic models served by Anthropic. Non-Anthropic models can work, but tool use may misbehave, since Claude Code is tuned for Claude.

Many thanks! I'll try that out.

I could set Codex to work with OpenRouter too yesterday. Is it a similar process with OpenAI Codex?

By the way, I cannot be but confused about all these names: Claude-code, Codex, OpenCode... I thought that Codex was made by Althropics but it's made by OpenAI. I must not be the only one feeling this way... Codex and Claude-code look similar too. Do they use the same base implementation or is it convergence design?

[Erfouni]

Yes, it's the same idea for Codex. T3 Code starts the Codex CLI with the provider instance's environment, and Codex reads its settings from CODEX_HOME (default ~/.codex). So the OpenRouter setup you already have carries over:

• If it lives in ~/.codex/config.toml, the regular Codex instance in T3 Code uses it too. The key has to be visible to T3 Code as well, so add the variable named in env_key (e.g. OPENROUTER_API_KEY) to that instance's Environment section.
• To keep your normal Codex untouched, copy that config.toml into a separate folder such as ~/.codex-openrouter/. Then add a second Codex provider instance and set CODEX_HOME=~/.codex-openrouter plus the key variable in its Environment. Each instance runs its own Codex process with its own CODEX_HOME, and T3 Code expands the ~.
• Add the OpenRouter model id as a custom model on that instance, the same way as with Claude.

On the names: they're separate tools from different companies, not one codebase. Claude Code is Anthropic's, Codex is OpenAI's (its CLI is open source), and OpenCode is an independent open-source agent that isn't tied to one model vendor. They look alike because they converged on the same design: a terminal agent that reads files, runs commands, edits code and speaks MCP. T3 Code then sits on top of all of them as one GUI.