Error reference changederrors
Nearest release: v2.1.238, published 10 hours 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+61added
Lines−1removed
From line
32
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits187to this page, all time
### The prompt to confirm went unanswered ### Too many messages to this session just now ### Refusing to send a cross-session message
The whole hunk
from line 32, old and new numbered
/
from line 32
3232| `Agent terminated early due to an API error` | [Server errors](#agent-terminated-early-due-to-an-api-error) |
3333| `You've hit your session limit` / `You've hit your weekly limit` | [Usage limits](#youve-hit-your-session-limit) |
3434| `Usage credits required for 1M context` | [Usage limits](#usage-credits-required-for-1m-context) |
35| `the prompt to confirm went unanswered — nothing was sent` | [Usage limits](#the-prompt-to-confirm-went-unanswered) |
3536| `Server is temporarily limiting requests` | [Usage limits](#server-is-temporarily-limiting-requests) |
3637| `Request rejected (429)` | [Usage limits](#request-rejected-429) |
3738| `Credit balance is too low` | [Usage limits](#credit-balance-is-too-low) |
from line 147
146147| `Failed to write to <name>'s inbox — nothing was sent` | [Tool errors](#failed-to-write-to-a-teammate-inbox) |
147148| `Failed to write the plan approval request to the lead's inbox — plan not submitted` | [Tool errors](#failed-to-write-to-a-teammate-inbox) |
148149| `Message too large for cross-session delivery` | [Tool errors](#message-too-large-for-cross-session-delivery) |
150| `Too many messages to this session just now` | [Tool errors](#too-many-messages-to-this-session-just-now) |
151| `Refusing to send: reply target is a symlink` / `Refusing to send: cannot vet reply target` | [Tool errors](#refusing-to-send-a-cross-session-message) |
152| `Refusing to send: connected endpoint is not the expected process` / `Refusing to send: connected endpoint identity could not be read` | [Tool errors](#refusing-to-send-a-cross-session-message) |
149153| `Can't open MCP settings while no terminal is attached to this background session` | [Background session errors](#commands-refused-in-a-background-session) |
150154| `Can't open MCP settings in a background session` | [Background session errors](#commands-refused-in-a-background-session) |
151155| `blocked because the path is spelled in a form that cannot be safely resolved` | [Background session errors](#write-or-command-blocked-because-the-path-cannot-be-safely-resolved) |
from line 394
390394
391395## Usage limits
392396
393Most errors in this section mean a quota tied to your account or plan has been reached. Two work differently: [`Server is temporarily limiting requests`](#server-is-temporarily-limiting-requests) is a server-side throttle unrelated to your plan quota, and [`Usage credits required for 1M context`](#usage-credits-required-for-1m-context) is an entitlement check rather than an exhausted quota.
397Most errors in this section mean a quota tied to your account or plan has been reached. Three work differently: [`Server is temporarily limiting requests`](#server-is-temporarily-limiting-requests) is a server-side throttle unrelated to your plan quota, [`Usage credits required for 1M context`](#usage-credits-required-for-1m-context) is an entitlement check rather than an exhausted quota, and [`The prompt to confirm went unanswered`](#the-prompt-to-confirm-went-unanswered) means a usage-credits consent prompt closed unanswered, whether or not a quota was reached.
394398
395399<h3 id="youve-hit-your-session-limit">
396400 You've hit your session limit
from line 442
438442* If the error persists after `/model`, a 1M model ID may be set elsewhere. See [Setting your model](/docs/en/model-config#setting-your-model) for the configuration locations to check in priority order.
439443* To remove 1M variants from the model picker entirely, set [`CLAUDE_CODE_DISABLE_1M_CONTEXT=1`](/docs/en/env-vars)
440444
445### The prompt to confirm went unanswered
446
447On plans where Fable 5 usage [bills to usage credits](/docs/en/model-config#fable-5-and-usage-credits), Claude Code asks you to confirm before a request bills them. When nobody answers that consent prompt in a session that may have no one at its terminal, Claude Code closes the prompt and ends the turn with one of these messages:
448
449```text theme={null}
450Fable 5 limit reached · continuing on Fable 5 uses usage credits, and the prompt to confirm went unanswered — nothing was sent · answer it where this session is running, or /model to change
451Fable 5 now uses usage credits · the prompt to confirm went unanswered — nothing was sent · answer it where this session is running, or /model to change
452```
453
454This happens in [Remote Control](/docs/en/remote-control) sessions, [background sessions](/docs/en/agent-view), and [agent team](/docs/en/agent-teams) teammate sessions. Claude Code shows the consent prompt only in the session's own interactive view: the terminal where it runs, or, for a background session, the [agents view](/docs/en/agent-view) once you attach. A Remote Control client can't display it. Claude Code closes the prompt at the [`dialogExpiry`](/docs/en/settings#available-settings) deadline, five minutes by default, or as soon as a new prompt arrives while nobody has typed at that terminal, such as a prompt sent from a Remote Control client. Typing at the terminal where the session runs cancels the deadline, and Claude Code waits for your answer. In a background session's attached view, typing doesn't cancel the deadline, so answer before it passes. Claude Code sends nothing and keeps your model, so when you send your next prompt, Claude Code shows the consent prompt again.
455
456**What to do:**
457
458* At the terminal where the session runs, send another prompt and answer the consent prompt when it reappears. For a background session, attach to it from the [agents view](/docs/en/agent-view) first. Resending from a Remote Control client shows this message again, because the client can't display the prompt.
459* Run `/model` to switch to a model that doesn't bill usage credits
460* To give yourself more time to reach that terminal, set [`dialogExpiry`](/docs/en/settings#available-settings) to a longer value or `"never"`
461
462Before v2.1.236, this message didn't appear: while a Remote Control client was connected, Claude Code waited 60 seconds for an answer and then continued the turn on your default model.
463
441464### Server is temporarily limiting requests
442465
443466The API applied a short-lived throttle that is unrelated to your plan quota.
from line 2105
20822105* Ask Claude to split the content across several shorter messages
20832106
20842107Before v2.1.235, Claude Code reported an oversized message as sent. The receiving session dropped it unread.
2108
2109### Too many messages to this session just now
2110
2111Claude sent a rapid burst of [cross-session messages](/docs/en/cross-session-messaging) to one of your sessions on this machine, and the burst reached what that session's inbox accepts. Claude Code refused the next send, and the receiving session got nothing from it. The refusal appears in the sending session's tool result, not as a banner in your terminal:
2112
2113```text wrap theme={null}
2114Failed to send to api-worker: Too many messages to this session just now: 30 were sent recently and more would be dropped by its rate limit, so this one was not sent. Batch what remains into one message, or wait a little before sending more.
2115```
2116
2117**What to do:**
2118
2119* Usually nothing: Claude batches the remaining content into one message, or waits before sending more
2120* If you prompted the burst yourself, ask Claude to combine what's left into a single message
2121
2122Before v2.1.236, Claude Code reported these sends as sent. The receiving session dropped them unread.
2123
2124### Refusing to send a cross-session message
2125
2126Before Claude Code writes a [cross-session message](/docs/en/cross-session-messaging) to another of your sessions on this machine, it checks that the target session's inbox socket is the endpoint the message was addressed to. When a check fails, Claude Code refuses the send in the sending session, and the target session receives nothing. For a message Claude sends, the refusal appears in the sending session's tool result:
2127
2128```text theme={null}
2129Failed to send to api-worker: Refusing to send: reply target is a symlink
2130```
2131
2132The text after `Refusing to send:` names the check that failed:
2133
2134* `reply target is a symlink`: a symbolic link sits at the target session's socket path. Claude Code doesn't deliver through it, because a link there could redirect the message to an endpoint the target session didn't create.
2135* `cannot vet reply target`: Claude Code couldn't inspect the target path at all, for example because reading it failed with a permission error.
2136* `connected endpoint is not the expected process`: the process holding the socket isn't the session the message was addressed to, so the address is stale or another process replaced the socket.
2137* `connected endpoint identity could not be read`: Claude Code connected but couldn't read which process holds the other end, so it couldn't confirm the target. This can be transient.
2138
2139**What to do:**
2140
2141* Usually nothing: the checks keep a message from reaching an endpoint other than the session it was addressed to, and nothing was sent
2142* Ask Claude to list your sessions again and resend; a refusal caused by a stale address clears once Claude sends to the current one
2143* If `reply target is a symlink` repeats for one session, check what created a link at that session's socket path, shown in its `/status` under `Peer address`
2144* For `connected endpoint identity could not be read`, resend; the condition can be transient
20852145
20862146## Background session errors
20872147
No line in this hunk matches that.