Skip to content

providers-claude.md

Latest commit

 

History

History
244 lines (165 loc) · 7.8 KB

providers-claude.md

File metadata and controls

244 lines (165 loc) · 7.8 KB
Raw

Claude

This guide is for people who want to use more than one Claude setup in T3 Code. For Codex, see Codex. For first-time setup, see Install T3 Code.

Common reasons:

  • use separate work and personal Claude accounts
  • try a different Claude Code configuration without disturbing your main setup
  • run Claude through a router such as Claude Code Router
  • use external providers exposed through a Claude-compatible workflow

I Only Use One Claude Account

Use the default provider.

Log in with Claude Code normally:

claude auth login

You can also add another Claude account from Settings → Providers: Add provider, pick Claude, then sign in from the card (browser, device code, or paste-back). ChatGPT/Codex works the same way, and you can store an API key on a second instance instead of a subscription login.

In T3 Code Settings, your Claude provider can stay like this:

Display name: Claude
Binary path: claude
CLAUDE_CONFIG_DIR path: empty

An empty CLAUDE_CONFIG_DIR path means T3 Code uses Claude Code's normal config directory.

When you set this field, T3 Code points Claude Code at that directory with the CLAUDE_CONFIG_DIR environment variable. It does not change HOME, so your system keychain and the rest of your environment stay as they are.

Where Claude Skills Are Loaded

T3 Code looks for Claude skills in the Claude config directory's skills folder, then <workspace>/.agents/skills, then <workspace>/.claude/skills.

If the same skill name exists in more than one folder, the later folder wins.

The workspace is the folder the thread runs in: its worktree when it has one, and the project folder when it does not. The / and $ menus list the commands and the skills of that workspace, so two projects show different entries.

I Want Work And Personal Claude Accounts

Use a different Claude config directory for each account.

Example:

default config dir           work account
~/.claude_personal_home      personal account

Set Up The First Account

Log in normally:

claude auth login

In T3 Code Settings:

Display name: Claude Work
Binary path: claude
CLAUDE_CONFIG_DIR path: empty

Set Up The Second Account

Log in with a separate config directory:

mkdir -p ~/.claude_personal_home
CLAUDE_CONFIG_DIR=~/.claude_personal_home claude auth login

Use CLAUDE_CONFIG_DIR, not HOME. Setting HOME writes the login to ~/.claude_personal_home/.claude, which is not where T3 Code looks.

Then add another Claude provider in T3 Code:

Display name: Claude Personal
Binary path: claude
CLAUDE_CONFIG_DIR path: ~/.claude_personal_home

Use the email shown in Settings to confirm each provider is using the intended account. Emails are blurred by default; click the blurred email to reveal it.

Can I Switch Claude Accounts In An Existing Thread?

Usually, no.

T3 Code only offers Claude providers that use the same config directory for an existing thread. A different config directory is treated as a different Claude environment.

This is different from the recommended Codex setup. Claude Code keeps account and local state across multiple files under its config directory, so T3 Code keeps separate config directories isolated instead of trying to share part of the state.

Why Did Claude Stop Halfway Through A Turn?

If your Claude subscription runs out of usage mid-turn, the thread shows a row like:

Claude usage limit reached. This turn is paused until the 5-hour limit resets at Feb 3, 3:00 PM PST.

Claude Code holds the turn until that window reopens, so the thread keeps showing as working. You can wait for the reset, or stop the turn and pick the work back up later.

I Want To Use OpenRouter

Use this when you want Claude Code to talk to OpenRouter directly, without running a local router. This is the simplest external-provider setup.

OpenRouter provides a Claude Code integration through Claude's Anthropic-compatible environment variables.

Configure A Claude OpenRouter Provider

Add or edit a Claude provider in T3 Code Settings:

Display name: Claude OpenRouter
Binary path: claude
CLAUDE_CONFIG_DIR path: ~/.claude_openrouter_home

In that provider's Environment variables section, add:

ANTHROPIC_BASE_URL   https://openrouter.ai/api
ANTHROPIC_AUTH_TOKEN sk-or-...                Sensitive
ANTHROPIC_API_KEY                              Empty value

Mark ANTHROPIC_AUTH_TOKEN as sensitive. T3 Code stores the value as a server secret and does not send it back to the app after saving.

If you want this setup isolated from your normal Claude account, create that home first:

mkdir -p ~/.claude_openrouter_home

If you previously used the same Claude home with a normal Anthropic login, run /logout in a Claude Code session for that home before using OpenRouter. Otherwise Claude Code may keep using cached Anthropic credentials instead of the OpenRouter token.

Pick OpenRouter Models

OpenRouter can route Claude Code's default model roles to OpenRouter model IDs.

Example:

ANTHROPIC_DEFAULT_OPUS_MODEL    anthropic/claude-opus-4.6
ANTHROPIC_DEFAULT_SONNET_MODEL  anthropic/claude-sonnet-4.6
ANTHROPIC_DEFAULT_HAIKU_MODEL   anthropic/claude-haiku-4.5
CLAUDE_CODE_SUBAGENT_MODEL      anthropic/claude-sonnet-4.6

Add those to the same provider's Environment variables section if you want stable model choices.

Verify OpenRouter Is Being Used

Open a Claude session and run:

/status

You should see the Anthropic base URL set to:

https://openrouter.ai/api

You can also check the OpenRouter activity dashboard for requests from your API key.

Common OpenRouter Mistakes

  • Use https://openrouter.ai/api, not https://openrouter.ai/api/v1, for Claude Code.
  • Set ANTHROPIC_AUTH_TOKEN to your OpenRouter API key.
  • Set ANTHROPIC_API_KEY to an empty string so Claude Code does not try to use an Anthropic login.
  • Put these variables on the Claude provider instance, not in global shell startup files.

OpenRouter's setup can change over time. Use its upstream Claude Code guide for the current details: https://openrouter.ai/docs/guides/guides/claude-code-integration.

I Want To Use Claude Code Router

Claude Code Router is useful when you want a local routing layer with more control than a direct OpenRouter setup.

T3 Code does not need a special Claude Code Router provider. Treat the router as a Claude environment: give a Claude provider its own CLAUDE_CONFIG_DIR path, and put whatever variables the router tells you to export into that provider's Environment variables section. Mark tokens and API keys as sensitive.

Display name: Claude Router
Binary path: claude
CLAUDE_CONFIG_DIR path: ~/.claude_router_home

Follow the upstream project's README for the router's own install, startup, and configuration steps: https://github.com/musistudio/claude-code-router.

I Want Different Claude Settings, Not A Different Account

Create another Claude provider with the same account if you want a named preset.

Examples:

  • "Claude Default"
  • "Claude Router"
  • "Claude Experimental"

If the preset needs different Claude files, give it a different CLAUDE_CONFIG_DIR path. If it needs different API keys, base URLs, or router settings, use Environment variables.

Do not put environment variable assignments in Launch arguments.

Full Access When Bypass Permissions Are Locked

Some Claude setups, including organization policy, forbid bypass-permissions mode. If you pick Full access there, T3 Code keeps the thread on Full access but starts Claude in Auto so the session can run. If Auto is also locked — or you pick Auto while Auto is locked — the session starts in Supervised instead. Pick the composer mode that matches what Claude will enforce if you want the label to stay in sync.