Error reference changederrors
Nearest release: v2.1.267, published under an hour after 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+47added
Lines−22removed
From line
109
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 109, 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 109
109109| `Unable to resize image` | [Request errors](#unable-to-resize-image) |
110110| `PDF too large` / `PDF is password protected` | [Request errors](#pdf-errors) |
111111| `Extra inputs are not permitted` | [Request errors](#extra-inputs-are-not-permitted) |
112| `API Error: 400 ... tools.N.custom.input_schema: JSON schema is invalid` | [Request errors](#tool-input-schema-is-invalid) |
112| `API Error: 400 ... tools.N.custom.input_schema: JSON schema is invalid` / `Property keys should match pattern` | [Request errors](#tool-input-schema-is-invalid) |
113113| `There's an issue with the selected model` | [Request errors](#theres-an-issue-with-the-selected-model) |
114114| `Model ... is not a recognized model id` | [Request errors](#model-is-not-a-recognized-model-id) |
115115| `Claude Opus is not available with the Claude Pro plan` | [Request errors](#claude-opus-is-not-available-with-the-claude-pro-plan) |
from line 207
207207| `EUNKNOWN: unknown error, uv_spawn` | [Background session errors](#eunknown-when-starting-a-background-session) |
208208| `EACCES: permission denied, posix_spawn` | [Background session errors](#eacces-when-starting-a-background-session) |
209209| `exited before it became reachable` | [Background session errors](#background-service-exited-before-it-became-reachable) |
210| `Claude Code is being updated by npm on this machine (still not runnable after 2 min, ...)` | [Background session errors](#eacces-when-starting-a-background-session) |
210211| `Claude Code process exited with code N` | [Wrapper and IDE errors](#claude-code-process-exited-with-code-n) |
211212| `Could not locate the Claude CLI on PATH` | [Wrapper and IDE errors](#could-not-locate-the-claude-cli-on-path) |
212213| `Restored the code, but skipped N files` | [Rewind warnings and errors](#restored-the-code-but-skipped-files) |
from line 714
713714Your apiKeyHelper script is failing · This usually means you need to re-authenticate with your provider · Run /status to see the script's error output
714715```
715716
717In [non-interactive mode](/docs/en/headless), stderr also carries the specific reason, prefixed with `apiKeyHelper failed:`.
718
716719Claude Code re-runs the script and retries the request up to two more times before showing this message, so the failure surfaces within three attempts. Before v2.1.208, Claude Code spent the full [retry budget](#automatic-retries) resending the request with the placeholder credential and then reported a generic `401` authentication error instead of the script failure.
717720
718721Running `/login` doesn't help here: the helper's output [takes precedence](/docs/en/authentication#authentication-precedence) over a saved login for as long as the setting is present.
from line 1610
16071610
16081611```text theme={null}
16091612API Error: 400 ... tools.N.custom.input_schema: JSON schema is invalid
1613API Error: 400 ... tools.N.custom.input_schema.properties: Property keys should match pattern '^[a-zA-Z0-9_.-]{1,64}$'
16101614```
16111615
1616The first form means the schema isn't valid JSON Schema draft 2020-12. The second means a top-level property name doesn't match the pattern the message quotes.
1617
16121618Claude Code [excludes MCP tools whose input schema would fail this validation](/docs/en/mcp#tools-with-invalid-input-schemas) when it loads a server's tools, so requests normally never include one.
16131619
16141620On a [deployment where flag fetching is off](/docs/en/env-vars#features-that-need-feature-flag-fetching), or on a machine whose flags have never arrived, Claude Code records in the server's log which tool would be rejected but sends it anyway, so this error can still occur.
from line 1992
19861992
19871993```text theme={null}
19881994The current directory no longer exists (it was deleted or moved). Start Claude Code from an existing directory.
1995error: The current working directory was deleted, so that command didn't work. Please cd into a different directory and try again.
19891996```
19901997
1998The cause and the fix are the same for both forms.
1999
19912000When Claude Code can't read the working directory for a different reason, such as a permissions change, the message names the error code instead: `Can't read the current directory (EACCES). Start Claude Code from a different directory.`
19922001
19932002**What to do:**
from line 2325
23162325
23172326### Failed to resume the conversation
23182327
2319Claude Code couldn't read or process the saved transcript for the session you selected from the [`claude --resume` picker](/docs/en/sessions#use-the-session-picker), so it ends the process rather than continue in a partially loaded state. The message includes the command to retry:
2320
2321```text theme={null}
2322Failed to resume the conversation.
2323Run claude --resume <session-id> to retry, or claude to start a new session.
2324```
2325
2326Claude Code exits with code 1 after showing the message. The `/resume` picker inside a running session reports `Failed to resume conversation` in the conversation instead, and your current session keeps running. Before v2.1.216, a failed resume from the `claude --resume` picker stayed on the `Resuming conversation…` spinner indefinitely instead of showing this message.
2327
2328**What to do:**
2329
2330* Run `claude --resume <session-id>` with the session ID from the message to retry
2331* If the retry fails again, run `claude` to start
2328Claude Code couldn't read
No line in this hunk matches that.