Remote Control always fails with HTTP 403 after restart; re-login on desktop and iOS does not recover

Status Closed — not planned
Maintainer reply None cached
Activity 1 comment · opened Oct 8, 2026 · closed Oct 8, 2026

Environment

  • Claude Code desktop app (Windows 10), Max plan
  • Remote Control used from the Claude iOS app

What happens

Remote Control can no longer be enabled for any session. Every attempt fails with:

Remote Control failed to connect: Remote Control server rejected the request (HTTP 403) — run /remote-control to retry
  • Started after a PC/app restart on 2026-10-06/07 (JST). Before that, Remote Control worked normally for several sessions.
  • After the restart, all existing sessions show Remote Control inactive and none reconnect automatically.
  • Retrying with /remote-control and the session toolbar switch returns the same 403 every time.
  • Signing out and back in on both the desktop app and the iOS app did not help.
  • Usage is not at a limit (weekly ~94%, 5-hour 3%). status.claude.com shows Claude Code and claude.ai operational.
  • A "spend limit incorrectly reached" incident was resolved on 2026-10-07 21:23 UTC; the 403 persists after it.

Expected

Remote Control reconnects (or can be re-enabled) after a restart, and re-login clears an authentication problem.

Related

#53563 (403 token expiry, closed) looks similar but re-login does not recover here.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗