FAQ
Key rotation, config restore and other common questions
Is writing the key to auth.json the same as running codex login?
Exactly the same. codex login --api-key simply writes your key into ~/.codex/auth.json. Our install script writes that file directly, so you never need to run codex login — and the configuration is shared by the Codex CLI, the VS Code extension and the Codex app (all three read ~/.codex/).
How do I switch to a new key?
Re-run the install command with the new key — fastest and mistake-proof:
The old config is always backed up automatically before the new one is written.
Is it safe to run the script multiple times?
Yes. The scripts are designed to be re-run: the CLI gets upgraded to the latest version, and the old config is backed up as .bak.<timestamp> before anything is overwritten.
Does the script send my key anywhere?
No. The key input on the install page only inserts your key into the command right in your browser. The script runs on your machine and writes the key only to your local config file (auth.json / settings.json). You can read the script source yourself at /install/codex.sh, /install/claude.sh, /install/codex.ps1, /install/claude.ps1.
How many machines can one key be used on?
Coming soon — contact support for your package's policy.
Which models does Claude Code get?
With the default configuration: claude-fable-5 (most capable), claude-opus-5, claude-sonnet-5, claude-haiku-4-5. Type /model during a session to switch. Subagents run claude-sonnet-5 by default.
Which model does Codex use?
gpt-5.6-sol with xhigh reasoning effort and a 1,000,000-token context window — preconfigured, nothing to tweak.
How do I uninstall everything?
rm -rf ~/.codex # remove Codex config
rm -rf ~/.claude # remove Claude Code config
npm uninstall -g @openai/codex @anthropic-ai/claude-code