During update-v17.cmd / crak setup you can select:
- OpenRouter
- default:
openrouter/free - optional free slugs:
google/gemini-2.0-flash-exp:freemeta-llama/llama-3.3-70b-instruct:freedeepseek/deepseek-r1:freeqwen/qwen-2.5-coder-32b-instruct:free
- default:
- Google Gemini OAuth
- browser Google login using the existing desktop OAuth flow
- ChatGPT / Codex OAuth
- browser ChatGPT login using the local
@openai/codexpackage
- browser ChatGPT login using the local
The OpenRouter API key is not stored in the repository. It is stored under the user's .crak-agent home or read from OPENROUTER_API_KEY.
update-v17.cmdThe installer starts the provider selection wizard.
.\crak.cmd provider show
.\crak.cmd provider set openrouter
.\crak.cmd provider set gemini
.\crak.cmd provider set chatgptOpenRouter:
.\crak.cmd openrouter-key set
.\crak.cmd openrouter-model openrouter/freeGoogle:
.\crak.cmd login-google --client "C:\path\client_secret.json"ChatGPT:
.\crak.cmd login-chatgptThen:
.\crak.cmd doctor
.\crak.cmd test-ai
.\crak.cmd startImage generation remains on the Gemini image provider. You can use OpenRouter or ChatGPT for normal chat and keep Google OAuth connected only for /image.
Never commit API keys, OAuth tokens, WhatsApp sessions, .crak-agent data, or secrets to Git.