[BUG] remote-control does not work with setup-token (needs user:sessions:claude_code scope)

Resolved 💬 6 comments Opened Mar 11, 2026 by benjaminwood Closed Apr 18, 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?

When attempting to use /remote-control with claude code authenticated via a setup-token, the following error is received:

OAuth token does not meet scope requirement user:sessions:claude_code

This has been reported twice (1, 2) but both tickets were auto-closed, and yet the issue remains.

This is a legitimate use-case. I want to run remote-control in a remote/ephemeral environment a setup-token is appropriate for that.

What Should Happen?

/remote-control should work when claude is authenticated via a setup-token

Error Messages/Logs

OAuth token does not meet scope requirement user:sessions:claude_code

Steps to Reproduce

Just authenticate claude with a setup token and then try /remote-control. You'll get the error.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.72

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Non-interactive/CI environment

Additional Information

_No response_

View original on GitHub ↗

This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗