151 wires and counting

$ follow Supabase

Keep up with Supabase in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-10-14
stories 139

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

Scoped OAuth reconsent in Studio, MCP drops double cost prompts

By RepoJournal · Filed · About Supabase · Composed from the cited sources · methodology

Studio now shows only the scope differences when an already-authorized app asks for more access, and the MCP server stops making users confirm project and branch costs twice.

feat(studio): scoped oauth apps reconsent UI supabase/supabase

by djhi

When an app a user already added changes its requested scopes, Studio now defaults to showing only the scope differences rather than the full permission list, so reconsent reads as a diff of what is new. It can be exercised against the authorize flow with mock_scenario=reconsent.

fix(mcp): stop double cost confirmation on create_project and create_branch supabase/mcp

by barryroodt

Since the earlier tool-description change told models the user must agree to cost first, form-capable clients like Claude Code asked in chat and then showed the server's cost form, for two confirmations of the same charge. Every client now gets the same description: call the tool without that pre-agreement step.

fix(cli): name the failing engine operation in stack telemetry supabase/cli

by avallete

Local stack failures caused by a container engine command previously collapsed into one shared engine_command fingerprint, which recent prereleases flagged as the main cause of Docker start failures on Linux without saying which call broke. Telemetry now names the failing step: create, start, inspect, engine target lookup, remove, or wait.

chore(studio): storage versioning override conflict supabase/supabase

by fsansalvadore

Uploading a file whose name already exists used to silently create an incrementally numbered copy; Studio now prompts, with Replace existing file (kept as a version) or Keep both as the two options.

chore(cli): add permission building blocks for shared API calls supabase/cli

by Prashansa-K

The CLI is adding reusable permission building blocks for Management API calls made by shared modules rather than command handlers, groundwork for scoped personal access tokens that declare which permissions each command needs. Also landed: fullscreen is now the only pricing panel presentation after the pricingPanelPlanPresentation experiment concluded, with the control, parity, gaps and fullsc...

Quick answers

What shipped in Supabase on October 14, 2026?
Studio now shows only the scope differences when an already-authorized app asks for more access, and the MCP server stops making users confirm project and branch costs twice. In total, 64 commits, 64 pull requests, and 11 releases landed.
Who contributed to Supabase on October 14, 2026?
10 developers shipped this update, including supabase-evals-releaser, supabase-evals-releaser[bot], djhi, fsansalvadore, Mert YEREKAPAN, ChloeGarciaMillerand, Prashansa-K, and avallete, and 2 more.
What were the notable Supabase updates?
feat(studio): scoped oauth apps reconsent UI, fix(mcp): stop double cost confirmation on create_project and create_branch, and fix(cli): name the failing engine operation in stack telemetry.