[BUG] Remote control (/rc) not supported in VS Code extension
Resolved 💬 49 comments Opened Feb 26, 2026 by arigon Closed Mar 20, 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?
The Claude Code VS Code extension does not support the /rc (remote control) feature. When remote control is enabled by default in the CLI configuration, it is ignored when the CLI is invoked through the VS Code extension. The extension only exposes a subset of slash commands and /rc is not among them.
What Should Happen?
The VS Code extension should support remote control sessions, either via the /rc slash command or by respecting the CLI's default remote control configuration. Since the extension already uses the CLI under the hood, remote control functionality should be passed through to the extension.
Error Messages/Logs
Steps to Reproduce
- Enable remote control by default in Claude Code CLI configuration
- Open a terminal and run claude — remote control session is created as expected
- Open the Claude Code VS Code extension panel
- Note that no remote control session is created
- Try typing /rc in the extension — command is not available
Claude Model
Opus
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
2.1.59 (Claude Code)
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Cursor
Additional Information
_No response_
49 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Up
up
Up
up
up
up
Up
up
same
Same thing and also on Windows
up
Up!
up! were waiting
Up
Up!
Up
Please fix this.
Up
Up
up
All the way up!
Up again.
Up
up
up
We're goin' up, up, up, it's our moment!
were still waiting and waiting and waiting
up
Up. I really want this
up
Up
up
Up
All my ups are belong to you
up!!!
up !!!
Up! This is a great feature, but needing to switch to cli mid-session is really troublesome.
Up. Perhaps use an agent to fix this. ;)
Up
Adding my voice here — I opened #30905 as a feature request before finding this issue.
My main use case: I manage a multi-agent system (OpenClaw) from my phone via Telegram. Being able to use Remote Control with the VS Code chat mode would let me seamlessly continue coding sessions from mobile without switching to terminal mode.
The VS Code chat experience is significantly better for inline diffs and editor integration. Limiting RC to terminal-only means losing that workflow entirely when going mobile. Would love to see this supported.
Uppity up up
Biggest pain point / opportunity with claude code atm
Up. Urgent. Please have an agent fix this ASAP. Or a human. Whichever is faster.
+1. We use the VS Code extension exclusively. Switching to a terminal session just for Remote Control access is not a viable workaround. This would be a big quality-of-life improvement for extension-first users.
Up
For the good of the folks who upped this in the past day, and those in the thread who might not yet know: this was a feature released with 2.1.79. Remote to your hearts' content.
it works with /remote-control
<img width="221" height="129" alt="Image" src="https://github.com/user-attachments/assets/4e1ca160-88ba-4335-a571-e19e973a8f03" />
It seem that the issue is still there, using /remote-control on v2.1.83
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.