Remote Control (mobile): stale session repo label after directory change; no way to start a new local session on a paired device

Two Remote Control / mobile session bugs, both reproduced today (2026-09-04).

1. Session repo label goes stale after a mid-session working-directory change, and never recovers.

A session originally created in incendiosoftware/FIREme had its working directory changed mid-conversation to a different, unrelated local repo (E:\SignMe, remote incendiosoftware/SignMe). Verified directly in the running session: pwd → /e/SignMe, git remote -v → incendiosoftware/SignMe. Despite this, the mobile app's Sessions list (Code tab) still shows this session's subtitle as incendiosoftware/FIREme, hours later, with no refresh mechanism I could find (no pull-to-refresh fix, no reconnect fix). This is actively misleading — a user scanning the session list has no way to tell which repo a session is actually operating on. At minimum this needs a live refresh; ideally the label should be derived from the current working directory/remote, not cached from session creation.

2. Mobile "+ New session" cannot start a new local session on an already-paired Remote Control device.

Tapping "+ New session" in the mobile Code tab only offers "Choose environment" (cloud sandbox) and "Connect GitHub" (clones a repo into a cloud sandbox). There is no option to start a new session on a device that's already paired and connected via Remote Control, even though that device is visible and online in the same app. This means every additional local session — with real laptop capabilities (SSH keys, local files outside a git repo, deploy scripts) — requires physically going to the laptop and opening a terminal. For a mobile-first Remote Control workflow, not being able to launch a new local session on a device you're already remote-controlling is a significant gap, not a minor one. Expected: a device picker in "+ New session" (or a "New local session" action per device in the Devices list) that lets mobile spawn a new claude process on the paired machine, in a folder the user specifies or a recent-projects list.

Both issues make Remote Control materially less useful for anyone running multiple concurrent projects from a phone.

---
Filed via gh on behalf of the reporting user (Claude Code session).