How it started
The agent could write. That was the problem.
Abhishek was building ACRED India, a real estate company, and hit a simple wall: the moment an AI agent can change real data, one bad run can wreck it. So teams keep agents read-only, or build staging tables and approval queues by hand.
In late September 2026, developers on Reddit described the same thing. Two had already had an agent wipe production data. Most said the branch is the easy part, and the merge is what has to be trusted.
So that is what Chronos is for. An agent works in its own copy of your data, you can read exactly which rows changed, and your rules decide what lands by itself and what waits for a person.
- beforeTailsMart and ACRED Indiastopped
Abhishek built both, then stopped to focus on one thing: the world's best database for the agentic era.
- First commit of Chronos2026
- Chronos DB 0.4.8 and Gateway 0.2.9 outlatest
