Skip to content

feat(framework): default the live-run session link to claude.ai/code (#212)#215

Merged
suleimansh merged 1 commit into
mainfrom
feat/default-remote-control-link
Jul 4, 2026
Merged

feat(framework): default the live-run session link to claude.ai/code (#212)#215
suleimansh merged 1 commit into
mainfrom
feat/default-remote-control-link

Conversation

@suleimansh

Copy link
Copy Markdown
Member

Closes #212. Part of #209 (the MVP dashboard).

Shows a useful session link on the dashboard without needing --session-link.

What changed

  • A live run defaults its session link to https://claude.ai/code (the page where a Claude Code session appears once Remote Control is on). --fake gets no link (no real session); an explicit --session-link still wins, including the {sessionId} template filled with the real Claude session id once known.
  • README gains a "Watching the live session" section documenting the Remote Control path (opt-in, subscription, v2.1.51+) and the --session-link template. Help text updated too.
  • New pure, tested exports: chooseSessionLink, CLAUDE_CODE_SESSION_LIST.

Why no per-session deep link

I checked the Remote Control docs: there is no claude.ai/code/{sessionId} deep-link to construct. A session is reached via the URL Claude Code emits or by name in the session list, and Remote Control is opt-in + subscription-gated. We drive Claude Code headless, so no session-URL slug exists. Constructing one would be a dead link, so the honest default is the list page. Filed #214 to later launch Claude Code with Remote Control and surface the real URL it emits.

Checks

  • Repo typecheck (21) + build green.
  • framework 73/73 (new: default resolves to the list for a live run, --session-link override wins, no link for --fake).
  • Changeset added (minor).

A live run now shows a session link to https://claude.ai/code by default
(where a Claude Code session appears once Remote Control is enabled), so
the dashboard points somewhere useful without --session-link. --fake gets
no link (no real session); an explicit --session-link still wins, incl.
the {sessionId} template filled with the real Claude session id.

No per-session deep link is constructed: we drive Claude Code headless and
Remote Control is opt-in + subscription-gated, so there is no session-URL
slug to build. The session id is already surfaced on the dashboard + CLI
narration; the README documents the Remote Control path. New exports:
chooseSessionLink, CLAUDE_CODE_SESSION_LIST.

Part of #209. Closes #212.
@suleimansh suleimansh added enhancement New feature or request priority: medium Worth doing, not urgent labels Jul 4, 2026
@suleimansh suleimansh self-assigned this Jul 4, 2026
@suleimansh suleimansh merged commit f156cf8 into main Jul 4, 2026
2 checks passed
@suleimansh suleimansh deleted the feat/default-remote-control-link branch July 4, 2026 18:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request priority: medium Worth doing, not urgent

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Live claude.ai/code session link via Remote Control

1 participant