Error reference changederrors
Nearest release: v2.1.312, published 2 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 27 Oct 2026 20:49 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 27 Oct 2026 21:07 UTC.
Upstream edited
Recorded here
Lines+31added
Lines−4removed
From line
142
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits202to this page, all time
### Feedback payload too large ### A command-line deny rule cannot be handed to a teammate intact
The whole hunk
from line 142, 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 142
142142| `N sessions ended while this machine was offline — the environment was cleaned up on the server and can't be resumed.` | [Network](#sessions-ended-while-this-machine-was-offline) |
143143| `Couldn't share the transcript.` | [Network](#couldnt-share-the-transcript) |
144144| `Couldn't send feedback` | [Network](#couldnt-send-feedback) |
145| `Feedback payload too large. Try again without the transcript, or shorten the details.` | [Network](#feedback-payload-too-large) |
145146| `MCP server "<name>" connection timed out. Your computer went to sleep or its clock changed while connecting.` | [Network](#mcp-server-connection-timed-out-during-a-sleep-or-clock-change) |
146147| `Prompt is too long` / `Input is too long for requested model` | [Request errors](#prompt-is-too-long) |
147148| `Prompt is too long · automatic compaction failed:` | [Request errors](#prompt-is-too-long) |
from line 332
331332| `Failed to write the plan approval request to the lead's inbox — plan not submitted` | [Tool errors](#failed-to-write-to-a-teammate-inbox) |
332333| `Its agent definition was not restored: the folder its definition file came from is not trusted` | [Tool errors](#teammate-agent-definition-not-restored) |
333334| `Only a teammate can approve a shutdown request` | [Tool errors](#only-a-teammate-can-approve-a-shutdown-request) |
335| `A command-line deny rule cannot be handed to a teammate intact` | [Tool errors](#command-line-deny-rule-cannot-be-handed-to-a-teammate) |
334336| `Message too large for cross-session delivery` | [Tool errors](#message-too-large-for-cross-session-delivery) |
335337| `Too many messages to this session just now` | [Tool errors](#too-many-messages-to-this-session-just-now) |
336338| `Cross-session message was dropped at the recipient session's inbox` | [Tool errors](#cross-session-message-dropped-at-the-inbox) |
from line 2186
21842186
21852187### Couldn't send feedback
21862188
2187A message starting `Couldn't send feedback` means the report you submitted from the [`/feedback`, `/bug`, or `/share` dialog](https://code.claude.com/docs/en/commands#all-commands), or a queued [feedback draft](https://code.claude.com/docs/en/tools-reference.md#sendfeedback-tool-behavior), wasn't sent. When a sentence about your organization follows the colon, your organization refuses feedback and the same report gets the same answer.
2189A message starting `Couldn't send feedback` means the feedback service didn't confirm the report you submitted from the [`/feedback`, `/bug`, or `/share` dialog](https://code.claude.com/docs/en/commands#all-commands), or a queued [feedback draft](https://code.claude.com/docs/en/tools-reference.md#sendfeedback-tool-behavior). Treat it as not received. When a sentence about your organization follows the colon, your organization refuses feedback and the same report gets the same answer.
21882190
2189The first of these two examples is a network failure and the second is an organization's refusal:
2191The second of these two examples is an organization's refusal:
21902192
21912193```text wrap theme={null}
21922194Couldn't send feedback (couldn't reach the service). If it keeps failing, you can file at https://github.com/anthropics/claude-code/issues instead.
from line 2201
21992201* **Not signed in**: the message continues `: not signed in. Run /login, then retry.` Run `/login`, then send again
22002202* **Your organization's refusal**: for example `: Feedback has not been enabled for your organization.` or `: Feedback collection is not available for organizations with custom data retention policies.` If the message adds `To report a bug, open an issue`, do so at [github.com/anthropics/claude-code/issues](https://github.com/anthropics/claude-code/issues). A queued draft stays queued, and you can [discard it](https://code.claude.com/docs/en/tools-reference.md#discard-or-keep-a-draft)
22012203* **Refused credentials**: the message continues `: the sign-in this session uses is not allowed to send feedback` or `: the server did not accept the credentials this session uses`. Run `/status` at the Claude Code prompt to see which login, token, or API key this session sends
2202* **`(request timed out)` or `(couldn't reach the service)` straight after `Couldn't send feedback`**: these are network failures. Send the report or the queued draft again. The dialog keeps your text, and a queued draft's message says `The draft is still queued.` If other requests are failing too, check your network connection and see [Unable to connect to API](#unable-to-connect-to-api). If it keeps failing, file the report at [github.com/anthropics/claude-code/issues](https://github.com/anthropics/claude-code/issues)
2204* **`(request timed out)` or `(couldn't reach the service)` straight after `Couldn't send feedback`**: send the report or the queued draft again. The dialog keeps your text, and a queued draft's message says `The draft is still queued.` If other requests are failing too, check your network connection and see [Unable to connect to API](#unable-to-connect-to-api). If it keeps failing, file the report at [github.com/anthropics/claude-code/issues](https://github.com/anthropics/claude-code/issues)
22032205* **`(server returned <status>)`, or no reason, straight after `Couldn't send feedback`**: the status is the service's response code. The service's own message follows it when one was sent, as in `(server returned 403: Access Forbidden)`. If it keeps failing, file the report at [github.com/anthropics/claude-code/issues](https://github.com/anthropics/claude-code/issues)
22042206
22052207Issues at github.com/anthropics/claude-code are public, so leave out code, transcripts, and anything else confidential when you open one.
from line 2208
22062208
22072209Before v2.1.281, every send failed with this message once a Remote Control **Stop** or an urgent cross-session message had arrived while the dialog was open. On those versions, close the dialog, reopen it, and send again.
22082210
2211### Feedback payload too large
2212
2213This message in the [review screen](https://code.claude.com/docs/en/tools-reference.md#review-and-edit-a-draft) for a [feedback draft](https://code.claude.com/docs/en/tools-reference.md#sendfeedback-tool-behavior) means Claude Code has no confirmation that the service accepted the draft. Treat it as not received. The draft stays in your `/feedback` queue, so you can send it again.
2214
2215```text wrap theme={null}
2216Feedback payload too large. Try again without the transcript, or shorten the details.
2217```
2218
2219**What to do:**
2220
2221* In the review screen, set **Send transcript** to `no`, then send the draft again. Shortening the details removes at most 10 KB of text, which is all a draft's details can hold.
2222
22092223### MCP server connection timed out during a sleep or clock change
22102224
22112225This message means a connection to an [MCP server](https://code.claude.com/docs/en/mcp.md) timed out, and Claude Code found that your system clock jumped forward during the attempt:
from line 2513
24992513
25002514### tool\_use.name over 200 characters
25012515
2502A tool call in the conversation history carries a name longer than the 200 characters the API accepts in a request:
2503
2504```text theme={null}
2505API Error: 400 ... tool_use.name: String should have at most 200 characters
2506```
2507
2508Claude Code cuts such a name to 200 characters when the response arrives and when it loads a saved conversation, so the call fails with a [`No such tool available`](#no-such-tool-available) tool error and the conversation continues without this API error.
2509
2510**What to do:**
2511
2512* Run `claude update`, then resume the conversation. The updated version repairs the overlong name when it loads the transcript, so a conversation that was stuck works again.
2513
2514Before v2.1.281, the overlong name stayed in the history and the API rejected every request that re-sent the conversation, including `/compact` and `--resume`, so this error repeated and the conversation was stuck.
2515
2516### There's an issue with the selected model
2517
2518The configured model name was not recognized or your account lacks access to it. As of v2.1.160 the trailing hint, shown here in its interactiv
2516A tool call in the conversation history carries a name longer than the 200 characte
No line in this hunk matches that.