Remote Control: no host provenance in the session UI — can't tell which machine runs a session (add hostname to session info + disconnect message)
Not a duplicate of #57361 / #58665 / #60790 — those report disconnect/resume failures themselves (all closed). This issue is about the missing information that makes that class of incident expensive: the UI never tells you which machine hosts a session's worker. Sibling of #64748 (per-message provenance); this is per-session host provenance.
Setup: 2 machines × 2 accounts, each running claude remote-control on pinned config dirs (CLAUDE_CONFIG_DIR), plus desktop-app local sessions; sessions viewed from the mobile app / desktop app.
Problem: RC auto-generated session names default to a hostname prefix (--remote-control-session-name-prefix), but once AI auto-titling renames the session, the host information disappears from the UI permanently. After that, nothing in the session view (header / info pane) identifies the hosting machine/environment.
Real incident (2026-07-02, CLI 2.1.197): a session showed "The bridged Claude Code process stopped responding mid-turn — check your terminal". Which terminal, on which machine? Identifying the host took ~30 minutes of cross-machine transcript/log/git-reflog forensics. Notably, the worker had actually survived and completed its turn (it kept pushing its results to the repo while the UI showed the error) — knowing the host before resending also matters to avoid double-executing a turn.
Requests:
- Show environment name + hostname persistently in the session header/info pane (not only in the create-session environment picker).
- Include the host machine name in the bridged-disconnect error message ("…stopped responding on iMac-3").
Environment: Claude Code CLI 2.1.197 (remote-control, launchd-resident), Claude desktop 1.17377.2, macOS 26.5; sessions viewed from iOS mobile app and desktop app.
Workaround we use: a SessionStart hook stamping hostname · config-dir · session-id into the first assistant reply, so the host survives in the scroll-back even after the bridge dies.