Conversation
This was referenced Sep 10, 2026
legibet
force-pushed
the
fix/oauth-add-without-switch
branch
from
September 10, 2026 10:46
ec371e1 to
720c8bc
Compare
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.
Summary
active_account_idwhen adding an account, including the first account.Why
OAuth completion currently writes the new account directly to
~/.codex/auth.json. This bypasses the process guard and token-preservation flow used by Switch.After this change, adding an account only stores it. The user activates it through the existing Switch action.
Checks
cargo test --manifest-path src-tauri/Cargo.toml: 51 passedcargo clippy --manifest-path src-tauri/Cargo.toml --all-targets: completed with pre-existing warningspnpm build: passedpnpm test:reset-credits: 3 passedgit diff --check: passedRelated