You asked for a ConjureForge-branded authentication experience instead of the default Clerk styling. This screen now becomes the product-owned entry point for sign-in and sign-up flows.
Aligns login entry with the forge glyph used in the preview loader and browser tab.
Sets up V2 auth UX so project ownership and memory can stay scoped to real users.
Uses Clerk-backed verification in configured environments while keeping a development-only local fallback path.
Welcome back
Continue into your projects, memory, plans, and execution history with your ConjureForge identity.
This branded auth screen now prioritizes Clerk-backed verification and trusted ConjureForge session cookies, with the local email fallback reserved for explicitly allowed development flows.
Clerk now runs directly inside this branded auth screen on the app domain, and the server can verify Clerk sessions via JWT or JWKS while also syncing the trusted ConjureForge session cookie when needed.