Remote control commands not delivered while /status screen is open (flush on close)

Resolved 💬 2 comments Opened May 11, 2026 by saarantras Closed Jun 10, 2026

Summary

When the /status screen is open in the CLI TUI, messages sent from the
web app via Remote Control are not delivered to the session. They remain
queued and fire only after /status is dismissed.

Repro

  1. Open Claude Code in a terminal, connect Remote Control (/remote-control).
  2. Run /status to open the status screen.
  3. From the web app, send a message to the session.
  4. Observed: no response; the assistant does not appear to receive the

message while /status is open.

  1. Close /status.
  2. Observed: queued message(s) are processed and a response is generated.

Confirmed reproducible on a live session today.

Expected

Remote Control messages should be delivered to the session regardless of
whether a local TUI modal like /status is open -- the modal is a local
display surface and should not gate inbound RC traffic.

Environment

  • Claude Code 2.1.138
  • Platform: darwin (macOS)
  • Remote Control source: web app (claude.ai/code)

Notes

  • Distinct from #38498 (outbound modal relay to channels) and #49765

(resume-summary modal hard-blocking headless --rc sessions). Here
the modal is /status, RC is the web app, and the queue does flush
on close -- so this is a delivery-gating bug, not a hard deadlock.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗