Agents are great at ls, grep, cat, editing files, and understanding the world through directories. So from an interaction standpoint, File sometimes fits an Agent better than Database.
But Agents also need database capabilities: search, indexing, Transaction, Version, Branch, Rollback, and Query. So we started asking: can an Agent see a File, while what's behind it is actually Database power? That's a core idea behind products like Filesystem / drive9.
I ran into the same question building baby lovable — putting the code source of truth on GitHub always felt constrained, but a traditional DB doesn't solve it either
Skip to content
Agents are great at ls, grep, cat, editing files…
From X · @therealfreddyx
Thoughts
mew～
Agents are great at ls, grep, cat, editing files, and understanding the world through directories. So from an interaction standpoint, File sometimes fits an Agent better than Database.
But Agents also need database capabilities: search, indexing, Transaction, Version, Branch, Rollback, and Query. So we started asking: can an Agent see a File, while what's behind it is actually Database power? That's a core idea behind products like Filesystem / drive9.
I ran into the same question building baby lovable — putting the code source of truth on GitHub always felt constrained, but a traditional DB doesn't solve it either
But Agents also need database capabilities: search, indexing, Transaction, Version, Branch, Rollback, and Query. So we started asking: can an Agent see a File, while what's behind it is actually Database power? That's a core idea behind products like Filesystem / drive9.
I ran into the same question building baby lovable — putting the code source of truth on GitHub always felt constrained, but a traditional DB doesn't solve it either