Error reference changederrors
Nearest release: v2.1.251, published 7 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+18added
Lines−0removed
From line
124
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits193to this page, all time
The whole hunk
from line 124, 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 124
124124| `The connection dropped while downloading the update` | [Installation errors](#the-connection-dropped-while-downloading-the-update) |
125125| `Download timed out: exceeded the total deadline` | [Installation errors](#the-connection-dropped-while-downloading-the-update) |
126126| `--bg and --print conflict` | [Command-line errors](#command-line-errors) |
127| `Cloud sessions cannot be created from a --restricted session` | [Command-line errors](#cloud-sessions-cannot-be-created-from-a-restricted-session) |
127128| `Error: --json-schema is not a valid JSON Schema` | [Command-line errors](#command-line-errors) |
128129| `Error: Settings file exceeds the 2MiB limit` | [Command-line errors](#settings-file-exceeds-the-2mib-limit) |
129130| `The current directory no longer exists (it was deleted or moved)` / `Can't read the current directory` | [Command-line errors](#the-current-directory-no-longer-exists) |
from line 1789
17881789* Drop `-p` or `--print`. `--bg` takes the prompt as its positional argument, so `claude --bg "<task>"` is the complete command. See [Dispatch new agents from your shell](/docs/en/agent-view#from-your-shell).
17891790* To run the prompt non-interactively and print the result instead of creating a background session, drop `--bg` and run `claude -p "<task>"`
17901791
1792<h3 id="cloud-sessions-cannot-be-created-from-a-restricted-session">
1793 Cloud sessions cannot be created from a --restricted session
1794</h3>
1795
1796When you start a session with [`--restricted`](/docs/en/cli-reference#cli-flags), Claude Code refuses to create [cloud sessions](/docs/en/claude-code-on-the-web#from-terminal-to-web) from it, because the new session would run outside the restricted process and wouldn't enforce restricted mode. Claude Code refuses on the client, before contacting the server, so no cloud session is created:
1797
1798```text theme={null}
1799Cloud sessions cannot be created from a --restricted session: they would not enforce it.
1800```
1801
1802**What to do:**
1803
1804* Run the task locally in the restricted session
1805* If you control how the session was launched, start a new `claude` session without `--restricted` and create the cloud session from there
1806
1807Before v2.1.248, Claude Code had no `--restricted` flag; earlier versions reject the flag itself with an unknown-option error.
1808
17911809### The --json-schema value is not a valid JSON Schema
17921810
17931811The schema you passed to [`--json-schema`](/docs/en/cli-reference#cli-flags) in [non-interactive mode](/docs/en/headless#get-structured-output) failed JSON Schema compilation, so `claude` exits with code 1 instead of running the prompt. Before v2.1.205, an invalid schema produced unstructured output with no error, and any schema that used the `format` keyword was treated as invalid.
from line 2468
24502468
24512469### Too many messages to this session just now
24522470
2453Claude 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:
2454
2455```text wrap theme={null}
2456Failed 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.
2457```
2458
2459**What to do:**
2460
2461* Usually nothing: Claude batches the remaining content into one message, or waits before sending more
2462* If you prompted the burst yourself, ask Claude to combine what's left into a single message
2463
2464Before v2.1.236, Claude Code reported these sends as sent. The receiving session dropped them unread.
2465
2466### Refusing to send a cross-session message
2467
2468Before 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:
2469
2470```text theme={null}
2471Failed to send to api-worker: Refusing to send: reply target is a symlink
2472```
2473
2474The text after `Refusing to send:` names the
2471Claude 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.
No line in this hunk matches that.