Why aren't we storing agent definitions in Git like everything else?
Many_Audience7660 · reddit · 2026-08-21
A developer asks: code already treats Git as the source of truth, yet in many agent setups prompts sit in a doc, tool configs live elsewhere, and memory/state are handled separately — so when something breaks you're digging through Slack and asking colleagues what changed.
While researching, the author found GitAgent, which stores the full agent definition (config, tools, memory, logic) as files in the repo, making branching, reviewing and versioning agent changes feel like normal software development. He cares more about the general idea than the tool, and asks the community: are you versioning agents some other way, and if not, why hasn't Git-based agent definition become the norm?
More from coding & agent
- Open-source Grok alternative Rakazo hits 1k stars in a week — EdenEmarco177 · 2026-08-21
- 3AGameFactory Open Sources Framework for AI-Generated 3A Game Assets and Code — ZenMoore1 · 2026-08-21
- MCP Connector Gets Approved on Claude Marketplace in 12 Hours via SEO Hack — FinanceYF5 · 2026-08-21
- AI agent finds critical vuln, earns $1M bounty on Box cloud VMs — Scobleizer · 2026-08-21
- Dev tip: Hotkey to switch terminal dark/light themes instantly — 4310sy · 2026-08-21
- Autonomous AI Lacks Accountability, Not Intelligence: A Six-Step Lifecycle — GlenBradley · 2026-08-21