Remote Control session list is misleading: unopenable history + meaningless auto-generated names

Status Open
Reported on v2.1.284
Maintainer reply None cached
Activity 0 comments · opened Sep 30, 2026

Problem
In the VS Code extension's Session Manager, the "Web" tab lists Remote Control
sessions that ran on other devices, but this list is functionally broken for
its apparent purpose (browsing/resuming past cross-device sessions):

  1. Clicking a past (no longer live) Remote Control session that originated on

a different machine fails with: "This Remote Control session's history
can't be opened here. Continue it on claude.ai, or in the terminal, editor
or app where it was started." This happens even though the session is
listed as if it were openable.

  1. When the local machine has no matching log fragment for that session, the

list shows a meaningless placeholder name (hostname + random word pair,
e.g. "my-laptop-jaunty-iverson") instead of the real conversation title,
with no indication it's a placeholder. This makes it impossible to tell
sessions apart.

Why this is confusing
Remote Control appears designed only for live, real-time steering of an
in-progress session from another device -- history isn't persisted
server-side. But the UI presents finished sessions in a list that looks
browsable/resumable, with no visual distinction between "can be opened" and
"dead end, cloud has no content."

Suggested fix

  • Either make Remote Control history genuinely resumable across devices, or
  • Clearly mark list entries that cannot be opened (e.g. gray out / label

"not available on this device"), and

  • Don't fall back to random placeholder names -- either show no title, or

hide entries with no real title/content, rather than a confusing codename.

Environment

  • Claude Code VS Code extension 2.1.284, Windows 11

View original on GitHub ↗