Skip to content

docs: Use getClaims instead of getUser in Next.js Auth prompt#439

Open
sagarsrc wants to merge 1 commit intomasterfrom
test-pr-429-40798-1767895737
Open

docs: Use getClaims instead of getUser in Next.js Auth prompt#439
sagarsrc wants to merge 1 commit intomasterfrom
test-pr-429-40798-1767895737

Conversation

@sagarsrc
Copy link

@sagarsrc sagarsrc commented Jan 8, 2026

I have read the CONTRIBUTING.md file.

YES

What kind of change does this PR introduce?

This PR updates the Next.js Supabase Auth AI tools prompt to use supabase.auth.getClaims() from the Supabase SDK instead of supabase.auth.getUser(). This is generally good practice, as getClaims does not make network calls unless the user's session is invalid or uses a symmetric signing key.

What is the current behavior?

This prompt instructs the AI tool to use getUser, which always makes a network call to the project's Auth API.

What is the new behavior?

The prompt instructs the AI tool to use getClaims, which is generally faster as long as a user has migrated their JWT signing keys.


Test data recreated from supabase#40798
Target state: open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant