Troubleshooting
The usual snags, what causes them and the fix.
“Unauthorized”
The key was revoked or rotated, or your organization was deleted.
Ask an admin for a current key (they're in Org settings → API keys), or sign in from your client instead.
A task is refused for money
The organization is out of credits, your allowance (or the key's) is used up, or the organization reached its monthly limit.
The result says which and whom to ask. An admin adds credits under Usage → Credits, raises the allowance in Org settings, or raises the monthly limit or turns on overage.
“This project is shared”
Saved logins and saved tasks are in Personal; identities are in a shared project.
Switch with switch_project, or in the app's project switcher. An organization API key stays in its own project.
“One task at a time”
Each person, each API key and each identity runs one task at a time.
Wait for the running task (get_job), carry it on with follow_up, or stop it with cancel_job.
Codex stops the call after a minute
Codex limits each tool call to 60 seconds by default, and a managed call can take up to 120 s.
Keep tool_timeout_sec in its config, as in the Codex examples.
npx fails, or the server won't start
An older Node.js, or Windows starting npx without a shell.
Check node --version is 22 or newer. On Windows, put cmd /c before npx.
The open MCP can't find a browser
Chrome is installed somewhere unusual, or you use another Chromium browser.
Point PILOTFISH_CHROME at the browser's executable.
The result says NEEDS A PERSON
The page wants a sign-in, a code or a check only you can do.
Do it in the browser window, then let the agent call browser_resume.
A site is refused
PILOTFISH_ALLOWED_HOSTS is set and doesn't include it, or it's on a private network.
Add its host to the list, or set PILOTFISH_ALLOW_PRIVATE=1 for localhost.
Still stuck?
Send us what you ran and what it said. A person reads every message.