Blog
Agents that write. Data you trust.
How to let AI agents change real data without reading every change: a branch for each run, rules that decide what merges, undo, and what we measure and learn building Chronos.
Can you merge a database branch back?
Sometimes. Most database branching gives you a copy to work in and discard; merging changed rows back is a separate feature. What Postgres templates, Neon, Dolt and Chronos each do, and when to use which.
Abhishek DG · 6 min readMore posts
How to let an AI agent write to MySQL safely
The agent works in its own branch of a copy of your tables; each approved merge is one InnoDB transaction with every row compared first. Setup, the write-back, and what happens to AUTO_INCREMENT ids.
Abhishek DG · 5 min readHow to let an AI agent write to MongoDB safely
The agent works in a branch of a copy of your collections; each approved change is one multi-document transaction that sends only the fields that changed. What it needs, and what is not there yet.
Abhishek DG · 4 min readHow do you add AI agents to your product without giving them your database?
Give each agent task a private copy of one customer’s rows and a token for that task only. Changes reach your database through a checked merge, inside your rules or after a person approves.
Abhishek DG · 5 min readWhat happens when an AI agent acts on data that changed?
Nothing stops it: a database only notices two writers on one row, not a decision made from a row that moved. Record what each agent run read, and hold its merge when any of it changed.
Abhishek DG · 5 min readHow do you stop two AI agents breaking a rule together?
Two changes can each be fine alone and wrong together. A merge check is a query that must find nothing in the merged result, run inside every merge before anything is written.
Abhishek DG · 4 min readWhere is Chronos DB slower than Postgres, DuckDB and Redis?
Analytics over large tables, some reports against Postgres, merges when a thousand agents commit at once, and raw vector-search speed. Our own numbers, with the reasons, and what Chronos is not.
Abhishek DG · 5 min readHow to let an AI agent write to your Postgres safely
Give each agent run its own branch of the data, read the diff, and let a merge policy decide what reaches Postgres. A ten-minute setup with Chronos DB, and what it doesn’t protect against.
Abhishek DG · 8 min readWhich rules should decide what an AI agent may change?
Start with no deletes without a person, then cap rows per merge and name the tables and columns that always wait. Three lines of SQL replace reviewing everything an agent does.
Abhishek DG · 5 min readHow do you undo what an AI agent did to your database?
Put back only the rows the agent changed, without restoring a backup and without losing anyone else’s work: one merge, or everything one agent did since a time.
Abhishek DG · 5 min read