Skip to main content

Clerk Changelog

Passkeys as a second factor

Category
Security
Published

Users can now use a passkey as their second factor for multi-factor authentication after they sign in another way.

Users can now use a passkey as their second factor for multi-factor authentication after they sign in another way. A passkey combines two factors, a device and a PIN or biometric, in one step.

When users sign in with a password, a social connection, or a reset-password code, they can use their passkey instead of an SMS code or authenticator app, including during reverification. In <SignIn /> and the reverification modal, users who have a passkey start on the passkey step and can pick another method with Use another method.

This also helps with recovery. A user who loses their phone or authenticator app can sign in with their password and use their passkey as their second factor, without waiting for an MFA reset.

A passkey doesn't turn on MFA for a user. Clerk doesn't prompt users who haven't set up MFA for a separate second factor. If you require MFA, those users must set up a second factor before sign-in finishes, including when they sign in with a passkey.

Get started

Native apps need clerk-ios 1.5.0, clerk-android 1.1.4, @clerk/expo 4.13.1, or later. Web apps need @clerk/clerk-js 6.40.0 and @clerk/ui 1.41.0 or later: upgrade your SDK to the minimum version in the versioning guide, and if you pin either package or bundle @clerk/ui, upgrade it too.

Then:

  1. If your application was created before July 8, 2026, turn on Passkeys satisfy multi-factor authentication under Sign-in with passkey on the User & authentication page. Newer applications already have it on, and native apps offer the passkey second factor once it's on.
  2. For web apps, opt in to the Passkeys as a second factor on the web update on the Updates page if your instance doesn't have it. Instances created on or after October 19, 2026 already have it, except production instances cloned from a development instance without it.

If you're building a custom flow, supportedSecondFactors can now include passkey. See the custom MFA flow guide to complete it, and the passkeys and MFA guide for SDK requirements.

Contributors
Daniel Moerner
Sean Perez
Sam Wolfand
Robert Soriano

Share this article

Test email addresses no longer receive email

Category
Product
Published

With test mode on, Clerk no longer sends any email to +clerk_test addresses.

Test email addresses are addresses with the +clerk_test subaddress, such as jane+clerk_test@example.com. With Test mode enabled in the Clerk Dashboard, automated tests can sign in using the fixed verification code 424242 instead of reading a code from an inbox.

Until now, Clerk skipped only verification codes and new device sign-in notices for these addresses, and still delivered every other email to them, including sign-in links, invitations, and receipts. Most test addresses aren't real inboxes, so those emails bounced, and bounces from test traffic hurt email delivery for every development instance.

Starting today, Clerk doesn't send any email to a test email address while Test mode is on. Emails that Clerk used to deliver are still recorded and trigger the email.created webhook, with delivered_by_clerk set to false.

What to change

If your test suite reads emails from an inbox, for example to follow a sign-in link or accept an invitation, send those emails to an address without +clerk_test. Emails to real addresses are delivered as before and count toward the development instance email limit.

Tests that sign in with the code 424242 don't need any changes.

Contributor
Jeff Escalante

Share this article

Agent feedback

Category
Product
Published

Let agents give product feedback directly from your MCP server, and review the feedback in Clerk.

Agents can now give product feedback through your MCP server. When a tool is missing, something unexpected happens, or an agent gets stuck, the agent often knows what would have helped, but you have no way to hear about it.

Add the submit_feedback tool from @clerk/mcp-tools to your MCP server, and agents report friction as they run into it. Your own agent can then read the reports through Clerk's MCP server and fix what other agents keep running into. For example:

  • "Summarize the feedback on my application."
  • "Look at the blocked reports and come up with new tools to add."

Get started

See Collect feedback from agents using your MCP server to add the tool to your MCP server.

Contributors
Bryce Kalow
Mitch Vostrez

Share this article

Introducing Clerk Protect

Category
Product
Published

Fraud and abuse protection built directly into your sign-up and sign-in flows.

Clerk Protect helps stop fake accounts and account takeover attacks with protections you can configure in the Clerk Dashboard. Clerk secures more than 100,000 active applications. Protect brings what we've learned fighting fraud and abuse directly into your authentication flows.

New protections on the Business plan

The Business plan now includes five advanced protections to give you more control over who can sign up:

Protections for every application

Every application includes the following protections:

Each protection is built and maintained by Clerk. Manage them together on the Protections page in the Clerk Dashboard. We'll keep adding protections as we find new ways to protect your application.

Get started

Explore Protect in the Clerk Dashboard and choose the protections that fit your application. See the getting started guide for requirements and setup instructions.

Contributors
Theo Zourzouvillys
Mike Wickett
Braden Sidoti
Brandon Romano
Steve Hayes

Share this article

Merge two users into one

Category
API
Published

A new Backend API endpoint merges a duplicate user into another and deletes the duplicate.

Sometimes one person ends up with two users in your application. Maybe they signed up with a work email and later signed in with Google under a personal one, or they unintentionally signed up again with a subaddress like jane+work@example.com (and Block email subaddresses was not enabled). An administrator for your application can always clean this up by deleting one user and adding what it had to the other, but this is a manual process. It also often meant asking the person to redo their own setup, like re-connecting their Google account or enrolling their authenticator app again.

Now you can do it in one call. Use our Backend API to merge a user into another, and Clerk moves its email addresses, phone numbers, connected accounts, passkeys, TOTP, backup codes, organization memberships and metadata onto the user you keep, then deletes the duplicate. When both users have a value for the same field, such as a name, password, username, metadata key, or role in an organization, the user you keep retains its current value.

A few things to know:

  • A merge can't be undone. Pass dry_run: true to see the merged user before committing to it.
  • The response includes the deleted user as it was before the merge, and a new user.merged webhook links the two, so you can keep track of merges in your own backend. Each merge is also recorded as a user.merged event in Admin Logs and Application Logs.
  • A merge isn't allowed if either user is managed by Directory Sync or if the user being deleted has an enterprise SSO account. If the Backend API rejects a merge, it returns the reasons.
Contributor
Daniel Moerner

Share this article

The Expo native components now ship in their own package.

Apps that don't use the native components no longer bundle the Clerk iOS and Android SDKs, and they no longer require iOS 17.

If you use <AuthView />, <UserButton />, or <UserProfileView />, install the package, rebuild your app, and update your imports:

npx expo install @clerk/expo-native-components
import { AuthView, UserButton } from '@clerk/expo/native'
import { AuthView, UserButton } from '@clerk/expo/native-components'

The old @clerk/expo/native import path is deprecated and will be removed in the next major version.

Ship the new app binary before any over-the-air update that includes this change. Without the package, native components throw an error at runtime.

On Android, apps without the package no longer migrate biometric credentials enrolled with earlier versions of the SDK, so some users may need to enroll again.

This change is available in @clerk/expo 4.11.0. See the native components overview for setup.

Contributors
Mike Pitre
Robert Soriano

Share this article