Doctrine

REMOTE is a distinct platform for Claude Code Remote Control sessions

ID: ORA-2026-0027
Date: 2026-04-19
Status: canonical
Maturity: M3
Source: docs/entries/doctrines/ORA-2026-0027_remote-platform-convention-for-claude-code-remote-control.md

fleet-opsnaming

REMOTE is a distinct platform for Claude Code Remote Control sessions

The rule

Claude Code Remote Control (shipped Feb 2026) is a distinct platform from CLI and DESKTOP. Sessions driven from a phone/browser over the Anthropic relay MUST use REMOTE as their PLATFORM segment, not CLI or DESKTOP.

Seat format: CLAUDE-REMOTE-<EXEC-DEVICE>-<LANE>-<NN>

Example: CLAUDE-REMOTE-MacBook-Air-CAMBER-01

Slot rules

Segment	Value	Notes
PROVIDER	`CLAUDE`	Only Claude Code supports Remote Control today
PLATFORM	`REMOTE`	New category alongside CLI, DESKTOP
DEVICE	Exec device hostname	The Mac where filesystem/tool-calls land, NOT the control device
LANE	Standard lane	`CAMBER`, `ORBIT`, `HEARTWOOD`, `ORA`, or joined with `+`
INSTANCE	`NN`	Increment until free per standard identity negotiation

Key distinction: DEVICE is always the execution machine (the Mac), never the control device (phone/iPad/browser). The control device is interchangeable; the exec Mac is the fleet resource that collides.

Detection procedure

Extends ORA-2026-0005 with a REMOTE detection step.

Claude Code sessions — updated detection order:

1. Check CLAUDE_CODE_ENTRYPOINT env var:

sdk-cli → PLATFORM = REMOTE (unless session context indicates SDK automation without human driver)
claude-desktop → PLATFORM = DESKTOP
cli or absent (with TERM populated) → PLATFORM = CLI

If CLAUDE_CODE_ENTRYPOINT is unavailable, secondary tells:

Remote sessions typically have shorter network timeouts (~10 min)
Remote sessions arrive via Anthropic relay, not local terminal

Operational characteristics

Property	CLI	DESKTOP	REMOTE
Wake-scriptable	Yes (`claude --resume`)	No (manual open)	Partial (push notifications)
Network timeout	None (local)	None (local)	~10 min relay timeout
Filesystem access	Full (local Mac)	Full (local Mac)	Full (exec Mac)
tmux telemetry (Layer 3)	Works	N/A	Works (Mac-side CLI)
Screenshot telemetry (Layer 4)	Sees Mac screen	Sees Mac screen	Sees Mac screen, not phone
Concurrent instances	Unlimited	One per app window	One remote conn per Mac-side process

Implications for existing doctrine

Session-wake constraint: REMOTE is more wake-scriptable than DESKTOP (push notifications work) but less reliable than CLI (10-min network timeout can drop long operations). Update feedback_session_wake_constraint.md accordingly.
Fleet telemetry (ORA-2026-0016): All four layers work for REMOTE since execution happens on the Mac. Layer 4 caveat: screenshot captures the Mac display, not the phone screen — the phone is just a control surface.
Collision guard: Only one remote connection per Mac-side process. Instance-number collisions happen on the exec device, same as CLI/DESKTOP.

Origin

2026-04-17: CLAUDE-REMOTE-MacBook-Air-CAMBER-01 session mis-booted as CLAUDE-CLI-MacBook-Air-CAMBER-01 because the naming convention had no REMOTE slot. Proposed this doctrine in ORA-0027 dispatch. Chad drove the session from his phone over Claude Code Remote Control.