Use /v3/session for status account info; stop probing account lifecycle endpoints - #68
Merged
Merged
Conversation
…fecycle endpoints The status command probed /v3/auth/account/memberships (and two other guessed paths) with the user's API key to scrape account info. That endpoint is session-only — every API-key request 403s with 'API keys cannot access account lifecycle endpoints' (Sentry issue SUPERMEMORY-BACKEND-108R, ~1,700 events across 765 users since June). /v3/session is the whoami endpoint that works with API-key auth (it's what the MCP server uses) and returns user email/name/id and org name directly, so the generic JSON scraper is gone too. Bumps to 2.0.12. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Member
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Dhravya
changed the title
Dhravya
marked this pull request as ready for review
August 10, 2026 20:07
Prasanna721
approved these changes
Aug 10, 2026
Prasanna721
approved these changes
Aug 10, 2026
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.
Why?
The
statuscommand probed/v3/auth/account/memberships(plus two other guessed paths) with the user's API key just to display account info. That endpoint is part of the console's account-deletion flow and is session-only — every API-key request deterministically 403s withAPI keys cannot access account lifecycle endpoints. This is the source of Sentry issue SUPERMEMORY-BACKEND-108R (~1,700 events across 765 users since June 17).What?
getAccountInfonow callsGET /v3/session— the whoami endpoint that works with API-key auth (same one the MCP server uses) — and readsuser.email/user.name/user.id/org.namedirectly.🤖 Generated with Claude Code