A troubleshooting guide

Is Devin down, or is it you?

The Devin CLI’s status isn’t on the page with Devin’s name: its agent runs on Windsurf’s servers. Here is which page to read, and what each error the CLI shows you means.

Open status.windsurf.com

Check in a minute

Look at Windsurf's status page

The Devin CLI’s agent runs on Windsurf’s servers, so its status is on status.windsurf.com, under “Cascade”. Some incidents there are posted with no row attached, so read the incident list too, not only the rows.

Read the error's exact words

Devin shows the kind of failure first, then the server’s own detail. A server error is Cognition’s side; a quota, a usage limit, a sign-in or a permission is yours. The table below sorts each one.

Run devin auth status

devin auth status shows how you’re signed in, your plan and team, and the servers the CLI talks to. Using --cloud or /handoff? Those go to Devin Cloud, whose status is on devinstatus.com.

The error says whose side it’s on

Devin retries a dropped connection on its own and keeps whatever answer already arrived, so a short blip rarely reaches you. What does reach you sorts into three kinds.

What Devin says	Whose side	What to do
`Server error: …`	Whose side: Cognition's	The server failed, and the detail after the colon says how. Wait a little and send again; if it repeats, check status.windsurf.com.
`Quota exhausted`	Whose side: Yours	Your daily or weekly allowance is used up. Wait for it to reset, or buy on-demand usage or turn on auto-reload at Settings → Usage & limits. Before CLI 3000.10.21 a server rate limit was labelled this way too, so update if you’re older.
`Usage limit reached`	Whose side: Yours	A monthly limit on your account, or your organization's (“Organization usage limit reached”). The alert links to a request for more usage; your admin decides.
`You've reached your ChatGPT subscription usage limit.`	Whose side: Yours	You've shared your ChatGPT subscription with Devin and that plan's limit is used up. Resume once it resets, or turn off ChatGPT token sharing in settings to carry on with Devin usage.
`Not logged in. Please run /login first.`	Whose side: Yours	Sign in again: `devin auth logout`, then `devin auth login`. If the browser step hangs, add `--force-manual-token-flow`.
`Permission denied: …`	Whose side: Yours	On an enterprise account, the CLI needs the “Use Devin CLI” permission, and access to Windsurf's tools doesn't include it. Ask your admin.
`Connection lost, retrying`	Whose side: Could be either	The answer dropped partway and Devin is retrying, keeping what already arrived. If it settles on “Connection error, send a message to continue retrying”, check the status page, then your network or proxy.
`Rate limited: …`	Whose side: Could be either	Too many requests in a short time, from you or across the service. Wait a few minutes before retrying; Devin's docs point to your organization's usage dashboard for quota.
`Request timed out: …`	Whose side: Could be either	Retry. Behind a corporate proxy, set HTTPS_PROXY or the proxy block in Devin's config.json; a TLS-inspecting proxy also needs its root certificate in the macOS keychain.

Status page clear and the error keeps coming? Run devin update in case you’re on an old CLI, look in ~/.local/share/devin/cli/logs, and report it with /bug.

Or let the menu bar check for you

Hear about an outage before you start debugging

Perch reads status.windsurf.com for you once you’ve used Devin on your Mac: often while a session is open, less often between them. When the Cascade row shows an outage, a red banner in the menu bar dropdown says so and links to the incident. A slowdown, maintenance, or an incident posted with no row shows as a small icon beside Devin’s usage, and every open problem is listed in Settings → General → Integrations.

It shows what has been posted, so in the first minutes of an outage the error in your terminal can arrive before the incident does. Your own allowance is on the same row: Perch shows how much of Devin’s daily and weekly quota you’ve used, and warns you before it runs out. How Perch watches agent health.

Get Perch — $29 Download for macOS

Questions

Devin outages, answered

Is Devin down right now?

For the Devin CLI, check status.windsurf.com and the Cascade row, plus any incident posted there without a row. If it's clear and you still get errors, the cause is usually your quota, your sign-in or your network, and the error's first words say which.

Why Windsurf's status page and not devinstatus.com?

Because the Devin CLI's agent runs on Windsurf's servers: devin auth status lists server.codeium.com as its API server, and Cognition's admin docs link status.windsurf.com as the Devin Desktop status page. devinstatus.com covers Devin Cloud, which the CLI uses only for cloud features such as --cloud and /handoff.

Where do I see how much Devin usage I have left?

Run /usage inside the Devin CLI for your daily and weekly allowance and when each resets, or open Settings → Usage & limits at app.devin.ai. The allowance is shared between Devin sessions, the Devin CLI and Devin Desktop.

Does devin doctor check whether Devin is reachable?

No. devin doctor checks your subagent profiles and AGENT.md files, not the network. For the connection, run devin auth status, and read the CLI's logs in ~/.local/share/devin/cli/logs.

Does the Devin CLI retry on its own?

Yes. When the connection drops mid-answer it retries, keeps the text that already arrived, and shows repeated failures as one notice. If it gives up, sending another message retries again.

The same guide for Claude Code, Codex, Amp and Droid.