[DOCS] Remote Control docs omit session archival behavior when Claude Code exits

Open 💬 4 comments Opened Apr 17, 2026 by coygeek

Documentation Type

Missing documentation (feature not documented)

Documentation Location

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

Section/Topic

"Connect from another device" and "Limitations" session lifecycle details for Remote Control

Current Documentation

The docs currently say:

Once a Remote Control session is active, you have a few ways to connect from another device: * Open claude.ai/code or the Claude app and find the session by name in the session list. Remote Control sessions show a computer icon with a green status dot when online.

And later:

* Local process must keep running: Remote Control runs as a local process. If you close the terminal, quit VS Code, or otherwise stop the claude process, the session ends.

The docs explain that the session ends when the local process exits, but they do not explain what happens to that Remote Control session in the claude.ai/code session list afterward.

What's Wrong or Missing?

Claude Code v2.1.113 fixed Remote Control sessions not being archived when Claude Code exits, which means session archival on exit is part of the intended session lifecycle.

The current Remote Control docs stop at "the session ends" and do not document that exiting Claude Code should archive the Remote Control session instead of leaving a stale entry behind in the session list. That leaves an important gap for users who monitor local sessions from claude.ai/code or the mobile app and need to know what state to expect after the host process exits.

Suggested Improvement

Add one short lifecycle note to https://code.claude.com/docs/en/remote-control, ideally in the "Limitations" section or immediately after the session-list guidance.

Suggested content outline:

When the local Claude Code process exits, the Remote Control session ends and is archived from the active session list. If you want to continue working, start a new Remote Control session from the CLI or VS Code.

This would make the session-list behavior explicit and align the docs with the v2.1.113 fix.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/remote-control | Primary Remote Control lifecycle and limitation details |
| https://code.claude.com/docs/en/claude-code-on-the-web | Session list and archive behavior reference for claude.ai/code |

Total scope: 2 pages affected

Source: Changelog v2.1.113

Exact changelog entry:

Fixed Remote Control sessions not being archived when Claude Code exits

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗