Part of #209. Show a useful link to the live Claude Code session on the dashboard.
Correction from the original framing: there is no claude.ai/code/{sessionId} deep link to construct. Per the Remote Control docs, a session is reached via the URL Claude Code emits, or by name in the list at claude.ai/code, and Remote Control is opt-in + subscription-gated (v2.1.51+). We drive Claude Code headless, so no per-session URL slug exists to build.
Scope (Option A, this issue): default the live-run session link to https://claude.ai/code (valid page, matches the ask), keep --session-link (with {sessionId} templating) as the override, and document the Remote Control path in the README. The current session id is already surfaced on the dashboard + CLI narration.
Follow-up (Option B, separate): actually launch Claude Code with Remote Control + a recognizable name and surface the real session URL it emits. Tracked separately.
Part of #209. Show a useful link to the live Claude Code session on the dashboard.
Correction from the original framing: there is no
claude.ai/code/{sessionId}deep link to construct. Per the Remote Control docs, a session is reached via the URL Claude Code emits, or by name in the list at claude.ai/code, and Remote Control is opt-in + subscription-gated (v2.1.51+). We drive Claude Code headless, so no per-session URL slug exists to build.Scope (Option A, this issue): default the live-run session link to
https://claude.ai/code(valid page, matches the ask), keep--session-link(with{sessionId}templating) as the override, and document the Remote Control path in the README. The current session id is already surfaced on the dashboard + CLI narration.Follow-up (Option B, separate): actually launch Claude Code with Remote Control + a recognizable name and surface the real session URL it emits. Tracked separately.