Remote Control: /remote-control gives no confirmation on enable, sessions never appear on claude.ai/code or mobile

Summary

/remote-control in an interactive CLI session produces no confirmation output when enabling (empty stdout), and none of the sessions I toggle it on for ever appear on claude.ai/code or in the mobile app. Running it again to disable does print "Remote Control disconnected.", so the command itself is doing something, but there's no visible signal that enabling ever succeeded, and nothing ever surfaces on the other end regardless.

This is across four separate interactive CLI sessions running concurrently on the same machine, all on the same account. None of them show up.

Environment

• claude-code CLI 2.1.281 (native install, commit 3e320108de68)
• macOS darwin-arm64
• Plan: Claude Max 20x, personal account
• Auth: OAuth login (~/.claude/.credentials.json present), no ANTHROPIC_API_KEY, no Bedrock/Vertex env vars
• claude doctor output: no installation issues, Remote Control section reports clean
• Network confirmed healthy to claude.ai and api.anthropic.com from this machine
• No active incident listed on status.claude.com at time of testing

Steps

1. In a running interactive session, run /remote-control.
2. Observe: empty stdout, no pairing link, no confirmation of any kind.
3. Check claude.ai/code and the mobile app Code tab: session never appears.
4. Run /remote-control again: prints "Remote Control disconnected."
5. Repeat across three other concurrent interactive sessions on the same account/machine: same result every time.

Expected

Either a visible confirmation (pairing link, session name, something) when Remote Control is enabled, and the session showing up on claude.ai/code and the mobile app within a reasonable time, or a visible error explaining why it didn't.

Actual

Enabling is silent. Nothing ever appears on claude.ai/code or the mobile app for any of the sessions tried. No error is surfaced anywhere in the CLI or in claude doctor.

Possibly related

• #84929 describes the same core failure (sessions register locally, stay connected, never appear on claude.ai/code or mobile, direct session URL shows "Unable to load messages"). That one's been open since August across multiple CLI versions (2.1.224, 2.1.241) with no resolution; this report adds a data point on 2.1.281 with a related but distinct symptom (no confirmation output at all on enable, rather than reaching a visible "Ready" state that then fails to surface).
• #96220 describes Remote Control being silently disabled across sessions after a Desktop app restart, a different trigger but the same practical outcome (Remote Control unusable without any actionable error).

Happy to provide additional diagnostics if useful.