Engine troubleshooting
Fix missing CLIs, failed authentication, model errors, and path differences.
“CLI not found”
- Open a terminal and run the CLI directly.
- Confirm the command is an executable, not only a shell alias or function.
- Restart Brainwrite after installation.
- Set the exact executable in Settings → Model providers if automatic detection still fails.
Apps opened from Finder or the Dock often get a different environment from your Terminal, so an engine that works in Terminal may not be found.
Authentication failures
Run the provider's own status or login command in a terminal. Brainwrite uses the CLI's authenticated session; installing the binary alone is not enough.
A 401 Unauthorized response from api.openai.com means the launched Codex process did not receive valid authentication. Confirm codex login status, sign in again if needed, then restart Brainwrite. Do not paste a ChatGPT password into Brainwrite.
When Codex has no sign-in at all on the computer that runs the bot, the message stops at once with Codex isn't signed in on this computer. Sign in to Codex in Settings → Model providers → Codex. Sign-ins don't copy over when you move to My Cloud, so sign in there too.
Codex usage limit
When the ChatGPT account Codex uses reaches its Codex usage limit, the chat says so, and that this is OpenAI's limit, not your Brainwrite Cloud plan. It says when the limit resets, when OpenAI gives the time. The message offers Manage usage, which opens your Codex usage page at OpenAI, instead of a retry. Until the limit resets, manage your usage in ChatGPT or switch the bot to another engine; see When an engine runs out of quota.
A selected model fails
- Refresh the model picker after updating the CLI.
- Choose a model actually available to that provider account.
- Confirm a custom wrapper forwards the model argument and preserves the provider's expected environment.
- Try the provider CLI directly with the same model to separate an account problem from a Brainwrite integration problem.
Codex sandbox mismatch
Brainwrite preserves Codex's resolved network and writable-folder settings when starting a turn. If Codex returns no resolved sandbox or a different mode from the one requested, the turn stops before sending your message. Check the native Codex sandbox setup and selected access mode, then retry. Brainwrite does not silently replace that policy with broader access.