Recommended local development workflow with WorkOS

[LeoDoldan7]

Problem

Our team (~10 developers) uses WorkOS, but we’re struggling to find a good workflow for local development. Right now, some developers are resorting to using production credentials because authentication doesn’t work reliably when running the entire product locally.

We’d like guidance on the best practices or recommended workflow for this scenario.

Goals

We want a local development setup that allows:

1. Using the WorkOS development environment (not production).
2. Creating new users as needed.
3. Easily deleting users so they can be recreated.
4. Seeding users via a simple script (e.g., a JS script).
5. Isolated environments per developer (so multiple devs can create users with the same email addresses).

Question

What workflow do you recommend for local development with WorkOS that meets the above goals?

[gorcevich]

It also would be really helpful if Supabase provided an option to configure WorkOS (AuthKit) as a third-party auth provider directly in the Supabase CLI. That way, we wouldn’t need to spin up a hosted Supabase project just to test — we could test locally instead.