Run Claude Code through one gateway

How it works

openllm claude launches the real Claude Code binary with run-local flags (--settings and --mcp-config). Nothing is written to ~/.claude, and your login, history and settings stay where they are.

• ▸Your Claude subscription is used by the official Claude CLI on your machine
• ▸API-key models from other providers are available as fallback hops or by alias
• ▸Exit and run claude directly any time — nothing to uninstall

Fallback chains when a model is rate-limited

Define an ordered chain per model alias. When a hop returns a rate limit, an overload or a provider error, the request moves to the next hop instead of failing your session.

• ▸Chains are configured once and shared by every client and device
• ▸Each hop resolves its own model settings, so a fallback never inherits the wrong parameters
• ▸Every hop that ran is visible in your request history

Your subscriptions stay on your machine

Subscription providers run through the local OpenLLM daemon, which delegates to the vendor's official CLI and its own login. The hosted gateway never holds a subscription credential.

Code search and memory over MCP

The same binary ships one MCP server: semantic search over your indexed repositories and documentation, plus memory that persists across sessions and clients.

See where the tokens go

Requests, tokens, latency and API-equivalent cost per model and provider, with charts you can export or share.

Provider keys encrypted at rest

API keys are encrypted in your browser with AES-256-GCM under a key derived from your recovery phrase, and stored as ciphertext. They are decrypted in memory only while a request is being served, then discarded. Subscription credentials never reach the hosted service.