[DOCS] Remote Control docs omit pending permission prompts for viewers joining mid-session

Status Fixed / completed
Reported on v2.1.217
Maintainer reply None cached
Activity 1 comment · opened Jul 22, 2026 · closed Aug 16, 2026

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/remote-control

Section/Topic

The Connect from another device section and the explanation of permission prompts for connected viewers.

Current Documentation

The page currently says:

Repeated permission prompts: after you answer several permission prompts in a session, an Approve tool calls from your phone notification shows the session URL.

Under Connect from another device, it says:

When you connect, the device shows any subagents and workflows the session already has running in the background.

The page does not state whether a device that joins after a permission prompt or dialog appears can see and act on that already-pending request.

What's Wrong or Missing?

Claude Code v2.1.217 fixes Remote Control sessions so a viewer who connects after a permission prompt or dialog appeared can see the pending request. The current documentation covers notifications that invite a user to connect and the visibility of already-running subagents and workflows, but it does not describe the safety-critical permission state that is transferred to a newly connected viewer.

A user joining from a phone or browser cannot tell whether the remote session is waiting for approval, whether the prompt will appear after connection, or how to continue the blocked turn. This can make a working session appear idle or leave the user waiting at the terminal unnecessarily.

Suggested Improvement

Add a note to Connect from another device explaining that, as of Claude Code v2.1.217, a viewer who joins while a permission prompt or dialog is already pending sees that request in the remote interface. Document the available approve/deny or dismissal actions, what happens to the local session after the viewer responds, and whether the request remains visible to other connected viewers.

Cross-link the note to the general permission-prompt documentation and the mobile push-notification guidance so users can distinguish a pending action from an informational connection reminder.

Impact

High - Prevents users from using a feature

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/remote-control | 121-136 | Permission-related connection reminder and the state visible to a device joining an active session |
| https://code.claude.com/docs/en/permissions | 1-2 | General permission-prompt behavior to cross-reference from Remote Control |

Total scope: 2 pages should explain how pending permission state is handled for remote viewers.

The relevant release is Claude Code v2.1.217. The release entry is listed in the Claude Code changelog under version 2.1.217.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗