[Feature Request] Remote Control UI needs session state indicators, interactive prompts, and multi-account support

Bug Description
Feature Request: Remote Control UI Needs Richer Session Management and Interaction Support

From: Jordan Dea-Mattson
GitHub: @jordan-of (OrdinaryFolk), @jordandm (personal)
Email: jordan-of@users.noreply.github.com
Related: #36909 (Session naming and state indicators), #36017 (Multi-account switching on Claude Mobile)

Context

Remote control is a great feature — continuing local sessions from a phone is exactly the right direction. But the current mobile/web UI has several gaps that limit its usefulness for power users
managing multiple concurrent sessions.

These findings are from hands-on testing with 5 active sessions via the Claude iOS app, connecting to Claude Code v2.1.81.

Finding 1: Session Status is Minimal and Not Accessible

The session list shows two groupings — "Idle" and "Archived" — with a static blue dot per session. There is no way to distinguish between sessions that are:

• Working — actively processing, running tools
• Waiting for input — blocked on a permission prompt or question
• Idle — finished and ready for the next prompt

With 5 active sessions, I have to tap into each one to find out which needs attention. The dot doesn't change color or state. The "Idle" header applies to all active sessions regardless of their
actual state.

Accessibility concern: Any status indicator system must not rely on color alone. Approximately 8% of men and 0.5% of women have some form of color vision deficiency — roughly 1 in 12 male users
cannot reliably distinguish red from green, or blue from yellow. Status indicators need distinct shapes combined with colors: a filled circle for working, an open circle for idle, a triangle or
exclamation mark for waiting on input. Color adds information; shape conveys it. This is a WCAG 2.1 requirement (1.4.1 Use of Color) and should be designed in from the start, not retrofitted.

This connects to #36909 — the same state indicators requested for the terminal statusline would be valuable here.

Finding 2: Interactive Prompts Don't Render

When the agent uses AskUserQuestion (a structured prompt with selectable options), the remote UI renders it as plain text — the question and options are visible but there are no tappable buttons
or selection UI. The user can only respond by typing in the text field.

This is a usability gap — the whole point of AskUserQuestion is structured input with predefined options. On the terminal, you get arrow-key navigation and Enter to select. On mobile, you get a
wall of text.

More critically: if permission prompts (approve/deny for tool use) also don't render as interactive elements in the remote UI, this could explain the ExitPlanMode denial bug we reported separately
— the agent is waiting for approval, the remote UI isn't showing the approval button, and the permission times out as "denied."

Finding 3: Account/Workspace Switching

The remote UI shows sessions from one account. There's no way to switch between accounts or workspaces. For users with multiple Claude accounts (personal + organization), this means managing
sessions across accounts requires logging out and back in.

Already filed as #36017 but worth noting here as part of the remote control experience.

Finding 4: Input Field Placeholder Text

The text input field shows "Add feedback..." as placeholder text. This is confusing — it reads like a feedback form, not a chat input. Expected: "Type a message..." or "Send a message to
Claude..." or simply empty with a send button.

Finding 5: Session Subtitle Shows Internal Path

Each session's subtitle shows the machine hostname and a truncated worktree path: monofolk · MB-Air-13-M2-2022:transcri.... This is internal infrastructure detail that isn't useful for session
identification. The repo name alone (ordinaryfolk/monofolk) or the session name would be more meaningful.

What's Really Needed

1. Clear and consistent indicators of session/agent state across CLI, Desktop, and Remote.

I need to know, at a glance, for each session/agent:

• Actively Working — the agent is processing, running tools, generating output
• Waiting on Me — the agent is blocked on my input (permission prompt, question, approval)
• Available for its next task — the agent has finished and is ready

This must be consistent across all surfaces — the terminal statusline, the Desktop app, and the Remote Control UI should show the same state the same way. And the indicators must be accessible:
distinct shapes combined with colors, not color alone. A filled circle, an open circle, and a triangle are distinguishable regardless of color vision. A green dot, yellow dot, and red dot are not.

1. Ability to move across Accounts and Workspaces with minimal friction.

I use Claude Code on personal projects with my own…
Note: Content was truncated.