claude agents TUI: ←-to-detach is undiscoverable, mode-dependent (empty input only), and Esc interrupts instead of going back

Environment

• Claude Code v2.1.207, macOS (Darwin 25.5.0), claude agents dashboard (agent view)

Problem

In the claude agents TUI, the key to detach from a session and return to the session list is the left arrow — but only when the message input box is empty. If any text has been typed, the same key silently switches roles and moves the text cursor instead.

This makes the single most common navigation action (going back to the list) effectively undiscoverable:

1. There is no on-screen hint that ← detaches, and no indication of which "mode" the key is currently in (navigate vs. edit text).
2. A user who has typed even one character gets no feedback about why ← "stopped working" — it just behaves as a text-editing key.
3. Esc — the key most users try first for "go back" — instead interrupts the running agent, which is a destructive surprise in this context.
4. The only in-product documentation of these bindings that a new user is likely to encounter is... asking the agent itself, or ? (which is itself undocumented on screen).

Real-world result: a user attached to a background session could not figure out how to get back to the dashboard, and had to ask the model inside the session to explain the UI to them.

Suggestions (any subset would help)

• Show a persistent one-line key hint in the dashboard/session footer (← back · → attach · Space peek · Ctrl+X stop · ? help), like lazygit/k9s do.
• Add an unambiguous detach binding that never collides with text editing (e.g. Ctrl+Q, or make Esc on an empty input detach instead of no-op).
• When ← is pressed with a non-empty input, flash a hint ("clear input to go back, or press <key>").

Steps to reproduce

1. claude agents, attach to any session with →
2. Type a character into the input box
3. Press ← repeatedly: cursor moves, nothing hints the navigation function exists
4. Press Esc: interrupts the agent instead of going back