Prefer Claude Keychain credentials for quota lookup#17
Merged
handlecusion merged 1 commit intoJun 11, 2026
Merged
Conversation
Owner
|
I've reviewed it. Thank you for the contribution! |
Merged
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
2 participants
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
This changes the Claude OAuth credential lookup order used by the Agent limits quota request.
~/.claude/.credentials.json→ macOS Keychain~/.claude/.credentials.jsonFixes #16.
Why
On macOS, Claude Code can have a fresh OAuth credential in Keychain while a legacy
~/.claude/.credentials.jsonfile still exists. Tokcat previously returned the file credential first, so the quota lookup could use a stale credential and show a Claude OAuth error even though Claude Code itself was authenticated.Verification
cargo check/Applications/Tokcat.appsuccessfully during manual validation