@itsclelia: I have one big problem with agentic engineering: I want agents to operate autonomously, but I also want granular, rever…
摘要
I have one big problem with agentic engineering: I want agents to operate autonomously, but I also want granular, reversible control over every change they make. I could solve this by committing every intermediate step to Git, but that would completely pollute my repo history. So I built 𝗮𝗴𝗴𝗶𝘁: a Git-like CLI for local and remote (S3-backed) agent artifact storage, written in Rust . With aggit, my agents can stash intermediate work, create branches safely, restore previous states, and back
查看缓存全文
缓存时间: 2026/05/11 10:38
I have one big problem with agentic engineering: I want agents to operate autonomously, but I also want granular, reversible control over every change they make. I could solve this by committing every intermediate step to Git, but that would completely pollute my repo history. So I built 𝗮𝗴𝗴𝗶𝘁: a Git-like CLI for local and remote (S3-backed) agent artifact storage, written in Rust . With aggit, my agents can stash intermediate work, create branches safely, restore previous states, and back up artifacts to my @RustFSofficial server with multi-instance replication support, all without touching the main Git repository. Once the results are ready, I can cleanly push the final changes to GitHub. Learn more → http://aggit.dev Install as an agent skill → 𝘯𝘱𝘹 𝘴𝘬𝘪𝘭𝘭𝘴 𝘢𝘥𝘥 𝘈𝘴𝘵𝘳𝘢𝘉𝘦𝘳𝘵/𝘢𝘨𝘨𝘪𝘵 Leave a → http://github.com/AstraBert/aggit
aggit | S3-backed, git-versioned object storage
Source: https://aggit.dev/ Rust CLI + S3
S3-backed, git-versioned object storage for agents. Track local files as compressed objects, branch safely, and sync reachable history to S3-compatible remotes.
$ aggit init .
$ aggit author -n "Jane Doe" -e "[email protected]"
$ aggit add notes.txt
$ aggit commit -m "initial commit"
$ aggit origin create prod -e https://s3.example.com -s *** -k *** -r us-east-1
$ aggit push prod
Core Capabilities
Git-like Local Engine
`blob`, `tree`, and `commit` objects are stored under `.aggit/objects` with branch-aware refs and index.
Branching + Recovery
Switch branches with clean-state checks, restore working trees from committed snapshots, and inspect history objects.
S3 Sync
Push only reachable objects beyond remote head; clone remotes back into `.aggit` and materialize files locally.
How It Works
`aggit` keeps a minimal Git-like store inside `.aggit/`: file contents are hashed into compressed objects, index entries are tracked per branch, and commits link trees plus parent pointers. On push, it computes objects reachable from local head and uploads only what the remote bucket is missing, alongside branch head and index. Clone performs the inverse: downloads `.aggit` data from S3 and restores the working tree from the selected branch commit.
相似文章
Grit:用Rust和智能体重写Git
本文介绍了Grit,这是一个用Rust重新实现的Git新版本,通过了超过99%的Git测试套件,并且是通过AI智能体创建的。它旨在提供一种基于库、内存安全的替代方案,以取代原版Git。
我们把AI当作魔术而不是软件对待,这让AI智能体变得难以维护。
文章认为,当前的AI智能体框架将智能体视为黑箱,导致其难以维护,并提出了一种基于Git的原生架构(Lyzr GitAgent、OpenGAP),在该架构中,智能体逻辑以平面文件的形式进行版本控制,并通过拉取请求实现回滚和可审计性。
我构建了 agentwerk,一个专注于高效完成任务的轻量级 Rust 库,用于扩展智能体协作
作者介绍了 agentwerk,这是一个轻量级的 Rust 库,旨在通过工单系统扩展智能体协作。它为 LangChain 或 AutoGen 等臃肿框架提供了更简单的替代方案,适用于无需人工干预的流水线。
我开始认为电子表格代理缺少了让编程代理真正可用的东西:Git
作者认为电子表格代理采用缓慢,因为它们缺乏Git风格的协作基础设施(差异、审查、回滚),而这正是编程代理可用的原因。作者宣布发布了一个早期运行时以弥补这一差距。
如何为你的AI代理进行版本控制和回滚?git让我失望,我感觉自己遗漏了什么。
一位开发者分享了使用git进行AI代理版本控制和回滚的困境,强调了提示词编辑导致的静默行为变化以及缺乏回归信号的问题。他们向社区寻求更好的工作流程。