A different place to put the agent definition

A March 13, 2026 Show HN thread introduced GitAgent, a proposal to define AI agents as ordinary files inside a git repository rather than as framework-specific JSON blobs or hosted configuration. The project’s core structure centers on files such as agent.yaml, SOUL.md, SKILL.md, plus optional folders for memory, tools, knowledge, hooks, and compliance metadata. At crawl time, the HN post had 114 points and 24 comments.

The pitch is straightforward: if the agent is just a repo, teams inherit version control, branching, pull requests, review history, and rollback mechanics automatically. GitAgent’s own examples lean hard into that operational framing. The site describes branch-based deployment, shared context in monorepos, and “stateless compute, git as state,” where runtime events are committed back into repository history instead of being hidden in an external service.

Why developers on HN noticed it

The useful part is not the branding but the attempt to reduce agent fragmentation. The HN launch post argues that switching agent frameworks often means rewriting the agent itself. GitAgent’s answer is a portable filesystem-shaped contract that can be adapted into multiple runtimes instead of authored separately for each one. The public site similarly positions it as a framework-agnostic standard with adapters and export paths, rather than a single execution engine.

That matters because agent tooling is getting more stateful, more proprietary, and more UI-driven. Git-native definitions push in the opposite direction. They make prompts, skills, runtime memory, and governance artifacts diffable and reviewable in the same workflow developers already use for code. For regulated or high-change environments, that is arguably more interesting than yet another agent chat surface.

What still has to be proven

The HN comments were pragmatic. Readers wanted to know which adapters actually work today, how stable the schema is, and whether repo-shaped agents reduce real operational friction or just rename it. Those are the right questions. But even at this early stage, GitAgent is a concrete signal that part of the agent ecosystem is moving toward auditable, file-based definitions rather than opaque platform state.

Primary source: GitAgent. Community discussion: Hacker News.

#open-standard

Show HN: GitAgent Treats AI Agents as Git Repositories Instead of Framework-Locked Configs