fix: distinguish Claude organizations sharing an email#1
Open
crgwbr wants to merge 1 commit into
Open
Conversation
Key saved credentials and per-account state by normalized email and organization UUID. Preserve legacy credential slots while validating captures, OAuth logins, switching, and cached usage against the exact organization.
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 & why
Claude subscriptions are scoped to organizations, but PitStop previously identified accounts only by email. Personal and team organizations sharing an email could therefore overwrite saved credentials, collide in cached state, merge into one menu row, and report the wrong usage.
Key Claude profiles and per-account state by normalized email plus organization UUID. Preserve legacy email-named keychain entries, require a one-time exact identity verification after migration, and keep OAuth login, switching, Desktop merging, usage caching, auto-switching, and session warming scoped to the correct organization.
How I tested
swift buildswift test— 129 tests passedChecklist
swift build)--checkand/or the menu)