Claude Code

The easy way: omnizen launch claude

The Omnizen CLI installs Claude Code (if you don't already have it), wires up the right environment, and runs it - without touching your existing ~/.claude/settings.json or your default Anthropic account. claude on its own keeps using your normal Claude.ai login; omnizen launch claude uses Omnizen.

npm install -g omnizen-cli      # one-time
omnizen login                   # browser-based, no copy/paste
omnizen launch claude           # opens Claude Code, routed through Omnizen

That's it. Claude Code's /model command picks between the Kimi tiers we map to Opus / Sonnet / Haiku slots - see the models page for the current mapping.

Manual setup (if you'd rather not use the CLI)

If you want to run Claude Code through Omnizen without our wrapper - e.g. in CI, in a Docker image, or because you've already got it set up - set two environment variables.

export ANTHROPIC_BASE_URL="https://api.omnizen.ai"
export ANTHROPIC_AUTH_TOKEN="sk-omni-…"

Or, if you'd rather keep it project-local, drop them into a per-project .envrc or ~/.claude/settings.json:

{
  "env": {
    "ANTHROPIC_BASE_URL": "https://api.omnizen.ai",
    "ANTHROPIC_AUTH_TOKEN": "sk-omni-…"
  }
}

Get your sk-omni-… key from your dashboard → API keys.

Heads-up: if you have an Anthropic OAuth login active (~/.claude/.credentials.json), Claude Code prefers that over the env vars. Run claude /logout once before the first Omnizen-routed session to drop the OAuth token.

Tips

• Your default claude stays untouched. omnizen launch claude spawns Claude Code with an isolated config directory, so plain claude keeps using your normal Anthropic account.
• Rotate your key any time from the dashboard - old keys keep working until you delete them.
• Plan-mode prompts still work - Claude Code's tool surface doesn't change, just the backend.