[GH-ISSUE #5907] FEAT: Privy #10374

New Issue

2026-04-13T06:28:35-05:00

GiteaMirror commented

2026-04-13 06:28:35 -05:00

Originally created by @austinm911 on GitHub (Nov 11, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/5907

Is this suited for github?

Yes, this is suited for github

Is your feature request related to a problem? Please describe.

Privy is a crypto wallet infrastructure stack that was recently acquired by Stripe.
https://www.privy.io/
https://docs.privy.io/api-reference/introduction

Describe the solution you'd like

Integration with their SDK

Describe alternatives you've considered

Not sure what alternatives there are

Additional context

No response

Originally created by @austinm911 on GitHub (Nov 11, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/5907 ### Is this suited for github? - [ ] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. Privy is a crypto wallet infrastructure stack that was recently acquired by Stripe. https://www.privy.io/ https://docs.privy.io/api-reference/introduction ### Describe the solution you'd like Integration with their SDK ### Describe alternatives you've considered Not sure what alternatives there are ### Additional context _No response_

GiteaMirror added the oauth label 2026-04-13 06:28:35 -05:00

GiteaMirror commented

2026-04-13 06:28:36 -05:00

@shrkawy commented on GitHub (Nov 12, 2025):

Privy doesn’t offer custom authentication in its Free or Pro plans, only in the Enterprise tier, which is quite expensive.
In my opinion, Web3Auth is definitely a better choice in that regard. I tried integrating Privy in one of my projects but eventually switched to Web3Auth + Better Auth, and they work together seamlessly with the jwt plugin.
The developer experience was much smoother, and the cost was significantly lower.

@shrkawy commented on GitHub (Nov 12, 2025): `Privy` doesn’t offer custom authentication in its Free or Pro plans, only in the Enterprise tier, which is quite expensive. In my opinion, `Web3Auth` is definitely a better choice in that regard. I tried integrating Privy in one of my projects but eventually switched to `Web3Auth` + `Better Auth`, and they work together seamlessly with the `jwt` plugin. The developer experience was much smoother, and the cost was significantly lower.

GiteaMirror commented

2026-04-13 06:28:37 -05:00

@austinm911 commented on GitHub (Nov 12, 2025):

@shrkawy good to know, I am not very familiar with each, so I appreciate the insight!

@austinm911 commented on GitHub (Nov 12, 2025): @shrkawy good to know, I am not very familiar with each, so I appreciate the insight!

GiteaMirror commented

2026-04-13 06:28:38 -05:00

@denyncrawford commented on GitHub (Dec 20, 2025):

@shrkawy here is a documentation of how to authenticate using JWT https://docs.privy.io/authentication/user-authentication/jwt-based-auth/overview is this only for Enterprise tier?

@denyncrawford commented on GitHub (Dec 20, 2025): @shrkawy here is a documentation of how to authenticate using JWT https://docs.privy.io/authentication/user-authentication/jwt-based-auth/overview is this only for Enterprise tier?

GiteaMirror commented

2026-04-13 06:28:39 -05:00

@itxtoledo commented on GitHub (Jan 12, 2026):

The JWT from better-auth doesn't work with web3auth because the generated JWT doesn't have the "iat" attribute, and web3auth looks for this property to validate the token.

@itxtoledo commented on GitHub (Jan 12, 2026): The JWT from better-auth doesn't work with web3auth because the generated JWT doesn't have the "iat" attribute, and web3auth looks for this property to validate the token.

GiteaMirror commented

2026-04-13 06:28:39 -05:00

@denyncrawford commented on GitHub (Jan 12, 2026):

@itxtoledo i was able to work with privy perfectly, just take in mind that you need at least the scale plan to do it.

@denyncrawford commented on GitHub (Jan 12, 2026): @itxtoledo i was able to work with privy perfectly, just take in mind that you need at least the scale plan to do it.

GiteaMirror commented

2026-04-13 06:28:40 -05:00

@itxtoledo commented on GitHub (Jan 12, 2026):

Thanks @denyncrawford! Just to clarify, we’re currently using Web3Auth (not Privy) and are on a paid plan. I wanted to share this as an observation because @shrkawy had recommended Web3Auth, but unfortunately it doesn’t work with BetterAuth’s JWT. Also, BetterAuth doesn’t allow modifying the JWT claims, even when using the definePayload property.

@itxtoledo commented on GitHub (Jan 12, 2026): Thanks @denyncrawford! Just to clarify, we’re currently using Web3Auth (not Privy) and are on a paid plan. I wanted to share this as an observation because @shrkawy had recommended Web3Auth, but unfortunately it doesn’t work with BetterAuth’s JWT. Also, BetterAuth doesn’t allow modifying the JWT claims, even when using the definePayload property.

GiteaMirror commented

2026-04-13 06:28:40 -05:00

@denyncrawford commented on GitHub (Jan 12, 2026):

@itxtoledo what about custom signing? https://www.better-auth.com/docs/plugins/jwt#custom-signing https://docs.metamask.io/embedded-wallets/authentication/custom-connections/custom-jwt/#generate-a-jwt

@denyncrawford commented on GitHub (Jan 12, 2026): @itxtoledo what about custom signing? https://www.better-auth.com/docs/plugins/jwt#custom-signing https://docs.metamask.io/embedded-wallets/authentication/custom-connections/custom-jwt/#generate-a-jwt

GiteaMirror commented

2026-04-13 06:28:41 -05:00

@shrkawy commented on GitHub (Jan 13, 2026):

@denyncrawford

@shrkawy here is a documentation of how to authenticate using JWT https://docs.privy.io/authentication/user-authentication/jwt-based-auth/overview is this only for Enterprise tier?

When I tried to integrate it with Privy, it was on the Enterprise plan, but I'm not sure if they've changed that or if it's still part of the Enterprise plan.

@shrkawy commented on GitHub (Jan 13, 2026): @denyncrawford > [@shrkawy](https://github.com/shrkawy) here is a documentation of how to authenticate using JWT https://docs.privy.io/authentication/user-authentication/jwt-based-auth/overview is this only for Enterprise tier? When I tried to integrate it with Privy, it was on the Enterprise plan, but I'm not sure if they've changed that or if it's still part of the Enterprise plan.

GiteaMirror commented

2026-04-13 06:28:42 -05:00

@shrkawy commented on GitHub (Jan 13, 2026):

@itxtoledo

The JWT from better-auth doesn't work with web3auth because the generated JWT doesn't have the "iat" attribute, and web3auth looks for this property to validate the token.

I already have a working app that uses both Web3Auth and Better Auth with JWT, and everything is running smoothly. If you can share a code snippet, I’ll be happy to help you figure out what’s going wrong.

This is a snippet of the Better Auth Backend JWT plugin config

jwt({
      jwks: {
        keyPairConfig: {
          alg: 'RS256', // Web3Auth prefers RS256
        },
        disablePrivateKeyEncryption: false,
      },
      jwt: {
        issuer: 'my_app_name',
        audience: 'my_app_aud',
        expirationTime: '1h',
        definePayload: ({ user, session }) => {
          const now = Math.floor(Date.now() / 1000);
          return {
            sub: user.id,
            name: user.name || '',
            email: user.email,
            iss: 'my_app_name',
            aud: 'my_app_aud',
            iat: now,
            exp: now + 3600,
            sessionId: session.id,
          };
        },
      },
    })

Frontend

const connectToWeb3Auth = async () => {
    try {
      const jwt = await authClient.token();
      if (!jwt.data?.token) {
        throw new Error("No idToken received from Better Auth");
      }

      await connectTo(WALLET_CONNECTORS.AUTH, {
        authConnection: AUTH_CONNECTION.CUSTOM,
        authConnectionId: "auth_connection_id", // you get this from Web3Auth Dashboard
        idToken: jwt.data.token,
      });
    } catch (err) {
      authClient.signOut();
      const errorMessage =
        err instanceof Error ? err.message : "Error logging into Web3Auth";
      console.error("Error logging into Web3Auth:", err);
    }
  };

I hope that can help

@shrkawy commented on GitHub (Jan 13, 2026): @itxtoledo > The JWT from better-auth doesn't work with web3auth because the generated JWT doesn't have the "iat" attribute, and web3auth looks for this property to validate the token. I already have a working app that uses both Web3Auth and Better Auth with JWT, and everything is running smoothly. If you can share a code snippet, I’ll be happy to help you figure out what’s going wrong. This is a snippet of the Better Auth Backend JWT plugin config ```ts jwt({ jwks: { keyPairConfig: { alg: 'RS256', // Web3Auth prefers RS256 }, disablePrivateKeyEncryption: false, }, jwt: { issuer: 'my_app_name', audience: 'my_app_aud', expirationTime: '1h', definePayload: ({ user, session }) => { const now = Math.floor(Date.now() / 1000); return { sub: user.id, name: user.name || '', email: user.email, iss: 'my_app_name', aud: 'my_app_aud', iat: now, exp: now + 3600, sessionId: session.id, }; }, }, }) ``` Frontend ```ts const connectToWeb3Auth = async () => { try { const jwt = await authClient.token(); if (!jwt.data?.token) { throw new Error("No idToken received from Better Auth"); } await connectTo(WALLET_CONNECTORS.AUTH, { authConnection: AUTH_CONNECTION.CUSTOM, authConnectionId: "auth_connection_id", // you get this from Web3Auth Dashboard idToken: jwt.data.token, }); } catch (err) { authClient.signOut(); const errorMessage = err instanceof Error ? err.message : "Error logging into Web3Auth"; console.error("Error logging into Web3Auth:", err); } }; ``` I hope that can help

GiteaMirror commented

2026-04-13 06:28:43 -05:00

@itxtoledo commented on GitHub (Jan 13, 2026):

@itxtoledo

The JWT from better-auth doesn't work with web3auth because the generated JWT doesn't have the "iat" attribute, and web3auth looks for this property to validate the token.

I already have a working app that uses both Web3Auth and Better Auth with JWT, and everything is running smoothly. If you can share a code snippet, I’ll be happy to help you figure out what’s going wrong.

This is a snippet of the Better Auth Backend JWT plugin config

jwt({
jwks: {
keyPairConfig: {
alg: 'RS256', // Web3Auth prefers RS256
},
disablePrivateKeyEncryption: false,
},
jwt: {
issuer: 'my_app_name',
audience: 'my_app_aud',
expirationTime: '1h',
definePayload: ({ user, session }) => {
const now = Math.floor(Date.now() / 1000);
return {
sub: user.id,
name: user.name || '',
email: user.email,
iss: 'my_app_name',
aud: 'my_app_aud',
iat: now,
exp: now + 3600,
sessionId: session.id,
};
},
},
})
Frontend

const connectToWeb3Auth = async () => {
try {
const jwt = await authClient.token();
if (!jwt.data?.token) {
throw new Error("No idToken received from Better Auth");
}
  await connectTo(WALLET_CONNECTORS.AUTH, {
    authConnection: AUTH_CONNECTION.CUSTOM,
    authConnectionId: "auth_connection_id", // you get this from Web3Auth Dashboard
    idToken: jwt.data.token,
  });
} catch (err) {
  authClient.signOut();
  const errorMessage =
    err instanceof Error ? err.message : "Error logging into Web3Auth";
  console.error("Error logging into Web3Auth:", err);
}
};
I hope that can help

Which version of better-auth are you using? I'm using "better-auth": "^1.4.7" and any additional properties I add to the token aren't returned in the JWT to the frontend, but I solved it by signing in a custom way as @denyncrawford showed.

@itxtoledo commented on GitHub (Jan 13, 2026): > [@itxtoledo](https://github.com/itxtoledo) > > > The JWT from better-auth doesn't work with web3auth because the generated JWT doesn't have the "iat" attribute, and web3auth looks for this property to validate the token. > > I already have a working app that uses both Web3Auth and Better Auth with JWT, and everything is running smoothly. If you can share a code snippet, I’ll be happy to help you figure out what’s going wrong. > > This is a snippet of the Better Auth Backend JWT plugin config > > jwt({ > jwks: { > keyPairConfig: { > alg: 'RS256', // Web3Auth prefers RS256 > }, > disablePrivateKeyEncryption: false, > }, > jwt: { > issuer: 'my_app_name', > audience: 'my_app_aud', > expirationTime: '1h', > definePayload: ({ user, session }) => { > const now = Math.floor(Date.now() / 1000); > return { > sub: user.id, > name: user.name || '', > email: user.email, > iss: 'my_app_name', > aud: 'my_app_aud', > iat: now, > exp: now + 3600, > sessionId: session.id, > }; > }, > }, > }) > Frontend > > const connectToWeb3Auth = async () => { > try { > const jwt = await authClient.token(); > if (!jwt.data?.token) { > throw new Error("No idToken received from Better Auth"); > } > > await connectTo(WALLET_CONNECTORS.AUTH, { > authConnection: AUTH_CONNECTION.CUSTOM, > authConnectionId: "auth_connection_id", // you get this from Web3Auth Dashboard > idToken: jwt.data.token, > }); > } catch (err) { > authClient.signOut(); > const errorMessage = > err instanceof Error ? err.message : "Error logging into Web3Auth"; > console.error("Error logging into Web3Auth:", err); > } > }; > I hope that can help Which version of better-auth are you using? I'm using `"better-auth": "^1.4.7"` and any additional properties I add to the token aren't returned in the JWT to the frontend, but I solved it by signing in a custom way as @denyncrawford showed.

GiteaMirror commented

2026-04-13 06:28:43 -05:00

@shrkawy commented on GitHub (Jan 13, 2026):

@itxtoledo I use the latest version, it was working on the previous versions as well.

returned data from /auth/jwks should match this

{
  "keys": [
    {
      "alg": "RS256",
      "kty": "RSA",
      "n": "",
      "e": "",
      "kid": ""
    }
  ]
}

Also, you can verify the additional properties by getting the token from this endpoint auth/token, it should be a normal JWT token

{
  "token": "eyJhbGciOiJSUzI1NiIsImtpZCI6......"
}

Use this website to decode it, and you should have the additional fields in the token
https://www.jwt.io/

In my case, the decoded value matches the defined payload

{
  "iat": 1768316381,
  "sub": "FQ08P7YuDDxAYtLGloHd0uSscBeT6wDJ",
  "name": "Name",
  "email": "email@gmail.com",
  "iss": "ISS_VALUE",
  "aud": "AUD_VALUE",
  "exp": 1768319981,
  "sessionId": "qqOXxs9xrnXaT0xkHXnvVbw2SiGIvhv6"
}

@shrkawy commented on GitHub (Jan 13, 2026): @itxtoledo I use the latest version, it was working on the previous versions as well. returned data from `/auth/jwks` should match this ```json { "keys": [ { "alg": "RS256", "kty": "RSA", "n": "", "e": "", "kid": "" } ] } ``` Also, you can verify the additional properties by getting the token from this endpoint `auth/token`, it should be a normal JWT token ```json { "token": "eyJhbGciOiJSUzI1NiIsImtpZCI6......" } ``` Use this website to decode it, and you should have the additional fields in the token https://www.jwt.io/ In my case, the decoded value matches the defined payload ```json { "iat": 1768316381, "sub": "FQ08P7YuDDxAYtLGloHd0uSscBeT6wDJ", "name": "Name", "email": "email@gmail.com", "iss": "ISS_VALUE", "aud": "AUD_VALUE", "exp": 1768319981, "sessionId": "qqOXxs9xrnXaT0xkHXnvVbw2SiGIvhv6" } ```

GiteaMirror commented

2026-04-13 06:28:43 -05:00

@denyncrawford commented on GitHub (Jan 13, 2026):

@shrkawy With privy enterprice plan should be very stright forward, this is literally my configuration:


 plugins: [
    expo(),
    jwt({}),
    ....
]

You only need to activate the jwt authentication on the admin pannel of your app and use client side authentication:

JWKS endpoint: https://api.yourapi.com/api/auth/jwks (or ngrok, but i recommend to you just pushing your code to a dev environment it is not going to fail and it is a one time setup)
JWT user ID claim: sub

and that's it.

For client side, create a privy auth provider and request the token of the session using the auth client:

export const PrivyAuthProvider = ({ children }: { children: React.ReactNode }) => {

  const { data: session, isPending } = authClient.useSession();

  const getCustomToken = useCallback(async () => {
    try {
      const { data: tokenData } = await authClient.token();
      const token = tokenData?.token;
      return token;
    } catch (error) {
      // If there's an error, the user is likely not authenticated
      return undefined;
    }

  }, [session, isPending]);
  return (
    <PrivyProvider
      appId="...."
      clientId="client-...."
      config={{
        embedded: {
          ethereum: {
            createOnLogin: "users-without-wallets",
          }
        },
        customAuth: {
          enabled: true,
          // Indicates if your auth provider is currently updating auth state
          isLoading: isPending,
          // Callback to get the user's JWT token
          getCustomAccessToken: getCustomToken,
        }
      }}
    >
      {children}
    </PrivyProvider>
  );
}

this is for a react native example, but pretty sure react client is almost same.

@denyncrawford

@shrkawy here is a documentation of how to authenticate using JWT https://docs.privy.io/authentication/user-authentication/jwt-based-auth/overview is this only for Enterprise tier?

When I tried to integrate it with Privy, it was on the Enterprise plan, but I'm not sure if they've changed that or if it's still part of the Enterprise plan.

@denyncrawford commented on GitHub (Jan 13, 2026): @shrkawy With privy enterprice plan should be very stright forward, this is literally my configuration: ```ts plugins: [ expo(), jwt({}), .... ] ``` You only need to activate the jwt authentication on the admin pannel of your app and use client side authentication: JWKS endpoint: https://api.yourapi.com/api/auth/jwks (or ngrok, but i recommend to you just pushing your code to a dev environment it is not going to fail and it is a one time setup) JWT user ID claim: sub and that's it. For client side, create a privy auth provider and request the token of the session using the auth client: ```ts export const PrivyAuthProvider = ({ children }: { children: React.ReactNode }) => { const { data: session, isPending } = authClient.useSession(); const getCustomToken = useCallback(async () => { try { const { data: tokenData } = await authClient.token(); const token = tokenData?.token; return token; } catch (error) { // If there's an error, the user is likely not authenticated return undefined; } }, [session, isPending]); return ( <PrivyProvider appId="...." clientId="client-...." config={{ embedded: { ethereum: { createOnLogin: "users-without-wallets", } }, customAuth: { enabled: true, // Indicates if your auth provider is currently updating auth state isLoading: isPending, // Callback to get the user's JWT token getCustomAccessToken: getCustomToken, } }} > {children} </PrivyProvider> ); } ``` this is for a react native example, but pretty sure react client is almost same. > [@denyncrawford](https://github.com/denyncrawford) > > > [@shrkawy](https://github.com/shrkawy) here is a documentation of how to authenticate using JWT https://docs.privy.io/authentication/user-authentication/jwt-based-auth/overview is this only for Enterprise tier? > > When I tried to integrate it with Privy, it was on the Enterprise plan, but I'm not sure if they've changed that or if it's still part of the Enterprise plan.

Sign in to join this conversation.

Branches Tags

2026-08-14/fix/standardize-plugin-types

2026-08-13/fix/dpop-public-url

dependabot/npm_and_yarn/demo/electron/demo-minor-patch-0f55cd1273

dependabot/npm_and_yarn/sveltejs/kit-2.70.2

2026-08-13/fix/acr-values-voluntary

starsling/CHG-forget-processed-cleanup-rows-b8077b74ef9a-4971f8e41755

refactor/device-authorization-oauth-boundary

2026-08-11/fix/api-key-rate-limit-window

dependabot/github_actions/github-actions-42c4bc6a62

feat/oauth-provider-custom-subject

pr-9793-merge

2026-07-31/chore/bump-better-call

2026-07-30/chore/upgrade-better-call

2026-07-30/fix/nextjs-rsc-session-refresh

feat/1-7-migration-validation

2026-07-29/refactor/centralize-placeholder-email-generation

refactor/oauth-client-application-type

2026-07-28/fix/anonymous-oauth-proxy-linking

feat/agent-feedback-endpoint

fix/oauth-provider-session-deletion

feat/scim-demo-workflow

feat/scim-active-user-link

feat/sso-provider-user-resolution

feat/identity-provider-accounts

feat/oauth-provider-remove-silence-warnings

changeset-release/release/vercel-announcement

release/vercel-announcement

2026-06-29/docs/optimize-og-images

feat/yandex-social-provider

feat/ssrf-fetch-boundary

codex/pr-10225-next-comments

fix/phone-number-disable-input

perf/router-build-once

fix/oauth-user-provisioning-fields

codex/ignore-compose-override-spellcheck

2026-06-19/fix/stripe-org-reference-scope

feat/webhooks

feat/baseurl-canonical-serving-split

feat/magic-link-expires-in

fix/esbuild-security-bump

chore/sync-main-to-next-20260615

chore/revert-10053

codex/fix-expo-sdk56-dynamic-import

refactor/oauth-provider-client-authentication-module

fix/oauth-no-store-headers

claude/slack-update-stripe-docs-consistency-8Sc0w

local/fix-invite-accept-idempotency

docs/beta-mdx-component-fallback

fix/dependabot-hono-shell-quote

codex/stateless-account-cookie-resolution

fix/admin-create-user-role-escalation

feat/oauth-provider-oidc-acr

refactor/sign-in-challenges

refactor/optional-kysely-dependency

2026-06-06/chore/kysely-changeset

copilot/fix-code-review-comment

starsling/prisma-migration-reset

2026-06-02/fix/next-cookies-defer-rsc

feat/oauth-contribution-protocol

ping-maxwell/c-ping-maxwell/fix-kysely-adapter-core-utils-string-resolution-68c5

temp/server-only-test

2026-05-31/refactor/kysely-joins-json-helpers

2026-04-29/feat/google-include-granted-scopes

2026-04-29/fix/oauth-account-scope-semantics

fix/oauth-callback-path-declarative

2026-05-31/fix/sqlite-dialect-affected-rows

fix/next-cookie-separator

2026-05-29/fix/last-login-method-cookie-prefix

ping-maxwell/c-ping-maxwell/fix-error-link-apostrophe-f89a

client-assertions-main

2026-05-15/ci/fix-sqlite-abi-mismatch

2026-05-15/fix/organization-team-add-cascade

2026-05-15/fix/parse-set-cookie-value-validation

2026-05-13/feat/captcha-wildcard-endpoints

fix/i18n-before-hook-translation

fix/disable-migration-generate

2026-05-10/fix/cookie-drain-order

2026-05-10/feat/hooks-finally

2026-05-09/fix/cookie-drain-order

2026-05-09/feat/hooks-finally

2026-05-08/feat/register-before-send

fix/stripe/subscription-data-merge

2026-05-01/chore/pnpm-v11-harden

chore/pnpm-v11

2026-04-27/fix/nextcookies-idempotent-writes

2026-04-26/fix/harden-proxy-host-validation

2026-04-26/refactor/stripe-callback-signature-cleanup

2026-04-26/fix/stripe-subscription-callback-timing

2026-04-11/fix/sveltekit-app-modules

feat/open-api-zod-contract

feat/oauth-idp-initiated-bounce

2026-04-21/fix/oauth-rfc-input-validation

fix/two-factor-identity-guard

fix/resource

feat/emailpassword-authorize

feat/oauth-provider-at-hash-v2

fix/release-grep-fallback

claude/address-review-comments-JhFLr

feat/async-auth

fix/two-factor-totp-verified-enrollment

feat/plugin-ui

codex/blog-1-6-release-post

2026-04-06/fix/type-any-guards

2026-04-05/chore/downgrade-better-call

2026-04-04/ci/skip-vercel-fork-prs

2026-03-28/ci/add-autofix-ci

chore/release-preview-script

himself65/2026/02/19/role

2026-03-20/docs/improve-website

2026-03-20/fix/anonymous-onlinkaccount-expo

2026-02-17/fix/anonymous-link-state

fix/8607-saml-inresponseto

fix/8549-scim-patch-noop

v1.4.x

refactor/migration-snapshot-tests

worktree-magic-link-additional-data

chore/migrate-build-to-rollup

worktree-fix-dynamic-baseurl-8447

2026-03-06/chore/public-api-check

fix/close-8156-regression-test

fix/secondary-storage-json-error-handling

himself65/verification-namespace

cursor/issue-8307-validation-79a3

himself65/2026/01/30/error-mdx

v1.4.x-staging

fix/email-otp-user

fix/restrict-full-organization-access-roles

himself65/2026/02/12/count

himself65/2026/02/04/define-plugin

2026-02-04/feat/add-pluralize

cursor/better-auth-js-integration-ec21

cursor/expo-state-mismatch-394c

2026-02-01/fix/org-update-role-sync-members

cursor/issue-7607-investigation-e146

cursor/email-generation-helper-0ff6

himself65/2026/01/21/avoid-spread-operator

himself65/2026/01/14/cli

claude/slack-add-docs-pr-NMvgO

claude/slack-add-advanced-useplural-WHKYL

feat/hooks-pos

feat/2fa-phone

feat/2fa

fix/rotation

fix/username-check

v1.3.x

refactor/organization

feat/multiple-client-ids-social-providers

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/better-auth#10374