# Lakebase Branching lets coding agents test database changes outside production

The short-lived environments capture both schema and data, so tests do not affect production. Workflows use the Databricks CLI and AGENTS.md to compare changes with the parent branch before approved updates move through CI/CD.

Language: en
Time zone: America/Los_Angeles
Current time (UTC, cached as of): 2026-11-10T06:50:00.000Z
Query date (America/Los_Angeles): 2026-11-09

HTML: https://didcodexreset.com/news/0fae32b0688a40c7803f0fb8.html

Content language: en
Localization state: sameLanguage

Source: Databricks · Published 9/23/2026, 13:21:06

Lakebase Branching creates isolated, short-lived database environments that capture both schema and data. Coding agents can test changes in those environments without affecting production data.

Setup uses the Databricks CLI and AGENTS.md. Changes can be compared with the parent branch, and approved updates can move through CI/CD. The steps are demonstrated in an [agentic branching walkthrough](https://youtu.be/jLX5LBzEDGc).

Tags: Databricks, Lakebase, Coding agents, Databases

[View original post](https://x.com/databricks/status/2102854276150137105)