---
title: "Supabase Select 2026 Recap"
description: "Supabase announced a code-first approach at its Select 2026 event, enabling developers to store schema and configuration in code so coding agents can set up and modify projects end to end. Local Supabase now runs as native processes without Docker, allowing multiple instances per directory and compatibility with sandboxes like Claude Code. A new MCP server lets application users connect their own agents, authenticating through existing Auth flows and enforcing row-level security on every tool call. Operational tools include Health Check Advisors for error rates, Database Connections for session management, Explorer notebooks for unified SQL and log queries, and query_logs for agent monitoring. Scaling features encompass Multigres for multi-node Postgres high availability, OrioleDB to avoid table bloat and VACUUM, Supabase Pipelines for near real-time data streaming to analytics platforms, and dbarena for transparent benchmarks."
---

# Supabase Select 2026 Recap

[Supabase](https://yomu.fyi/company/supabase) · oli\_rice, inian, jonny · Oct 2, 2026

**Type:** Announcement

## Summary

Supabase announced a code-first approach at its Select 2026 event, enabling developers to store schema and configuration in code so coding agents can set up and modify projects end to end. Local Supabase now runs as native processes without Docker, allowing multiple instances per directory and compatibility with sandboxes like Claude Code. A new MCP server lets application users connect their own agents, authenticating through existing Auth flows and enforcing row-level security on every tool call. Operational tools include Health Check Advisors for error rates, Database Connections for session management, Explorer notebooks for unified SQL and log queries, and query\_logs for agent monitoring. Scaling features encompass Multigres for multi-node Postgres high availability, OrioleDB to avoid table bloat and VACUUM, Supabase Pipelines for near real-time data streaming to analytics platforms, and dbarena for transparent benchmarks.

## Context

Coding agents can write application code but cannot set up, monitor, or fix the backend end to end. This work remains manual in the dashboard and docs.

## Approach / What changed

Schema and configuration can now live in code, managed via pg-delta for migrations and supabase config pull. Local development runs as native processes without Docker. An MCP server allows users to connect their own agents. New operational features include Health Check Advisors, Database Connections, Explorer notebooks, and query\_logs. Scaling includes Multigres, OrioleDB, Supabase Pipelines, and dbarena benchmarks.

## Takeaways

- Supabase now works code first: schema and configuration live in SQL files and project settings in code, enabling agents to declaratively set up and change projects.
- Local Supabase runs as native processes without Docker, supporting multiple simultaneous instances per directory for parallel checkouts.
- Multigres provides multi-node high availability for Postgres with built-in connection pooling, while OrioleDB replaces the heap to avoid table bloat and VACUUM.

## FAQ

### How do users connect their own agents to a Supabase app?

Users connect through the new app-level MCP server, which runs as an Edge Function. They sign in through your existing Auth flow, and every tool call runs as that user, with your RLS policies determining access.

### What can the Database Connections feature do?

It shows which sessions hold connections, run long, or are blocked, and who holds the lock. You can then cancel a query or terminate the connection directly from the dashboard.

### How can I stream production data to analytics tools without impact?

Use Supabase Pipelines to stream Postgres data in near real time to BigQuery, ClickHouse, DuckLake, or Snowflake. This keeps analytics queries off your production database.

**Tags:** [AI Agents](https://yomu.fyi/topic/ai-agents), [Benchmark](https://yomu.fyi/topic/benchmark), [MCP](https://yomu.fyi/topic/mcp), [Postgres](https://yomu.fyi/topic/postgres), [Supabase](https://yomu.fyi/topic/supabase)

- Source: [Supabase](https://supabase.com/blog/supabase-select-2026-recap)
- Source URL: https://supabase.com/blog/supabase-select-2026-recap
- Ingested by Yomu: 2026-10-02T21:00:06.208Z

[Read original post](https://supabase.com/blog/supabase-select-2026-recap)