8d – Agent-Native Version Control, where Git breaks

Hey HN, We built GitAgent — a git-native, framework-agnostic open standard for defining AI agents. The idea is simple: your repo IS the agent. npx @open-gitagent/gitagent@latest run -r https://github.com/shreyas-lyzr/architect -a claude That one command clones the repo, reads agent.yaml + SOUL.md + skills/, and launches it with Claude Code. Switch `-a openai` or `-a lyzr` to run the same agent on a different framework. No code changes. Goal: is keep the gitagent as a open standard ledger for an AI Agent in a VM, with versioned memories, skills etc. An agent is…

hi guys. been working on something i think is fundamentally missing in today's workflow with ai agents. vcs. i find myself struggling with questions that agents can't answer like "why did you do it?", "when did u delete this folder? why?", etc. or trying to /rewind (after a /compact...) or basically `bisect` to find when and why something was done by the agent in the current / previous session. just like git did for code, i think we are the same core capabilities with ai agents so... i developed an open source solution for that (currently supporting claude code) would love to…

Agent-native version control for parallel AI swarms

Version Control for AI agent Activity

I built unf after I pasted a prompt into the wrong agent terminal and it overwrote hours of hand-edits across a handful of files. Git couldn't help because I hadn't finished/committed my in progress work. I wanted something that recorded every save automatically so I could rewind to any point in time. I wanted to make it difficult for an agent to permanently screw anything up, even with an errant rm -rf unf is a background daemon that watches directories you choose (via CLI) and snapshots every text file on save. It stores file contents in an object store, tracks metadata in SQLite, and…