Troubleshooting

Fixes for the problems people run into most often.

Signing in#

"Failed to fetch" when signing in. The app could not reach the Peridot servers. Check your internet connection, any VPN or firewall, and that the site loads in a browser. If you run the desktop app from source in development mode, it uses the hosted backend through a proxy. Restart bun run electron:dev after changing anything in vite.config.ts.

Google sign-in does nothing in the desktop app or the CLI. Google opens in your normal browser and returns to 127.0.0.1 on port 53682. Make sure no other program uses that port, and that your browser is allowed to open a link to 127.0.0.1.

"This account was registered with Google." The account was created with Google and has no password. Use Continue with Google.

Limits#

"You have reached today's message limit." Daily limits reset at midnight UTC. Agent runs use many requests (each tool step is one), so they use the daily count quickly. See Accounts and plans.

"You have used your usage allowance for this month." The monthly allowance resets on the 1st (UTC). Upgrade your plan or wait. Settings → Usage shows where you are.

"This model is not included in your plan." Pick another model, or upgrade. See Models and effort.

"This task has grown too long for your plan. Start a new one." An agent task sends its whole history on each step. Start a new chat and describe where you were.

Peridot Code#

The agent says "Stopped after too many steps." A run stops after 40 steps. Reply "continue" to carry on.

It cannot read a file. Files over 400 KB and binary files cannot be read, and files outside the project folder are refused. Ask it to search or read part of the file. See Tools and approvals.

An edit failed: "old_string was not found." The text it tried to replace did not match exactly, often because the file changed. The agent re-reads the file and retries.

A command times out. Commands have a 2 minute limit. For long-running tasks (dev servers, watchers) use the terminal panel instead of the agent.

Nothing is saved to my history. History is only saved when you are signed in.

AI team#

The lead does not use my bots. Select Lead on the team page and tick the bots. Write a specific role for each bot, and name the bot in your request. See Patterns and tips.

A run is stuck. A bot may be waiting for approval in the chat. Switch to the chat and answer the card.

My team is gone. Teams belong to a project, so check you opened the same folder. The team is in .peridot/team.json in the project, and a file that is not valid JSON loads as an empty team. See The team file.

"The teammate used up its steps before finishing." Bots get 25 steps. Give a smaller task. See How hand-offs work.

CLI#

Peridot says my workspace is very broad. You started it in your home folder or /. Start peridot inside a project folder instead.

The CLI does not know who I am. Run /login again, or set PERIDOT_TOKEN. The token lives in ~/.config/peridot/config.json.

Still stuck?#

Check the help center or contact us, and include the exact message you see, your platform and the app version.

← HTTP API Cowork →