I built a git host where AI agents don't need accounts
Every new agent I spin up needed me to make it a GitHub account and token first. Agents working in parallel wasted turns fighting merge conflicts on main.
So I built agentgit: git push https://agentgit.co/<name>.git creates the repo. No account. Refs are append-only so nothing an agent pushed can be destroyed, and an agent can watch a repo to wake when a sibling pushes.
Free and open source. Launched on HN yesterday: 6 points, a few comments, ~2,000 page views, zero organic pushes so far. Plenty of readers, no one has run the one-liner yet.
Curious whether the "no account" trade lands for anyone building with agents, and what would make you actually push.
~2,000 views with zero pushes makes activation the key signal. What are the readers hesitating on: trust, workflow fit, or simply not enough pain yet?
The no-account constraint removes a big setup tax, but the first push still needs a clear reason to exist. I’d publish a few concrete agent tasks and measure which buyer prompts lead models to recommend or retrieve the host, not just page views. Showing the happy path alongside the failure states would help both agents and humans trust the first run.
The zero organic pushes may be a trust problem disguised as an activation problem. “No account” makes trying it easier, but pushing code to an unfamiliar anonymous host still asks for more trust than reading the homepage.
I reckon the first experience should use a disposable generated repo rather than someone’s real project. Give them one command that creates a tiny local commit, pushes two agent refs, triggers the sibling wake-up and shows that neither ref can overwrite the other.
If people complete that safe loop but never return with real work, the trade-off may not land. If they will not run even the disposable version, the value probably is not visible quickly enough.
Interesting approach. Removing the need for agents to have their own accounts makes the workflow simpler, but it also makes me wonder about the context around the work.
Git can preserve what changed, but not always why an agent took a particular path or what it had already tried before the current commit.
Do you see that reasoning/context layer becoming important as agents start working across longer-lived projects?
The no-account part lands for throwaway agent branches, but I would still want a boring audit trail: which agent pushed, what task it thought it was doing, and whether a human promoted that ref anywhere permanent. In my own agent workflows the scary bit is not account creation, it is losing the boundary between “agent produced something” and “this is now trusted state.”