new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Better Auth · Plugins · all subjects

two-factor/signin

2 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Sign-in with 2FA response behavior

When a 2FA-enabled user signs in via email, username, or phone number, the response contains twoFactorRedirect set to true and twoFactorMethods array (e.g. ['totp', 'otp']). By default, 2FA applies only to credential endpoints: /sign-in/email, /sign-in/username, /sign-in/phone-number. Non-credential methods like email OTP, magic link, OAuth, passkey, and anonymous are not gated by 2FA by default.

2FA sign-in session state during challenge

When a 2FA-enabled user signs in via credential endpoint, a 2FA challenge is issued instead of completing sign-in. The pending session is discarded and ctx.context.newSession is reset to null. There is no authenticated session until the user verifies the second factor. Server-side hooks that read newSession must null-check before accessing newSession.user to avoid errors.

Give your agent this brain