Error reference changederrors
Nearest release: v2.1.248, published under an hour before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+25added
Lines−4removed
From line
93
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits190to this page, all time
The whole hunk
from line 93, old and new numbered
/
This page is larger than the 256 KiB this site keeps, so one side of the diff below stops where the stored text does.
from line 93
9393| `The remote session sent a reply this version can't display` | [Network](#the-remote-sent-a-reply-this-version-cant-display) |
9494| `Prompt is too long` / `Input is too long for requested model` | [Request errors](#prompt-is-too-long) |
9595| `Prompt is too long · automatic compaction failed:` | [Request errors](#prompt-is-too-long) |
96| `Prompt is too long · this conversation is a single exchange` / `A single-exchange conversation cannot be compacted` | [Request errors](#prompt-is-too-long) |
9697| `Context limit reached · /compact or /clear to continue` | [Request errors](#prompt-is-too-long) |
9798| `Context limit reached · /clear to continue` | [Request errors](#prompt-is-too-long) |
9899| `capability_rejected: prompt_too_long` on a Claude apps gateway session | [Request errors](#prompt-is-too-long) |
from line 1371
13701371
13711372Resolve the named error first; `/compact` fails on the same error until you do. Before v2.1.229, a failed automatic compaction surfaced `Prompt is too long` without the cause.
13721373
1374A single-exchange conversation has no earlier turns to summarize. When automatic compaction would have run on one, Claude Code skips the attempt and explains what fills the request instead. When the API doesn't report token counts in its error, the message reads:
1375
1376```text theme={null}
1377Prompt is too long · this conversation is a single exchange and cannot be compacted — the request size comes mostly from system prompt, tool definitions, or attachments.
1378```
1379
1380When the API reports token counts in its error, Claude Code compares them with its own estimate of the conversation's size to tell which is most of the request: the conversation's own content, or the system prompt, tool definitions, and attachment content that Claude Code sends with it. When the conversation's own content is most of the request, the message reads:
1381
1382```text theme={null}
1383Prompt is too long · the request is ~<request tokens> tokens (limit <limit>) and this conversation's own content is most of it. A single-exchange conversation cannot be compacted; start with less content (smaller files or pasted text).
1384```
1385
1386When most of the request is outside the conversation, the message reads:
1387
1388```text theme={null}
1389Prompt is too long · the request is ~<request tokens> tokens (limit <limit>) but this conversation is only ~<conversation tokens> tokens — the rest is system prompt, tool definitions, and attachment content. A single-exchange conversation cannot be compacted; reduce attached files/tools or start with less context.
1390```
1391
1392Before v2.1.162, Claude Code attempted the compaction anyway and surfaced the bare `Prompt is too long` when it failed.
1393
13731394**What to do:**
13741395
1375* Run `/compact` to summarize earlier turns and free space, or `/clear` to start fresh
1396* In a multi-turn conversation, run `/compact` to summarize earlier turns and free space, or `/clear` to start fresh. A single-exchange conversation can't be compacted, so shrink the request instead
13761397* Run `/context` to see a breakdown of what is consuming the window: system prompt, tools, memory files, and messages
13771398* Disable MCP servers you are not using with `/mcp disable <name>` to remove their tool definitions from context
13781399* Trim large `CLAUDE.md` memory files, or move instructions into [path-scoped rules](/docs/en/memory#path-specific-rules) that load only when relevant
from line 1420
13991420
14001421**What to do:**
14011422
1402* Run `/compact` to summarize earlier turns and free space, or `/clear` to start fresh
1423* In a multi-turn conversation, run `/compact` to summarize earlier turns and free space. To start fresh instead, run `/clear`
14031424* For more ways to reduce usage, see [Prompt is too long](#prompt-is-too-long)
14041425
14051426Before v2.1.216, `/context` showed usage above 100% with no warning line explaining what that meant or how to recover.
from line 2510
24892510**What to do:**
24902511
24912512* Re-create the agent file at `.claude/agents/<name>.md` in the session's project, or at `~/.claude/agents/<name>.md` for a personal agent, then resume again
2492* Or resume with `--agent <name>` naming an agent that does exist, to run the session as that agent instead
2493* If the agent is project-scoped and you haven't trusted the session's original directory, run Claude Code there once, accept the trust dialog, then resume again
2494
2495### CLAUDE\_CODE\_PROCESS\_WRAPPER launcher errors
2496
2497[`CLAUDE_CODE_PROCESS_WRAPPER`](/docs/en/corporate-launcher) is set, and its value can't be used, so Claude Code refuses to start the affected process rather than run it without the launcher. Configuration problems are reported with a message that starts with the variable name and states the reason, for example:
2498
2499```text theme={null}
2500CLAUDE_CODE_PROCESS_WRAPPER: launcher `/opt/corp/launcher` is not an executable regular file
2501```
2502
2503A launcher that starts but exits without replacing itself with Claude Code fails the session it was starting, and the session's row in agent view reports that the launcher `must exec, not daemonize`, followed by anything the launcher printed. A session that can't start or reach the background service because of the launcher reports the launcher problem as the reason inside `Couldn't reach the background service (...)`.
2504
2505**What to do:**
2506
2507* Set the variable to the absolute path of an executable that ends by calling `exec "$@"`. See [the launcher contract](/docs/en/corporate-launcher#the-launcher-contract) for the full contract
2508* Check `/status`, which shows the resolved launch command in its Self-exec entry and warns when the running background service doesn't match it, or run `claude daemon status` from a shell
2509* After fixing the value in the `env` block of [settings](/docs/en/corporate-launcher#set-up-the-launcher), restart the background service with `claude daemon stop --any` so the next dispatch starts a wrapped one
2510
2511### EUNKNOWN when starting a background session
2512
2513Windows refused to start a program with an error code that has no standard name, so the failure surfaces as `EUNKNOWN`. The usual trigger is a software restriction policy, such as Group Policy or AppLocker, blocking the program being started. The error appears when you start a
2513* Or resu
No line in this hunk matches that.