Mobile/web session list: surface hostname (and cwd) — same-repo multi-machine fleets are indistinguishable

Summary

In the Claude mobile app (and claude.ai session list), Claude Code sessions from multiple machines running the same repo are visually indistinguishable. The list shows the session title plus an owner/repo row — but for a fleet where every machine has a clone of the same repository under the same account, that row is identical for every session. There is no info button, detail view, or secondary metadata that reveals which machine a session is running on.

Environment

• Several headless Linux boxes + a Mac, all running Claude Code sessions inside tmux
• Every machine has a clone of the same repo at the same path (~/<same-repo>), same Claude account
• Sessions surfaced on mobile via remote control (/remote-control); they show up with the computer icon + online indicator as documented

Problem

The session list's differentiator row (<user>/<repo>) is the one field guaranteed to be the same for every session in this setup — same account, same repo everywhere, by design. Meanwhile the actual differentiator (hostname / machine) is shown nowhere:

• No session detail / info view in the app exposes the host
• Auto-generated names include a hostname prefix, but explicitly renamed sessions (which we want — descriptive names are good) lose that signal
• Result: five online sessions named for their tasks, and no way to tell which box each one is on without ssh-ing around and matching tmux sessions by hand

Workarounds tried

• /rename with a machine prefix (s1·extraction chain, s2·graph spike) — works, but spends title space on what should be metadata, and relies on every session/operator remembering the convention
• CLAUDE_REMOTE_CONTROL_SESSION_NAME_PREFIX — only affects auto-generated names, not explicit ones

Request

Any of these would solve it (in preference order):

1. Show hostname (and ideally cwd) as secondary metadata in the session list row, e.g. under or beside the repo name
2. A session detail/info view (tap-through or long-press) exposing hostname, cwd, repo, and start time
3. Make the secondary row configurable (e.g. a session list subtitle setting: repo | hostname | cwd)

Multi-machine home-lab and fleet setups where every node runs the same repo are exactly the case where the current design gives zero signal — and they're also exactly the users running many concurrent remote-control sessions.