Skip to content

[BUG] Remote control (/rc) not supported in VS Code extension #28951

Closed

Description

@arigon

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • 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

  1. Enable remote control by default in Claude Code CLI configuration
  2. Open a terminal and run claude — remote control session is created as expected
  3. Open the Claude Code VS Code extension panel
  4. Note that no remote control session is created
  5. 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

Activity

  1. github-actions commented on Feb 26, 2026

    @github-actions

    Found 3 possible duplicate issues:

    1. [BUG] VS Code Extension has an incomplete slash command list compared to the CLI version #8590
    2. bypassPermissions mode not working in VS Code extension #20536
    3. Add /rename slash command support in VSCode extension #24472

    This issue will be automatically closed as a duplicate in 3 days.

    • If your issue is a duplicate, please close it and 👍 the existing issue instead
    • To prevent auto-closure, add a comment or 👎 this comment

    🤖 Generated with Claude Code

  2. adfdev commented on Feb 27, 2026

    @adfdev

    Up

  3. rares-munteanu commented on Feb 27, 2026

    @rares-munteanu

    up

  4. felepeg commented on Feb 28, 2026

    @felepeg

    Up

  5. SushiZZ commented on Feb 28, 2026

    @SushiZZ

    up

  6. themfinger commented on Feb 28, 2026

    @themfinger

    up

  7. aanoyatis commented on Mar 1, 2026

    @aanoyatis

    up

  8. LeroyK commented on Mar 1, 2026

    @LeroyK

    Up

  9. jision commented on Mar 1, 2026

    @jision

    up

  10. ghost-ng commented on Mar 1, 2026

    @ghost-ng

    same

  11. gmyuval commented on Mar 1, 2026

    @gmyuval

    Same thing and also on Windows

  12. 25 remaining items

  13. jbastruz commented on Mar 13, 2026

    @jbastruz

    up !!!

  14. AlexHors commented on Mar 14, 2026

    @AlexHors

    Up! This is a great feature, but needing to switch to cli mid-session is really troublesome.

  15. Bokazan commented on Mar 14, 2026

    @Bokazan

    Up. Perhaps use an agent to fix this. ;)

  16. Ves40 commented on Mar 14, 2026

    @Ves40

    Up

  17. andrade-igor commented on Mar 14, 2026

    @andrade-igor

    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.

  18. mkull commented on Mar 15, 2026

    @mkull

    Uppity up up

    Biggest pain point / opportunity with claude code atm

  19. tommycarstensen commented on Mar 18, 2026

    @tommycarstensen

    Up. Urgent. Please have an agent fix this ASAP. Or a human. Whichever is faster.

  20. sethatwood commented on Mar 19, 2026

    @sethatwood

    +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.

  21. Maxsamenonlinemarketing commented on Mar 19, 2026

    @Maxsamenonlinemarketing

    Up

  22. rexynexus commented on Mar 19, 2026

    @rexynexus

    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.

  23. arigon commented on Mar 20, 2026

    @arigon
    Author

    it works with /remote-control

    Image
  24. my-lalex commented on Mar 25, 2026

    @my-lalex

    It seem that the issue is still there, using /remote-control on v2.1.83

    2026-03-25 13:42:33.391 [info] From claude: 2026-03-25T13:42:33.391Z [DEBUG] [bridge:repl] Skipping: bridge not enabled
    
  25. github-actions commented on Apr 2, 2026

    @github-actions

    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.

  26. locked as resolved and limited conversation to collaborators on Apr 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:idebugSomething isn't workingplatform:macosIssue specifically occurs on macOSplatform:vscodeIssue specifically occurs in VS Code

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions