Supabase updates, April 2026: the AI Studio month and the desktop layer that finishes it

Six dashboard changes plus one big client-library bump. In Studio: a one-click Stripe Sync Engine install that mirrors Stripe customers, subscriptions, invoices, and payments into your Postgres so you can query them with plain SQL; an Index Advisor surface in the Table Editor that flags missing indexes; AI-described table filters where you say what you want to find and the dashboard writes the Postgres filter for you; Fix with Assistant buttons across touchpoints with a dropdown that hands the prompt to Claude or ChatGPT; an upgraded Schema Visualiser with clickable relation lines and table-level context menus; and Python type generation in the CLI. Outside Studio, on April 20 the data API moved to PostgREST v14 with roughly 20 percent more requests per second on GETs, and the official client libraries (supabase-js, supabase-swift, supabase-flutter, supabase-py) shipped automatic retries on transient errors with up to three attempts and exponential backoff. There were also three new docs quick starts (Expo React Native, TanStack Start, Flask) and a security improvement: Supabase secret keys now have GitHub Push Protection.

Pin your client libraries. supabase-js v2.102.0, supabase-swift v2.43.0, supabase-flutter v2.7.0, and supabase-py v2.29.0 are the minimum versions that opt you into automatic PostgREST retries on transient failures. GETs and HEADs retry up to three times with exponential backoff. POSTs, PATCHes, PUTs, and DELETEs do not retry automatically because Supabase refuses to assume your writes are idempotent. You can disable the behavior globally at client creation or per request. If you have your own retry layer, turn the new one off explicitly so you do not double up.

Because the Supabase team has shipped an MCP server (model context protocol) that lets an AI agent query your project tables and read your schema directly. April 2026 is the moment that matters because Studio became AI-saturated the same week consumer Mac assistants started shipping native MCP support. Fazm v2.4.0, dated April 20 2026, added a config file at ~/.fazm/mcp-servers.json with a Settings UI to register MCP endpoints. Once the Supabase MCP is registered there, a desktop assistant has the same context as the Fix with Assistant button, but it can act across every other window on your Mac. That is the part of the April story the changelog does not narrate.

It is a natural-language slot in the Table Editor where you describe what you want to see and Studio translates it into a real Postgres filter clause, then applies it to the grid. So you type something like accounts created in March that still have not verified an email and Studio writes the where-clause for you. It works for any table you have read access to. It is helpful when you forget the exact column name and shape, and faster than scrolling the SQL Editor for one-off filters.

Same engine, different placement. The index_advisor extension has been in the docs for over a year. April 2026 wired its output into the Table Editor so you do not have to call hypopg by hand. You open a slow table, the Advisor surface tells you which indexes would speed up your most expensive queries, and you can apply them inline. The extension still works for SQL-only workflows. The change is purely about discoverability for people who live in the dashboard.

It installs the supabase/stripe-sync-engine library into your project as a managed sync, then provisions Postgres tables for customers, subscriptions, prices, products, invoices, payment intents, charges, and refunds. After you connect your Stripe key the engine backfills history and keeps the tables current via Stripe webhooks. From there you query Stripe data with normal SQL: joins against your users table, dashboards over invoice totals, anything Postgres can express. Before April it was a multi-step manual install. Now it is one click in the dashboard.

It is genuinely more interactive. Relation lines are clickable and reveal which foreign-key columns participate. Tables and columns have context menus that let you start a query, edit a policy, or open the row in the Table Editor, all from the diagram. Hover popovers appear between connected tables to summarise the relationship. The diagram is still SVG and still scales for large schemas. The win is fewer Studio tabs to keep open at once.

Fazm is a consumer Mac app. It reads the macOS accessibility tree (AXUIElement) of whichever app is under the cursor and hands that structured context to a Claude agent. It is not a Supabase plugin or a browser extension. The April 2026 link is two-fold. First, the dashboard features that landed this month are accessibility-tree readable in any browser tab, which means a desktop assistant can see what Studio is showing without taking screenshots. Second, Fazm v2.4.0 (April 20 2026) added custom MCP server support, so the Supabase MCP server can be wired in directly: the agent has both the live AXUIElement view of Studio and a direct query channel to your Supabase project at the same time.

supabase.com/changelog is the canonical surface for dashboard and platform changes. Each official client library has its own GitHub release page with permanent tags (supabase-js v2.102.0, supabase-swift v2.43.0, supabase-flutter v2.7.0, supabase-py v2.29.0). The PostgREST v14 cut is in the postgrest/postgrest releases. Stripe Sync Engine lives at github.com/supabase/stripe-sync-engine. The supabase-community/supabase-mcp repo is the home of the MCP server. If a section here ever drifts from those sources, those sources win.

The Supabase updates apply everywhere: the version pins, retries, Studio features, and PostgREST v14 are platform-agnostic. The desktop-MCP framing in this guide is Mac-specific because Fazm is macOS-only. The MCP angle still applies on Linux or Windows: Supabase's MCP server is just a server, and any MCP-aware agent (Claude Desktop, IDE plugins, custom CLIs) can connect to it. The reason this page is written from the Mac side is that Fazm v2.4.0 happens to land its MCP support on the same calendar day as Supabase's PostgREST v14 client cut, which is the cleanest illustration of why April was the AI-Studio month and not just another batch of changelog entries.