I fixed a bug where Jazz's SvelteKit plugin didn't apply its configuration correctly the very first time you started the dev server. The plugin now restarts Vite once after allocating the app ID, so SvelteKit's server hooks pick up the config properly.
I fixed broken configuration and authentication in several of Jazz's example applications. The affected apps — including WorkOS auth, Better Auth, Next.js CSR/SSR, Cloudflare Workers, and managed runtime — had issues that stopped developers from using them as working references.
I removed leftover jazz_principal_id JWT claims from the starter templates. Jazz only reads the sub claim to identify users, so this extra claim wasn't doing anything — it was just confusing people who were reading the starter code and thinking it was important.
I restructured the auth documentation to be organized around mental models with framework-specific tabs. I also moved the more technical theory into a new internals reference page covering things like Ed25519 key derivation, JWT structure, and how provider upgrades are verified.
I updated the create-jazz CLI spinner to show progress counts while it fetches GitHub dependencies, so you can see how far along it is instead of staring at a static spinner. I also cleaned up some console warnings that were corrupting the output.
I added jazz-wasm as a direct dependency to six Vite-based starter templates. When using pnpm, packages only get hoisted to the top level if they're listed as direct dependencies, so without this change the starters would fail to resolve jazz-wasm at runtime.
I fixed a bug where JazzProvider in React would tear down and recreate the Jazz client unnecessarily. The issue was that a config object in the useEffect dependency array was triggering cleanup on every render. I switched it to use a stable string key instead, which prevents the cycle.
I updated the Jazz Vite plugins to automatically inject worker.format: "es" and optimizeDeps.exclude: ["jazz-wasm"] via a config hook. This removes the need for developers to add these settings manually to their Vite config.
I added instructions to the project's CLAUDE.md telling AI coding agents to investigate unexpected test failures rather than assuming they're pre-existing, and to never rewrite tests without asking the developer first.
I replaced two placeholder texts in the "What is Jazz?" blog post with proper markdown links — one pointing to the Discord community and one to the booking calendar.
I migrated several example apps (chat-react, moon-lander-react, wequencer) to use the new jazzPlugin() from jazz-tools/dev, switched wequencer to local-first auth, fixed a WebSocket proxy issue, and cleaned up permission configurations.
I added an AGENTS.md file to all nine starter templates, directing AI coding agents to fetch live Jazz documentation rather than relying on their training data. This helps agents give more accurate and up-to-date advice when working in Jazz projects.
I added a jazz-tools schema hash command that prints the short hash of your current schema.ts file locally, without hitting the server or writing a snapshot. Handy for checking if your local schema matches what's deployed.
I replaced the temporary jazz2-docs.vercel.app URLs with the permanent jazz.tools domain across all starter AGENTS.md files.
I added three plain-Vite React starters alongside the existing Next.js/SvelteKit ones, and moved the Jazz Cloud provisioning step into the create-jazz CLI itself with a --hosting flag so you can set up hosting during scaffolding.
I added a fallback so Jazz apps work in Firefox private browsing mode. When the browser blocks access to the Origin Private File System (OPFS) with a SecurityError, the app now transparently falls back to in-memory storage instead of crashing.
I added schema validation warnings to jazz-tools deploy that flag tables without explicit permission policies. The warnings are informational only and don't block the deploy, but they help catch accidental permission gaps before they reach production.
I added an interactive widget to the quickstart docs that generates an app ID, admin secret, and backend secret from the hosted Jazz Cloud service. It automatically substitutes the generated values into the code examples on the page.
I built an interactive CLI scaffolder so you can run npm create jazz to bootstrap a new project. It prompts for your framework choice and auth mode, then fetches the right starter template, resolves dependencies, and initialises git.
I added an AuthBackup component to four local-first starter templates with recovery phrase and passkey backup/restore support. This gives users a way to recover their account if they lose their device.