{ "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "How does Keyway work?", "acceptedAnswer": { "@type": "Answer", "text": "Keyway runs a local proxy on 127.0.0.1:9527. Requests from connected CLIs are forwarded according to your default provider, routing rules and failover settings. Request logs show the actual destination." } }, { "@type": "Question", "name": "How are my API keys stored?", "acceptedAnswer": { "@type": "Answer", "text": "API keys live in a local SQLCipher-encrypted database whose master key is held in the system keychain. Exported provider configurations exclude API keys." } }, { "@type": "Question", "name": "Which AI CLIs are supported?", "acceptedAnswer": { "@type": "Answer", "text": "Keyway offers 9 CLI groups covering the Anthropic, OpenAI and Gemini protocols. Claude Code, Codex CLI, Gemini CLI, OpenCode and OpenClaw support automatic takeover; other CLIs can be connected manually." } }, { "@type": "Question", "name": "Do I need to restart sessions after switching providers?", "acceptedAnswer": { "@type": "Answer", "text": "Sessions already routed through the proxy do not need a restart after switching the default provider. First-time Codex takeover requires one new session; routing rules still take priority." } }, { "@type": "Question", "name": "Is Keyway free?", "acceptedAnswer": { "@type": "Answer", "text": "Keyway is completely free and open source under the MIT license. You only pay the model providers you use." } } ] } ne/app-light.png" />
The local gateway for AI CLIs. Manage providers, routing and failover in one place. Trace actual destinations in request logs.
Latest stable release v0.2.14 · macOS / Windows / Linux
Default providers, connection status and actual requests — clearly distinguished.
Sessions already using the proxy need no restart when changing the default provider. New requests follow the updated configuration; in-flight requests do not migrate.
API keys live in a local SQLCipher-encrypted database; its master key is held in the system keychain. Provider configuration exports exclude API keys.
Check providers, models, status codes and errors in request logs. When routing or failover changes the destination, you have more than a guess.
Local-first · not a hosted relay
Keyway keeps the control plane on your machine: it does not host your API keys, sell model access, or present the default provider as the actual destination.
Connect to the proxy first, then switch your default provider. Start a new Codex session after first-time takeover; later switches need no restart.
From key safety to request observability, Keyway is the local gateway for your AI CLIs.
Configure and enable a backup chain to try the next candidate after retryable upstream failures. Recovery is not guaranteed once a streaming response has begun.
Route specific models to specific providers: e.g. claude-* to official, deepseek-* to a relay — preview the path, then dispatch by model name.
The last 100 requests, item by item: actual provider, model, tokens in/out, status code and latency. Debugging at a glance.
Token usage and request success rate aggregated by CLI and by provider. Who's stable, who's costly — let data decide.
Work / personal / testing — snapshot provider sets, save and switch anytime without interference.
Export provider configs to JSON with one click (keys excluded). Moving machines or sharing presets is easy. Imports from the 5 CLIs with automatic takeover.
API keys are stored in a local SQLCipher-encrypted database; its master key is held in the system keychain. Provider configuration exports exclude API keys.
One-click latency and reachability test per provider, before you switch.
A three-step wizard: pick CLIs, add providers, take over in one click. Lives in the menu bar for instant switching.
Or import from existing CLI configs. GLM, Kimi, official, any relay.
Originals backed up, restorable anytime.
Send a new request, then check its actual provider and response status in the logs.
Keyway runs a local proxy (127.0.0.1:9527). Connected CLI requests follow your default provider, routing rules and failover settings. Request logs show actual destinations.
API keys live in a local SQLCipher-encrypted database; its master key is held in the system keychain. Provider configuration exports exclude API keys. Authentication is sent to the selected upstream when forwarding requests.
Keyway provides 9 CLI groups across the Anthropic / OpenAI / Gemini protocols. Claude Code, Codex CLI, Gemini CLI, OpenCode and OpenClaw support automatic takeover; other groups can be connected manually using the variables supported by each CLI.
Sessions already using the proxy need no restart when changing the default provider. New requests follow the updated configuration; in-flight requests do not migrate. First-time Codex takeover needs a new session, and routing rules still take priority.
Yes. Model routing rules send different models to different providers; failover switches to backups on upstream errors; profiles swap whole work / personal setups in one tap.
Click Restore in takeover management to undo Keyway's configuration changes while keeping unrelated edits. Conflicts in managed fields or generated entries stop the restore; the file and backup are retained for inspection.
Keyway is completely free and open source (MIT). You only pay the model providers you use.
CLIs connected to the local proxy depend on Keyway running. Closing the window keeps it in the tray; fully quitting stops the proxy. Restore configs first if you need direct connections. An offline proxy and an upstream provider failure are different states.
* Configuration and usage records are stored in an encrypted local database. The proxy sends request content and authentication to the selected model provider; local storage does not mean offline inference.
** Claude Code, Codex, Gemini CLI, OpenCode and OpenClaw are products of their respective owners; Keyway is not affiliated with Anthropic, OpenAI or Google.