[BUG] `claude remote-control` works locally but fails in SSH environment for Max subscriber
Resolved 💬 3 comments Opened Feb 26, 2026 by miyuki5151 Closed Feb 26, 2026
Bug Report
Environment:
- Claude Code version: 2.1.59
- OS: Linux (remote SSH session)
- Subscription: Max
- Shell: bash
Description:claude remote-control returns "Remote Control is not enabled for your account. Contact your administrator" when run in an SSH session, but works correctly when run locally on the same machine.
Steps to Reproduce:
- Connect via SSH to a remote machine
- Run
claude remote-control - Observe error: "Remote Control is not enabled for your account. Contact your administrator"
- Run
claude remote-controldirectly on the machine (local terminal) - Works correctly - QR code displayed
Expected Behavior:remote-control should work in SSH environments the same way it works locally.
Actual Behavior:
SSH session returns "not enabled" error, while local session works.
Environment Variables (SSH session):
TERM=xterm-256color
SSH_CLIENT=192.168.104.64 46602 22
SSH_CONNECTION=192.168.104.64 46602 192.168.10.126 22
SSH_TTY=/dev/pts/22
Possible Related Issues:
- May be related to TTY/terminal detection in headless SSH environments
- Feature flag service (Statsig) may behave differently in SSH vs local sessions
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗