Error reference changederrors
Nearest release: v2.1.323, 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 12 Nov 2026 23:23 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 12 Nov 2026 23:37 UTC.
Upstream edited
Recorded here
Lines+46added
Lines−3removed
From line
118
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits234to this page, all time
### Stopped an OAuth request ### Remote Control did not start because of the `--settings` file ### The settings file has changed since Remote Control started
The whole hunk
from line 118, 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 118
118118| `A request to MCP server "<name>" was sent without your stored credentials` | [Authentication](#couldnt-read-the-stored-credentials-for-mcp-server) |
119119| `This server's URL is missing or not a valid URL, so sign-in can't start` | [Authentication](#mcp-server-url-is-missing-or-not-a-valid-url) |
120120| `Issuer mismatch in authorization response (RFC 9207)` | [Authentication](#issuer-mismatch-in-authorization-response) |
121| `Stopped an OAuth request` | [Authentication](#stopped-an-oauth-request) |
121122| `Refusing to send credentials to non-https token endpoint` / `<short-name> from the MCP SDK for <server-url>` | [Authentication](#refusing-to-send-credentials-to-non-https-token-endpoint) |
122123| `Cloud gateway session expired — run /login to reconnect.` | [Authentication](#cloud-gateway-session-expired) |
123124| `Cloud gateway <url> no longer accepts this session` | [Authentication](#cloud-gateway-session-expired) |
from line 248
247248| `Ultrareview did not start` | [Command-line errors](#ultrareview-did-not-start) |
248249| `Remote Control did not start: "<question>" got no answer` | [Command-line errors](#remote-control-did-not-start-got-no-answer) |
249250| `` `<flag>` before `remote-control` is not carried over to the sessions Remote Control starts `` | [Command-line errors](#not-carried-over-to-the-sessions-remote-control-starts) |
251| `Remote Control did not start, because sessions would skip part or all of the --settings file` | [Command-line errors](#remote-control-did-not-start-because-of-the-settings-file) |
252| `The settings file <file> has changed since Remote Control started, so this session did not start` | [Command-line errors](#settings-file-changed-since-remote-control-started) |
250253| `--sandbox is not supported by claude remote-control` / `--no-sandbox is not supported by claude remote-control` | [Command-line errors](#sandbox-is-not-supported-by-claude-remote-control) |
251254| `` `claude import` is not yet available in this build `` | [Command-line errors](#claude-import-is-not-yet-available-in-this-build) |
252255| `Could not read Claude Code config` | [Command-line errors](#could-not-read-claude-code-config) |
from line 824
821824Later calls in the same Claude response can be denied with this reason:
822825
823826```text theme={null}
824another call in this response was changed by a hook after auto mode reviewed it, or could not be confirmed unchanged
827another call in this response was changed after auto mode reviewed it, or could not be confirmed unchanged
825828```
826829
827830Claude can then issue each denied call again so the server reviews it. If a permission prompt opens, answer it. You don't need to do anything else unless Claude says in its reply that auto mode couldn't check the call. Then stop the change or approve the call yourself, and ask Claude to try the call again:
from line 1821
18181821
18191822Before v2.1.232, Claude Code used the v2 runtime only in a gradual rollout or when you set `MCP_SDK_GENERATION=v2`.
18201823
1824### Stopped an OAuth request
1825
1826This message means that Claude Code stopped an [OAuth request for an MCP server](https://code.claude.com/docs/en/mcp.md#authenticate-with-remote-mcp-servers) because an OAuth endpoint redirected it. In both forms of the message, the first address is the one that sent the redirect:
1827
1828```text theme={null}
1829Stopped an OAuth request, which can hold secrets: https://auth.example.com redirected it to https://other.example.com. Ask the owner of https://auth.example.com to remove that redirect.
1830Stopped an OAuth request: https://auth.example.com redirected it more than 5 times. Ask the owner of https://auth.example.com to fix those redirects.
1831```
1832
1833**What to do:**
1834
1835* Ask whoever runs the first address, such as the MCP server's operator, to remove or fix the redirect. Then try again from `/mcp`.
1836
18211837### Refusing to send credentials to non-https token endpoint
18221838
18231839On the [v2 runtime](https://code.claude.com/docs/en/mcp.md#mcp-client-runtimes), Claude Code sends an [MCP OAuth](https://code.claude.com/docs/en/mcp.md#authenticate-with-remote-mcp-servers) token request only to a token endpoint served over HTTPS or at `localhost`, `127.0.0.1`, or `::1`. This message means the server's token endpoint is neither, so Claude Code stopped before sending the request. That happens after the browser sign-in, so the browser step succeeds first, and again whenever Claude Code refreshes the server's token.
from line 2219
22032219
22042220### Host not allowed in a cloud session
22052221
2206An outbound HTTP request from a cloud session or cloud scheduled task was blocked by the environment's network policy.
2222In a cloud session or cloud scheduled task, a `403` or a DNS error such as `ENOTFOUND` can mean that the requested host isn't on the [cloud environment's allowlist](https://code.claude.com/docs/en/cloud-environments.md#access-levels). To confirm, check the host against that list. A `403` with this header confirms the block, but not every blocked request's `403` has it:
22072223
22082224```text theme={null}
22092225HTTP 403
from line 2489
24732489`/context` shows this warning at the top of its output when the conversation has grown past the model's context window:
24742490
24752491```text theme={null}
2476Context exceeds the 200k-token limit by 94k tokens — run /compact or /clear to continue.
2477```
2478
2479After a `Context exceeds` warning, you don't need to run either command while [auto-compact](https://code.claude.com/docs/en/settings-reference.md#autocompactenabled) is on, which is the default:
2480
2481* **Auto-compact on**: send your next message. If it still fails with [`Prompt is too long`](#prompt-is-too-long), see that entry.
2482* **Auto-compact off**: in the session, run `/compact` if the warning names it, or `/clear` to start over. Until you run one, messages fail with `Context limit reached`, or `Prompt is too long` in `-p` output.
2483
2484When the limit you exceeded is a compaction window, such as the 200K boundary on 1M-context models, the warning reads differently. A compaction window can sit below the model's context window, so requests past it can still succeed.
2485
2486```text theme={null}
2487Context is 94k tokens past the 200k-token compaction window — run /compact to reduce usage.
2488```
2489
2490Both forms name `/clear` instead of `/compact` when you have set [`DISABLE_COMPACT`](https://code.claude.com/docs/en/env-vars).
2491
2492**What to do:**
2493
2494* **After a compaction-window warning**: in a multi-turn conversation, run `/compact` to summarize earlier turns and free space. To start fresh instead, run `/clear`.
2495* For more ways to reduce usage, see [Prompt is too long](#prompt-is-too-long)
2496
2497Before v2.1.216, `/context` showed usage above 100% with no warning line explaining what that meant or how to recover.
2498
2499### Request too large
2500
2501Th
2492Context exceeds th
No line in this hunk matches that.