Implementing ePDS Login

ePDS lets users sign in to AT Protocol apps using email OTP. New users receive a DID, handle, and data repository automatically.

Earlier versions of this skill recommended a hand-rolled OAuth flow. That guidance is deprecated in favor of @atproto/oauth-client-node, which handles PAR, PKCE, DPoP, token exchange, and OAuth state. The repository's packages/demo client still contains the earlier implementation and is not the current integration reference.

For protocol-level guidance beyond ePDS specifics—granular scope design, identity verification after token exchange, session storage, and refresh-token race handling—read the atproto-oauth skill.

Choose the Login Input

All variants use one NodeOAuthClient and converge on the same callback and session.did.