Databricks Lakebase branches databases per coding agent
A Databricks blog post explains how Lakebase Postgres database branching supports coding-agent workflows: using copy-on-write, a full database branch can be created from a parent in under a second regardless of size, and branches scale to zero so idle ones incur no compute cost. The walkthrough gives each agent and each pull request an isolated ephemeral branch, combining Git worktrees, a post-checkout hook, GitHub Actions and Drizzle migrations, applying migrations to both a preview app and the main branch and posting a schema-diff comment on the PR. The author notes that Lakebase branches are not merged back to the main branch like Git; schema changes are promoted through migrations in code, and the speed and cost claims come from Databricks' own blog.
As coding agents take on more parallel development work, database isolation is an easily overlooked part of the agentic development loop, and branching offers one way to keep each agent and change isolated.