## Summary With Remote Control connected via `/rc`, the local interactive terminal session feels noticeably slower to respond. Immediately after disconnecting with `/remote-control`, responses become fast again. ## Steps to reproduce 1. Start `claude` (interactive) 2. Run `/rc` to connect Remote Control 3. Chat locally in the terminal — responses are noticeably delayed 4. Run `/remote-control` to disconnect (`Remote Control disconnected.`) 5. Responses are fast again ## Expected No perceptible

Remote Control (/rc) makes local interactive session noticeably slower

Status Open

Reported on v2.1.270

Maintainer reply None cached

Activity 0 comments · opened Sep 12, 2026

Summary

With Remote Control connected via /rc, the local interactive terminal session feels noticeably slower to respond. Immediately after disconnecting with /remote-control, responses become fast again.

Steps to reproduce

Start claude (interactive)
Run /rc to connect Remote Control
Chat locally in the terminal — responses are noticeably delayed
Run /remote-control to disconnect (Remote Control disconnected.)
Responses are fast again

Expected

No perceptible latency penalty on the local session while Remote Control is connected.

Environment

Claude Code 2.1.270
macOS (Darwin 25.6.0), zsh
remoteControlAtStartup not set (RC was enabled manually with /rc)

Notes

Docs say the WebSocket transport keeps latency minimal, but the local slowdown was consistent across the session and disappeared the moment RC was disconnected.

View original on GitHub ↗