Remote Control: input silently dropped on all clients — messages appear sent but never arrive at local process (regression ~May 25)

Resolved 💬 2 comments Opened May 26, 2026 by RichyRich1970 Closed Jul 15, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Description

Remote Control stopped working approximately 24 hours ago (around May 25–26, 2026). Input sent from remote clients appears to submit
successfully on the client side but never arrives at the local Claude Code process. Output from the local process to remote clients
continues to work normally.

This is a regression — Remote Control has worked reliably for months on this setup.

## Environment

  • Claude Code version: 2.1.150
  • OS: Windows 11 Pro
  • Remote clients tested: Browser (session URL), Windows Desktop app, Android mobile app — all exhibit identical behavior

## Steps to Reproduce

  1. Start a Claude Code session
  2. Type /remote-control to activate remote session
  3. Open the session URL on any remote client (browser, desktop app, Android app)
  4. Type a message and submit (Enter, Ctrl+Enter, or send button)
  5. Message appears sent on the client side
  6. Message never appears in the local CLI process — no response, no echo, nothing

## Expected Behavior

Messages sent from remote clients should arrive at and be processed by the local Claude Code process.

## Actual Behavior

Messages appear to send successfully on the client side (UI shows the message as submitted) but the local CLI process never receives
them. The relay appears to be forwarding outbound messages (local → client) but silently dropping inbound messages (client → local).

## What I've Tried

  • Hard refreshed all remote clients
  • Disconnected and started a completely fresh /remote-control session
  • Ran claude auth logout then claude auth login to get fresh credentials
  • Started a brand new Claude Code session after re-auth
  • Tested on three different clients (browser, Windows desktop app, Android app) — all identical behavior

None of the above resolved the issue.

## Notes

  • This is NOT the known Windows Enter key issue (#44537) — Ctrl+Enter also does not work
  • Output direction (local process → remote clients) continues to work correctly
  • The bidirectional failure on input only, across all clients, after months of working, suggests a server-side relay regression on the

inbound path

What Should Happen?

Command should show up in CLI and execute

Error Messages/Logs

None - just doesn't show up in remote session CLI

Steps to Reproduce

## What I've Tried

  • Hard refreshed all remote clients
  • Disconnected and started a completely fresh /remote-control session
  • Ran claude auth logout then claude auth login to get fresh credentials
  • Started a brand new Claude Code session after re-auth
  • Tested on three different clients (browser, Windows desktop app, Android app) — all identical behavior

None of the above resolved the issue.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.150

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_

View original on GitHub ↗

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