“we also have the APIs and the CLI to be able to let agents automate this. So when they are doing things and automating code and branching and making pull requests and doing code review, there can actually be a mirror database state that is working in sync with all of those things, right?”
Video moment · 17:03 · youtube.com
From “Move Fast and Don’t Break Things: Scaling Databases for the AI Era — Ben Dicken, PlanetScale”, found 2026-10-15.
Dicken describes giving agents API and CLI access to database branching, so each agent branch or pull request gets a matching database state instead of every agent sharing one schema. Changes are merged through a deploy request and can be reverted. Quoted from YouTube’s auto-generated captions.