Follow Discord
Sweep 30 Oct 2026 · 01:02Z Build v2.1.314 532 read Stable v2.1.308 Latest v2.1.314 Next v2.1.314 Feeds RSS JSON llms.txt llms-full.txt Unofficial
One change · claude-code

Error reference changederrors

Nearest release: v2.1.314, published 4 hours after 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 29 Oct 2026 19:44 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 29 Oct 2026 20:07 UTC.

Upstream edited
Recorded here
Lines+7added
Lines−1removed
From line 273 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits207to this page, all time

### Can't restart while work is running or Remote Control is connected

The whole hunk

from line 273, old and new numbered
/
lines

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 273
273273| `Windows reported an error (EBADF) when Claude Code read this session's transcript file` | [Command-line errors](#windows-reported-an-error-ebadf) |
274274| `Cannot switch renderers in this session` | [Command-line errors](#cannot-switch-renderers-in-this-session) |
275275| `Cannot switch renderers while work is running in the background` | [Command-line errors](#cannot-switch-renderers-in-this-session) |
276| `Can't restart while work is running in the background — wait for it to finish (or stop it via /tasks), then try again.` | [Command-line errors](#cant-restart-while-work-is-running-or-remote-control-is-connected) |
277| `Can't restart while Remote Control is connected. To use the installed version, exit and start Claude Code again, then run /resume.` | [Command-line errors](#cant-restart-while-work-is-running-or-remote-control-is-connected) |
276278| `Claude Code couldn't restart` | [Command-line errors](#claude-code-couldnt-restart) |
277279| `Couldn't open Claude Desktop` | [Command-line errors](#couldnt-open-claude-desktop) |
278280| `Failed to open Claude Desktop. Please try opening it manually.` | [Command-line errors](#couldnt-open-claude-desktop) |
from line 856
854856 
855857### The prompt to confirm went unanswered
856858 
857If your account requires the [Fable usage-credits consent](https://code.claude.com/docs/en/model-config.md#fable-and-usage-credits), Claude Code asks you to confirm before a Fable request bills usage credits. When the consent prompt closes with nobody answering it, Claude Code ends the turn with one of these messages:
859When the [Fable usage-credits consent prompt](https://code.claude.com/docs/en/model-config.md#fable-and-usage-credits) closes with nobody answering it, Claude Code ends the turn with one of these messages:
858860 
859861```text theme={null}
860862Fable limit reached · continuing on Fable 5.1 uses usage credits, and the prompt to confirm went unanswered — nothing was sent · answer it where this session is running, or /model to change
from line 2511
25092511**What to do:**
25102512 
25112513* If you maintain the server, shorten the tool's name.
2512* If the server is in your [MCP configuration](https://code.claude.com/docs/en/mcp.md#mcp-installation-scopes), give it a shorter name there, such as `db` in place of `analytics-database`. Then update what refers to the server or its tools by the old name, such as [permission rules](https://code.claude.com/docs/en/permissions.md#mcp) and [hook match
2514* If the server i
Feedback