[BUG] /remote-control not showing up

Status Fixed / completed
Reported on v2.1.119
Maintainer reply None cached
Activity 5 comments · opened Apr 28, 2026 · closed May 5, 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?

/remote-control is showing as an unknown command

<img width="452" height="59" alt="Image" src="https://github.com/user-attachments/assets/01d6735f-d5e3-48db-bf66-9e5f4fd51ca5" />

<img width="906" height="132" alt="Image" src="https://github.com/user-attachments/assets/720f3676-7e45-450b-ab48-8157b6be1c22" />

What Should Happen?

I should be able to start a remote-control session from an existing session using the slash command.

Error Messages/Logs

Unknown command: /remote-control

Steps to Reproduce

  1. in exsiting session, use /remote-control
  2. Claude Code is up to date (2.1.119)
  3. mac mini M1 2020

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.119

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

5 Comments

github-actions[bot] · 5 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/53374
  2. https://github.com/anthropics/claude-code/issues/29796
  3. https://github.com/anthropics/claude-code/issues/28322

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

jkhalaf-gr · 5 months ago

I think you can only get remote control if you pass it as a flag when you first start Claude Code. Like this:

claude --remote-control
koneru9999 · 5 months ago

I think the root cause of the issue is that if you have any of these ENV vars in the claude global settings, remove-control command is not enabled. It does not matter if they are enabled or disabled.

"env": {
    "DISABLE_TELEMETRY": "1",
    "DISABLE_ERROR_REPORTING": "1",
    "DISABLE_NON_ESSENTIAL_MODEL_CALLS": "1"
  },

The /remote-control command started working as soon as removed this block entirely. You may want to check this out. Hope it helps.

brandonwooding · 5 months ago

Starting up Claude code with the flag --remote-control brought back the slash command.

github-actions[bot] · 3 months ago

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.