feat(framework): label the dashboard session link honestly (#221)#222
Merged
Conversation
Our headless runs are not Remote-Controlled, so the default claude.ai/code link is a generic entry point, not a live per-run session. Label it "Open Claude Code" and keep "live session" only for a real --session-link. Rewrite the README session section to document the user-initiated claude auth login + --remote-control steer path. Corrects #212's overpromise; follow-up to the #214 de-risk. Closes #221
suleimansh
added
enhancement
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Our runs are headless, which is deliberately not Remote-Controlled, so the default
https://claude.ai/codelink is a generic Claude Code entry point, not a live per-run session. The dashboard used to render it as a "live session" anchor, which overpromises.--session-link.claude --resume).claude auth login+claude --remote-control --name <run>session and open it from claude.ai/code (a separate process from a run).Why
Follow-up to the #214 de-risk. Testing against Claude Code 2.1.201 confirmed the real-URL capture #214 asked for is infeasible:
-p+--remote-control: flag silently ignored, no URL emitted (only a local UUID session_id).claude remote-controlrefuses automation tokens ("requires a full-scope login token").So Remote Control is a user-initiated steer handoff, not something our headless orchestrator can deep-link into. This PR makes the dashboard say that honestly. Corrects #212's overpromise.
Closes #221.