Guides·Troubleshooting

Errors and fixes

Every page here starts from the error text you actually saw, explains the mechanism that produced it, and ends with a fix that survives the next restart.

Download for Mac All guides
01

Start here

Troubleshooting

Why Cursor is slow, and how to isolate the real cause

Typing lag, slow Agent replies, high CPU, and Remote SSH stalls have different causes. This sequence separates them in minutes.

Read guide →12 min Troubleshooting

Cursor says you have hit your usage limit: fix it properly

The exact checks to identify the empty pool, keep working safely, and prevent the same mid-task surprise next cycle.

Read guide →11 min Troubleshooting

Exit code 137 and the rest: reading how a process died

What 137, 143, 127, 126, 130, 124, 1, 2, and 255 actually tell you, and what to do about each.

Read guide →9 min
02

Every guide in this cluster

zsh: command not found: claude - the actual fix Find where it actually installed, why the shell cannot see it, and the fix that survives a restart. 7 min Claude Code rate limit reached: what to do right now Which limit you hit, what to do in the next five minutes, and how to stop it recurring. 7 min Claude Code not working: a diagnostic order that finds it Six checks in the order that finds the problem fastest, plus a symptom-to-cause table. 8 min Claude Code permission errors: reading the refusal correctly Filesystem denials, policy refusals, macOS folder protection, and the sandbox all look alike. How to tell which you have. 8 min Claude Code context low: what it means and what to do What the warning means, why compacting deliberately beats waiting for it, and how to fill the window slower. 7 min MCP server not connecting in Claude Code The stdout trap that breaks most custom servers, plus the six other causes in order. 6 min Claude Code in WSL: the problems and their fixes The filesystem trap that halves your speed, searches that silently miss files, and login that never returns. 6 min Codex CLI not working: the sandbox is usually why Most Codex failures are the sandbox working correctly. How to tell those from real problems, starting with one command. 7 min Delete a Claude Code session, and everything it left behind Why /clear deletes nothing, where the transcripts live, and the command that removes a project cleanly. 7 min Exit code 137 and the rest: reading how a process died What 137, 143, 127, 126, 130, 124, 1, 2, and 255 actually tell you, and what to do about each. 9 min Claude rate limits: two systems that share one name A subscription window and an API throughput limit are different mechanisms with the same name. Here is both, and how to tell them apart. 7 min Claude rate limit reached: is it you, or is Claude down? Five different messages, three of them about you and two about Anthropic. Which one you got decides everything. 6 min Claude token limit per day: the ceilings that actually exist Nobody publishes a daily token cap because there is not one. Here is every ceiling that does exist, in its real unit. 7 min Cursor says you have hit your usage limit: fix it properly The exact checks to identify the empty pool, keep working safely, and prevent the same mid-task surprise next cycle. 11 min Why Cursor is slow, and how to isolate the real cause Typing lag, slow Agent replies, high CPU, and Remote SSH stalls have different causes. This sequence separates them in minutes. 12 min
03

Other clusters

PricingUsage trackingInstallReferenceMCPCodexGeminiCursorWorktreesHead to headConcepts
Try it

Every agent.
One workbench.

Continuum runs Claude Code, Codex, Cursor, Gemini, and more under the subscriptions you already pay for, with live quota gauges and spend by repo.

Download for Mac Compare tools

free app · your subscriptions · local-first