Loading post…
Supabasejgoux, wenboAnnouncement
A local Supabase project per agent, with or without Docker
Summary
The Supabase CLI v2.119.0 introduces an experimental native runtime that runs all 13 services as plain processes without Docker, reducing startup time by over 80% and idle memory by 89%. It also supports multiple local projects on one machine via git worktrees, each with its own Postgres, Storage, Edge Functions, and MCP server on auto-assigned ports. This allows each coding agent to have an independent database to reset and test against without affecting others, making a project per worktree practical on a laptop. Remote branches now inherit configuration from their base project and are ready nearly five times faster, with function bundles copied in parallel. The native runtime runs on Linux and macOS, and Docker remains the default when present, but the CLI automatically selects native when Docker is absent.
Context
Developers running multiple coding agents need separate Supabase environments per agent, but coordinating ports and project IDs manually is cumbersome, and Docker-based local projects consume significant memory and startup time.
Approach / What changed
The Supabase CLI v2.119.0 introduces an experimental native runtime that runs all 13 services as plain processes without Docker, and supports multiple local projects on one machine via git worktrees, each with its own Postgres, Storage, Edge Functions, and MCP server on auto-assigned ports. Remote branches inherit configuration from their base project and are ready nearly five times faster.
Takeaways
The native runtime reduces startup time by over 80% and idle memory by 89%, making it practical to run multiple local projects on a laptop.
Multiple local projects can be created using git worktrees, each with independent services and auto-assigned ports, eliminating manual coordination.
Remote branches now inherit Auth, Storage, network restrictions, and deployed Edge Functions from the base project, and function bundles are copied in parallel for fast creation.
FAQ
How do I set up multiple local Supabase projects for different agents?
Create a git worktree for each agent, run `supabase start` in each, and the CLI assigns unique ports and remembers them across restarts. Each worktree gets its own Postgres, Storage, Edge Functions, and MCP server.
How do I run Supabase locally without Docker?
Use the native runtime by setting `--runtime native` or let the CLI auto-select it when Docker is unavailable. It runs all 13 services as plain processes on Linux and macOS.
How do remote branches work faster?
Remote branches inherit configuration from the base project, and function bundles are copied in parallel, so a project with 40 functions comes up as fast as one with two. Branches are ready nearly five times faster.
Source and freshness
- Source
- supabase.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.