Supabase CLI v3 flips the default to local, as the Postgres tools race toward agents

Supabase goes local-first

The week's biggest shift came from Supabase, which cut a major CLI release that makes the local stack the default target for every command that can run locally. The deprecated --linked, --project-ref and --db-url flags collapse into a single --remote, and any change to a hosted project now prompts for confirmation — failing outright in unattended CI unless you pass --yes. An experimental per-project local stack ships behind an environment variable.

The config package got the same treatment: 1.0.0 removes db remote commit, several inspect aliases, and the bundled supabase-go binary, and replaces [inbucket] sections with [local_smtp]. The resolution order is now flag > shell environment > project env files > config file > default, which has a sharp edge: SUPABASE_* variables sitting in .env files now beat matched [remotes.*] blocks and get pushed to the linked project. The config package also reads and writes JSONC and commented JSON configs and adds an auth.email require_current_password setting. Behind it all, the CLI now skips Docker's first health check wait for faster cold starts, caps API retries with SUPABASE_API_MAX_RETRIES, and pins the Supabase CA on linked database connections in the next major's preview line.

Two things soften the migration. A maintenance release adds v2 install channels — npm supabase@v2.stable, Homebrew supabase@2, Scoop supabase-v2-stable — for teams that can't move CI yet; v2 now receives only security and fundamentally-broken-behavior fixes. Separately, the changelog's CLI v3 announcement is mandatory reading before upgrading automation.

Supabase's client libraries had their own breaking week: supabase-flutter v3 types queries, functions, realtime and auth, changing v2 behavior for anyone who upgrades — nothing breaks until you do, but the migration guide covers what the compiler won't catch. Supabase JS added Realtime broadcast persistence, per-request custom fetch via query builder options on .from, and fixed global sign-out clearing the local session when the server failed, plus storage's exists reporting bad JWTs and missing buckets as missing files.

Neon opens the gateway and undoes deletions

Neon's week centered on access: AI Gateway prepaid credits are now purchasable on the Free plan starting at $5, giving one credential across 60-plus OpenAI, Google and other provider models. The same changelog brought seven-day project recovery in the Console and automatic compute updates for computes up to 16 CU, autoscaling included, so no manual restarts.

Neon's AI surface kept expanding. The Function Registry installs working templates — Vercel Chat SDK, Mastra, TanStack AI, Context.dev — with one command, so agents start from code rather than docs. The MCP server adopted the stateless MCP 2.0 spec and retired its SSE endpoints, now handling more tool calls and roughly double the daily active users of the Neon CLI. Managed Better Auth gained the OAuth Provider plugin, turning auth instances into OAuth 2.1 authorization servers that MCP clients can log into. And a deep architecture post showed Lakebase Postgres serving 99.99999% of reads without touching object storage — the compute node's local cache answers 99.46% of page accesses, with object storage reads confined largely to branches, restores and wake-from-zero first reads.

PlanetScale hardens credentials and backups

PlanetScale attacked long-lived secrets first: GitHub Actions and Depot CI can exchange OIDC tokens for short-lived PlanetScale service tokens under an admin-defined trust policy, so no more stored credentials in CI. On the resilience side, emergency backups for Vitess copy directly from the running database when regular backups are failing, optionally from a replica to spare the primary. The MCP server moved onto four dedicated egress IPs — Postgres databases behind IP restrictions must allow all four — and gained feedback and question tools so agents can report wrong results or docs gaps. Terraform provider v1.18.0 manages VTGate, VTTablet and MySQL parameters, and the CLI added branch maintenance windows, events and replica detach as well as system-CA verification of role connection URLs.

Elsewhere, Prisma's v8 release candidate makes Postgres scalars convenience types and lets extension packs find Supabase via the search path, with MongoDB indexes now carrying their names through migrations.