[BUG] remote-control slow, unresponsive

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?

It's just slow and unresponsive.

What Should Happen?

I should be able to run /remote-control from a claude code session, tap claude on my phone, tap code, and tap the session, and interact real-time.

Error Messages/Logs

No such output, just incredibly slow and unusable.

Steps to Reproduce

Run claude code on a highly-optimized network, using openwrt devices.
Claude Code has done some of the optimization. Brought it in to look at the setup about 50% of the way into working on it.

Network does not allow inbound unsolicited ipv6 connections due to carrier restrictions, so (i think that's what) also breaks PMTUD. Many workarounds later, and ipv6 works correctly. I doubt your remote control system requires anything other than both clients be connected to the claude back-end, and then the back-end is relaying the information back and forth. But it's extremely slow. Actual connections to claude directly, from client to services, is fine. All other network performance is great. It's just isolated to this 'remote control' feature.

Just run claude code and then fire up /remote-control and try to control / communicate with it from your phone. Performance is terrible. Looking at both the laptop and the phone, I can send a message with the phone, and it sits in the que for well over 30 seconds before the claude code session on the laptop ever sees it. There's clearly a relay issue where the messages are being held-up inbetween. Neither the phone nor the laptop itself have any communication problems.

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.185

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

WSL (Windows Subsystem for Linux)

Additional Information

non-working 'feature'. please fix.