[BUG] CLI permission prompts not visible in remote session (web/desktop client)

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 running Claude Code via /remote and monitoring the session through the web or desktop client, the CLI sometimes stops and waits at an interactive prompt (e.g. "Do you want to proceed? 1. Yes / 2. No").

The remote viewer has no way of knowing this has happened — the session just appears frozen/idle with no indication that input is required.

What Should Happen?

Expected behavior:
The remote viewer should see that the CLI is waiting for input, ideally with the ability to respond, or at minimum a visible status indicator.

Actual behavior:
The session appears completely idle. There is no way to tell it is blocked on a prompt.

Workaround:
Using --dangerously-skip-permissions avoids the issue by bypassing all prompts, but this is not always desirable.

Environment: Claude Code CLI with /remote sharing, monitored via web and desktop client.

Error Messages/Logs

Steps to Reproduce

1. Start a Claude Code session with /remote
2. Monitor the session from the web or desktop client
3. Claude reaches a bash command that triggers a permission prompt
4. CLI pauses and waits for input
5. The web/desktop client shows no indication of the paused state

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

latest

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_