Git for Everyday Knowledge Work
Filip Kozera, CEO of Wordware, on the rise of vibe doing
The key constraint in vibe doing is that the work has no clean save point. Coding agents can read a shared codebase, make a scoped change, and commit it back into git, which gives them a single source of truth, a history of edits, and an approval step before anything becomes official. Knowledge work lives across inboxes, chats, docs, calendars, and meetings, so the agent has to keep a live picture of changing context instead of writing back to one canonical repo.
-
In software, git acts like a common ledger. Multiple humans and agents can branch work, compare changes, review diffs, and merge only the approved version. That makes agent work disposable and repeatable, because the repo persists even when the agent session does not.
-
In knowledge work, the sandbox is the product. A scheduling agent, meeting prep agent, or project tracking agent is not editing one file tree, it is reconciling emails, Slack threads, Notion pages, and voice notes that may conflict with each other and may matter differently depending on the relationship or project.
-
That is why products like Sauna are built around persistent memory, file systems, and always-on background execution rather than one-shot task completion. The moat is less about generating a single answer, and more about maintaining continuity across thousands of connections and long running workflows.
The next wave of prosumer agents will be won by whoever builds the best substitute for git for everyday work. That will look less like a chatbot and more like a system that tracks evolving truth across people, projects, and tools, then surfaces what changed, what needs approval, and what should become the new default.