Fix Claude OAuth: use claude.ai token endpoint (console host now 404s) - #12
Merged
TopiCsarno merged 1 commit intoJun 15, 2026
Merged
Conversation
Anthropic retired https://console.anthropic.com/v1/oauth/token (now returns 404). The subscription OAuth flow exchanges and refreshes tokens at https://claude.ai/v1/oauth/token. The authorize endpoint was already on claude.ai, so only the token host needed updating.
Owner
|
Thanks for the fix! |
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.
Fixes #11.
Anthropic retired
https://console.anthropic.com/v1/oauth/token— it now returns 404, so adding a Claude account fails at the code-exchange step. The subscription OAuth flow now exchanges and refreshes tokens athttps://claude.ai/v1/oauth/token.Same request, just the host changed, and it returns the tokens fine. The authorize endpoint and redirect URI were already correct, so only
TOKEN_ENDPOINTneeded updating — in two places (login + refresh). Tested on 0.5.0; login works again after this change.