Help
Quick answers
- Which systems does it run on?
macOS (Apple Silicon, macOS 12 or later) and Windows (10 / 11, x64). There's no Intel Mac or Linux build yet.
- Which agents does it support?
Claude Code, Codex, Grok Build and ZCode. Each agent is written to by its own open-source adapter; see How each agent is written.
- Does it cost anything?
No. There's no subscription and no account. The source is available under PolyForm Noncommercial 1.0.0: free for personal use, learning and research; commercial use needs a separate license.
- Do I need Python or anything else?
No. The four adapters ship inside the app. Switch doesn't install the agents themselves; get those from their official sources.
- Could it break my configuration?
Every write starts with a plan you review, and nothing is written until you confirm. Everything is backed up first. Turning a prompt off undoes only what Switch wrote; your own content stays. When an adapter finds a write unsafe, it refuses and changes no files.
- Are my prompts uploaded?
No. Prompts live only in
~/.keysmith-switch/on your computer, and there are no analytics or telemetry. The app goes online mainly to check for updates and read announcements, and reads the extension source only after you turn Extensions on. The full list is in Data and privacy.- Where is it safe to download?
Only from this site's download page or the official GitHub releases page. Don't open an installer you got anywhere else.
Installing and opening
- macOS says it can't be opened or verified
macOS stops the app the first time. Open System Settings → Privacy & Security, find Keysmith Switch near the bottom, click Open Anyway and confirm. On macOS 14 and earlier you can also right-click it in Applications and choose Open. You only do this once.
- Windows says “Windows protected your PC”
Click More info, then Run anyway. It installs into your own user folder and doesn't need administrator rights.
- My antivirus flags it
If you downloaded it from this site or the official GitHub releases page, it's a false alarm. Restore the file from quarantine and add Keysmith Switch to the trusted list (allowlist). Not sure? Ask us on GitHub.
- How do I update?
When a new version is out, a red dot appears in Settings; one click updates, and only when you say so. You can also download the new version from the download page and install it; your library is unaffected.
- Checking for updates times out
On versions before v0.3.7 with a proxy turned on, checking for updates can time out. Download the new version from the download page and install it once by hand; later updates then work.
- How do I uninstall?
First turn off each agent's prompt and disconnect input rewrite in the app, so the agents' configuration is put back. Then move the app to the Trash on macOS, or uninstall it from Settings → Apps on Windows. Uninstalling keeps
~/.keysmith-switch/(your library and backups); to remove it completely, delete that folder by hand afterwards.
Deploying and turning off
- I deployed, but the agent doesn't use it
Restart the agent after deploying: start a new session in Claude Code, Codex or Grok Build, and reopen ZCode. Sessions already open don't reload the prompt.
- A deploy is blocked because the config changed
Someone (or another tool, such as cc-switch) edited this agent's configuration after the last deploy. That's drift, and the deploy is blocked so your edits aren't overwritten. Follow the dialog:
- if only the managed lines moved, click Tidy config;
- if the record is a mess, Clean up to start over (this deletes the agent's login and session history; read the cleanup plan first).
- Turning off says the record or backup is missing
If the config backup from before deploying is gone (a cleanup may have removed it), choose Keep current config and turn off; only the part Keysmith wrote is removed. If the deployment record is missing, Clean up clears the stale record.
- Windows says permission denied
Your Windows account doesn't have full control of that agent's folder. Give it Full control and try again.
- I edited the live prompt, but the agent didn't change
Saving changes only the library copy. Deploy it again to write the change to the agent; the app reminds you after saving.
- Deploying to ZCode fails
Make sure ZCode is installed from its official source, has been opened at least once, and is signed in with an API key (ZCode supports API sign-in only). When a deploy is refused, the dialog shows the adapter's exact reason.
Clean up and roll back
- What does cleanup delete?
Cleanup returns an agent to a fresh install: the deployed prompt, the rules and configuration you added are removed; logins, session history, plugins and caches are deleted, not saved. Everything is listed before it runs; see Clean up and roll back.
- Can I get it back afterwards?
Most of it. A version is saved first; roll back under Settings → Versions and the prompt, memory file, rules and configuration come back. Logins and session history don't; sign in again.
- Cleanup says the agent is running
Quit the agent first: while it runs, its sessions, memories and login are in use.
Input rewrite
- After connecting, the agent can't reach the model
The Input rewrite page shows each agent's status. If it says the relay isn't running, click Reconnect; you can also Disconnect any time and the agent connects directly again.
- Why does it say “bypassed”?
Another tool changed the setting Switch wrote, for example switching Codex's provider or changing Claude Code's API address. Click Reconnect.
- Why can't my agent connect?
Current limits: Claude Code doesn't support Bedrock or Vertex; Codex needs a custom provider rather than its built-in OpenAI sign-in; ZCode doesn't support Coding Plan sign-in; Grok Build must have run once.
Feedback and help
- How do I report a problem or ask for a feature?
In the app, open Settings → About and choose Report a problem or Request a feature; a prefilled GitHub form opens for you to review and submit. You can also post in GitHub Discussions, or join the conversation on LINUX DO or in the Telegram group.
- What should I leave out of feedback?
GitHub issues are public. Don't include tokens, cookies, private paths, complete configuration or prompt text. Please don't disclose security issues publicly in Discussions.