Add CLI account login and persistent service environments - #8
Merged
Merged
Conversation
added 4 commits
September 21, 2026 14:49
irl-dan
changed the title
irl-dan
marked this pull request as ready for review
September 21, 2026 22:56
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.
Adds account login, status, logout and organization listing to the Rust and Bun CLIs. Production is the default; a persistent user setting selects staging, with separate credentials and a visible environment indicator. Repositories cannot change the selected service environment.
The CLI reuses the existing device authorization API and stores credentials in the operating system credential store where supported. Automation can provide an environment-specific API key. Service credentials are excluded from harness processes.
Validation: shared account and environment-persistence scenarios pass in both implementations. Live browser approval and native credential-store interoperability remain unverified. No backend deployment or public release is included. Registry publishing is a separate stacked PR.