[BUG] Claude Projects: "Allow Claude to connect to your device in this thread" card on every cloud thread start; Allow spins, then fails with worker_busy_gave_up
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
What's Wrong?
Since about 2026-10-05, every new cloud thread in my private Claude Project gets an "Allow Claude to connect to your device in this thread" card a couple of seconds after it starts. Nobody asked for it. The thread never calls connect_device or any device or Remote Control tool, and nothing in the repo asks for one (AGENTS.md, CLAUDE.md, .claude/settings.json, hooks, skills, project instructions).
If I tap Allow, the button spins for minutes and the link then fails. The thread itself keeps working in the cloud, so the card is noise at best and a broken flow at worst.
Evidence (the thread's own message records)
- Two seconds after the session was created:
{"kind":"thread_device_link","phase":"proposed","basis":"thread_start","text":"Connect your device to this thread? ..."}
- I tapped Allow at 14:20:47 UTC:
{"kind":"thread_device_link","phase":"linking","text":"Allowed. Connecting your device."}
- At 14:24:35 UTC, while the thread was mid-turn:
{"kind":"thread_device_link","phase":"failed","failed_reason":"worker_busy_gave_up","text":"Your device could not be connected."}
The session tags do not include config:claude-code-device-bind, so this looks different from #99688, though it may share a cause.
Setup
- macOS, Claude desktop app, MacBook Pro M1.
- The desktop app serves Remote Control for three folders. One of them is the project's repo folder and is preapproved for the project, for local threads. That may be why every thread start proposes a device link.
- The affected threads are plain cloud threads.
What Should Happen?
- A cloud thread that never asked for the device should not get a device-link card on every start, or the card should be opt-in per project.
- If I allow it, the link should not give up because the worker is busy. It should wait for the turn boundary or retry instead of spinning and failing.
Related
#99688, #99858
What Should Happen?
What Should Happen?
- A cloud thread that never asked for the device should not get a device-link card on every start, or the card should be opt-in per project.
- If I allow it, the link should not give up because the worker is busy. It should wait for the turn boundary or retry instead of spinning and failing.
Related
#99688, #99858
Error Messages/Logs
Steps to Reproduce
Send a message to coordinator asking for something, the thread he creates now shows this persmission dialog.
Claude Model
Not sure / Multiple models
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
Claude 2.26454.0 (98e3cc) 2026-10-06T05:51:15.000Z
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Other
Additional Information
<img width="1316" height="306" alt="Image" src="https://github.com/user-attachments/assets/1a29bb77-dcf9-4fa1-b6e5-4c451ad6e005" />
<img width="1316" height="306" alt="Image" src="https://github.com/user-attachments/assets/b1afa9b8-cfe7-434a-a288-9f2f7dfea2e1" />