Forumics logo Forumics
Issue 01

Back to issue

All Claude Code known issues

CLAIM C142 Supported 2026-11-16

GitHub issue #100377 in anthropics/claude-code, opened 2026-10-08 by moeedahmed, records a report that since about 2026-10-07 21:37 UTC, every claude.ai Project thread sent to run on the reporter's Mac fails to start ("Couldn't start"), with the claude remote-control server log showing "Error: CCR v2 worker registration failed for session cse_...: Request failed with status code 400" for each attempt; it fails on every server, both older 2.1.2xx builds and 2.1.292, while a fresh claude remote-control in a scratch folder on the same machine created its own session and registered its worker normally; the report was filed against macOS with claude remote-control servers run with --capacity 32 --permission-mode bypassPermissions --no-create-session-in-dir.

Verbatim Excerpts from Cited Records
“Since about 2026-10-07 21:37 UTC, every claude.ai Project thread sent to run on my Mac fails to start ("Couldn't start").”
— moeedahmed · anthropics/claude-code (issue 100377 opening body, What happens section) · 2026-10-08T02:32:41Z ·GitHub Issue ↗
“The `claude remote-control` server log shows, for each attempt: `Error: CCR v2 worker registration failed for session cse_...: Request failed with status code 400`”
— moeedahmed · anthropics/claude-code (issue 100377 opening body, What happens section) · 2026-10-08T02:32:41Z ·GitHub Issue ↗
“It fails on every server, both those started in late September (older 2.1.2xx builds) and those started on 2026-10-08 on 2.1.292.”
— moeedahmed · anthropics/claude-code (issue 100377 opening body, Scope section) · 2026-10-08T02:32:41Z ·GitHub Issue ↗
“A fresh `claude remote-control` in a scratch folder on the same machine and login, at 2026-10-08 01:25 UTC, created its own session.”
— moeedahmed · anthropics/claude-code (issue 100377 opening body, Local vs Project thread section) · 2026-10-08T02:32:41Z ·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 21 comments were read. moeedahmed (2026-10-08) reproduced with a clean setup and corrected the failure start to about 22:46 UTC on 7 Oct; rrva (2026-10-15) captured the 400 response body via mitmproxy, showing reason rc_child_session_ended with the message "this machine session was closed before it ran; start it again from the project", and showed the server considers the child session ended about 0.5 s after the ack while the heartbeat still says active; moeedahmed (2026-10-17) measured the work item reaching the bridge's poll about 15 s after the thread started, after the server had already closed the child session; moeedahmed (2026-10-23) isolated retained native Remote Control consents as a trigger, with starts failing at 50 retained consents and succeeding at 49 in controlled pairs, and later reported recurrences on 12 and 14 Nov cleared by ending finished sessions; rrva (2026-10-28) reported the consent explanation does not fit his account, where every Projects start fails even with 0 other consents live, and on 2026-11-15 confirmed ending all 233 Remote Control consents fixed it on both machines; jonathanglasmeyer (2026-11-04) showed only starts creating a new project thread fail while starts from an existing thread register fine, and on 2026-11-10 reported the problem gone for him. No maintainer fix and no retraction of the original report appear in the surveyed thread. The claim documents only the original report, not a verified current state. Falsification probe: If GitHub issue #100377 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn. Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by scripts/verify_claim_verbatim.py.