Remote control: bare /effort renders nothing in the web UI (selector self-cancels), so a session's current effort is unreadable

Status Open
Maintainer reply None cached
Activity 1 comment · opened Jul 17, 2026

Environment

  • Claude Code v2.1.212 on Linux (headless Hetzner server)
  • Session started via the remote-control bridge (entrypoint: claude-vscode), driven from the claude.ai/code web UI

Steps to reproduce

In a remote-control panel in the claude.ai/code web UI, type /effort with no argument.

Expected

Show the current effort level (in the TUI this opens a selector with the current level highlighted).

Observed

Nothing is shown in the web UI. The local session transcript records the command resolving to <local-command-stdout>Cancelled</local-command-stdout> — the interactive selector evidently cannot render over the bridge and self-cancels.

/effort <level> with an argument works fine and its confirmation text is relayed to the web UI.

Impact

There is no way to verify a remote-control session's actual effort level from the web UI at all — only blind writes via /effort <level>. It is also not inspectable machine-side (~/.claude/sessions/*.json records pid/cwd/bridge id but no effort), so when the web panel's effort picker shows a suspect value (see companion issue about panels resetting to Medium), there is no way to check what the session is actually running at.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗