AskUserQuestion dialogs in Remote Control sessions only render on the desktop, not on mobile / claude.ai
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?
When a session followed through Remote Control calls AskUserQuestion, the dialog renders only in the desktop app. The phone shows nothing to answer, so the session waits until I go to the PC.
Workaround: Tell the session to ask questions as plain text instead of using AskUserQuestion.
What Should Happen?
The question and its options appear on the device where I'm following the session (phone), or on every connected client.
Error Messages/Logs
Steps to Reproduce
- In the desktop app, start a local Code session and turn on Remote Control.
- From that session, spawn a child session with
spawn_task, then click the chip on the desktop. The child session connects to Remote Control (remoteControlActive: true). - Follow the child session from the phone through Remote Control.
- The child session calls
AskUserQuestion.
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
Claude desktop app 2.26454.2.0 (Windows), Claude Android app 1.261005.20
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Other
Additional Information
Environment
- Claude desktop app 2.26454.2.0, Code tab, Windows 11 Pro (10.0.26200)
- Mobile: Claude Android app 1.261005.20 via Remote Control
- Model: claude-opus-5-5
- No terminal involved: the session runs in the desktop app's Code tab, so "Other" is selected above.
Possibly related: #33625 (same symptom with the CLI + iOS: "awaiting input" on mobile but the question UI is missing) and #34947 (AskUserQuestion not forwarded to Claude Desktop). Filing separately because this reproduces now in the desktop app on Windows with a spawn_task child session; happy to close as a duplicate if it's the same root cause.
Also: From a Remote Control "hub" session I couldn't start new sessions. start_session wasn't in its tool list, so child sessions could only be launched through spawn_task chips, and those need a click on the desktop.