Repository navigation
fix: make Codex and Claude Code subscriptions discoverable - #179
Merged
Merged
Conversation
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
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.
Codex and Claude Code already reuse their CLI login, but Settings presented them without a subscription setup path. Users can now choose clearly labeled subscription CLI options and see shared sign-in, copy-command, account-status and official-guide controls in Settings and the Agents empty state. API-key inputs remain specific to the independent API backends; the guide explains CLI credential precedence and the separate login required on an SSH target.
Verified the actual ShellDeck client paths with Codex 0.159.2 signed in through ChatGPT and Claude Code 2.1.285 signed in through Claude.ai/Max. A new opt-in live smoke removes API-key variables in a child process, confirms the subscription authentication methods, and receives the exact connection-test response from both providers. No user login was replaced or API key stored.
Validation:
--no-deps -- -D warnings, formatting and whitespace checks passed.SDTEST-1935 stays opt-in outside CI. SDTEST-1936 tracks missing automated native render/click coverage. Fresh browser login, remote subscription authentication and full write-capable coding-agent journeys were not live-tested.