Remote Control toggle spawns a hidden peer session, and SendFeedback tool unavailable in Remote-Control-linked sessions
While testing Remote Control in Claude Code (VS Code extension, project session), I ran into two related issues:
1. Toggling Remote Control off/on silently creates a new peer session
I disabled and re-enabled Remote Control mid-conversation. The chat thread I was looking at stayed visually continuous — same messages, same context — but behind the scenes a separate session was created (auto-named with a random adjective-noun name in the UI), alongside other Remote-Control-related peer sessions in an idle/offline state.
There was no indication in the UI of why this new session was created, and Claude itself had no way to inspect the cause — it could only see (via its session-listing tool) that the peer session existed, not why the toggle triggered it.
Steps to reproduce:
- Start an interactive Claude Code session in a project.
- Enable Remote Control.
- Use it normally from another device.
- Disable Remote Control, then re-enable it.
- Observe: a new peer session appears (random auto-generated name) even though the original chat thread looks unchanged/continuous.
Expected: Either the toggle should not create a new session at all, or the UI should clearly indicate that a new session was created and why (e.g. "reconnected as a new session because X").
2. Feedback tool disabled in this session
When trying to report the above issue directly through Claude Code's built-in feedback mechanism, the tool responded that it "is not enabled in this session." Claude could not explain why (no visibility into which tools are gated per session type), and had to fall back to telling me to file this manually on GitHub instead.
Question: Is the feedback tool intentionally disabled for sessions connected via Remote Control, or is this itself a bug?
---
🤖 Generated with Claude Code