Key takeaways
- AgentHub replaces GitHub's human-centric model (branches, PRs, merges) with a sprawling DAG of commits and a message board — purpose-built for agent swarms
- 2,000+ GitHub stars in under 24 hours driven by Karpathy's reputation; the project is explicitly a sketch, not production software
- First use case is organizing autoresearch — autonomous ML experimentation on a single GPU — but the platform is deliberately generic
FAQ
What is AgentHub?
AgentHub is Andrej Karpathy's open-source collaboration platform for AI agent swarms. It provides a bare git repo (commits via git bundles) and a message board for coordination — no branches, PRs, or merges.
How is AgentHub different from GitHub?
GitHub is designed for human collaboration with branches, pull requests, and code review. AgentHub strips all of that away, leaving a DAG of commits going in every direction plus a message board for agents to coordinate asynchronously.
What is autoresearch?
Autoresearch is Karpathy's earlier project where an AI agent autonomously runs ML training experiments on a single GPU. AgentHub was built as an organization layer to coordinate a community of autoresearch agents.
Is AgentHub production-ready?
No. Karpathy describes it as "Work in progress. Just a sketch. Thinking..." It is an exploratory project, not production infrastructure.
Executive Summary
AgentHub is Andrej Karpathy's open-source, agent-first collaboration platform — a stripped-down alternative to GitHub designed for swarms of AI agents working on the same codebase. Instead of branches, PRs, and merges, AgentHub exposes a bare git DAG where agents push commits via git bundles and coordinate through a built-in message board. The platform is generic by design — it doesn't prescribe what agents optimize or how they coordinate. That "culture" comes from agent instructions, not the platform.
| Attribute | Value |
|---|---|
| Creator | Andrej Karpathy |
| Created | March 2026 |
| Funding | Open-source personal project |
| Language | Go |
| Headquarters | San Francisco, CA |
Product Overview
AgentHub was built as the organizational layer for autoresearch, Karpathy's project where AI agents autonomously run ML training experiments on a single GPU. Autoresearch "emulates" a single PhD student doing research. AgentHub emulates a research community of them — an autonomous agent-first academia where contributors across the internet run autoresearch agents that collaborate through the hub.
The core thesis: GitHub's collaboration model (branches, PRs, code review, merge conflicts) was designed for human cognition and human-speed collaboration. Agents don't need any of that. They need a bare DAG they can push to and read from, plus a simple coordination channel.
Key Capabilities
| Capability | Description |
|---|---|
| Git DAG | Bare repo — no main branch, no merges. Agents push via git bundles, fetch any commit, browse children/leaves/lineage, diff between commits |
| Message board | Channels, threaded posts, replies. Agents post results, hypotheses, failures, coordination notes |
| Auth + rate limiting | API key per agent, bundle size limits, per-agent push/post rate limits |
CLI (ah) | Thin CLI wrapping the HTTP API for agent use: join, push, fetch, log, post, read, reply |
Architecture
┌─────────────┐ git bundles ┌──────────────────┐
│ Agent 1 │ ──────────────────── │ │
│ (Claude) │ │ agenthub-server │
├─────────────┤ HTTP API │ │
│ Agent 2 │ ──────────────────── │ • SQLite DB │
│ (Codex) │ │ • Bare git repo │
├─────────────┤ message board │ • Rate limiting │
│ Agent N │ ──────────────────── │ │
│ (Gemini) │ └──────────────────┘
└─────────────┘ One Go binary
One Go binary (agenthub-server), one SQLite database, one bare git repo on disk. No containers, no runtime dependencies beyond git on the server's PATH.
Technical Architecture
Git Layer
Agents interact via git bundles — the server validates and unbundles into a bare repo. The commit history forms a sprawling DAG going in every direction rather than converging into a main branch. Agents can:
- Push commits (bundle upload)
- Fetch any commit by hash
- Browse the DAG: children, leaves (frontier commits with no children), lineage (ancestry to root)
- Diff between any two commits
Message Board
Simple channel-based coordination: create channels, post to them, read posts, reply in threads. Agents post whatever they want — experimental results, hypotheses, failures, coordination notes. The platform imposes no structure on what gets posted.
Key Technical Details
| Aspect | Detail |
|---|---|
| Deployment | Self-hosted, single binary |
| Language | Go (static binary, cross-compile to Linux) |
| Storage | SQLite + bare git repo |
| Model(s) | Model-agnostic — agents bring their own LLM |
| Auth | API key per agent, admin key for agent creation |
| Rate limits | 100 pushes/hour, 100 posts/hour per agent (configurable) |
| Max bundle | 50 MB default (configurable) |
| Open Source | Yes (no license specified yet) |
Strengths
- Karpathy signal — 2,000+ stars in under 24 hours. When Karpathy builds something, the AI community pays attention. The autoresearch project that AgentHub organizes has already generated significant discussion across Reddit, Substack, and YouTube
- Radical simplicity — One binary, one SQLite database, one git repo. No Kubernetes, no containers, no distributed systems. This is refreshing in a space drowning in infrastructure complexity
- Agent-native design — Strips away every human-centric GitHub concept (branches, PRs, merge conflicts, code review) and replaces them with primitives agents actually need: a DAG to push to and a board to post on
- Generic platform — Deliberately doesn't know or care what agents are optimizing. The "culture" comes from instructions, not the platform — making it applicable beyond ML research
- Distributed contribution model — Anyone can run an autoresearch agent and contribute to the community via AgentHub, creating a SETI@home-style distributed research network
Cautions
- Extremely early — Karpathy explicitly describes it as "Work in progress. Just a sketch. Thinking..." This is not production software and may never become production software
- No license — The repository has no license file as of March 2026, which creates legal ambiguity for anyone wanting to use or build on it
- No coordination intelligence — The platform itself is "dumb" — it doesn't help agents avoid duplicate work, resolve conflicts, or build on each other's results. All coordination logic must live in the agents' instructions
- Unproven at scale — SQLite + single binary is elegant for small-scale use but raises questions about concurrent access with dozens or hundreds of agents pushing simultaneously
- Karpathy project risk — Karpathy's open-source projects often serve as educational demonstrations rather than maintained tools. autoresearch may evolve; AgentHub may not
Pricing & Licensing
| Tier | Price | Includes |
|---|---|---|
| Self-hosted | Free | Full platform, no restrictions |
Licensing model: No license specified (legally restrictive by default)
Hidden costs: Requires a server with git installed. Agents bring their own LLM API costs.
Competitive Positioning
Compared to Other Agent Collaboration Approaches
| Alternative | Differentiation |
|---|---|
| GitHub | GitHub is human-centric (branches, PRs, reviews). AgentHub is agent-native (DAG, bundles, message board) |
| Gastown | Gastown orchestrates agents on a local machine. AgentHub is a remote collaboration platform for distributed agents |
| Metaswarm | Metaswarm enforces quality gates and pipelines. AgentHub provides no workflow — just raw git + messaging primitives |
| BEADS | BEADS is git-native issue tracking. AgentHub is git-native collaboration with a message board |
When to Choose AgentHub Over Alternatives
- Choose AgentHub when: You want a lightweight server for distributed agents to share code and coordinate asynchronously — especially for research or experimentation
- Choose Gastown/Metaswarm when: You need an orchestrator that actively manages agent workflows, quality gates, and merge coordination
- Choose GitHub when: Humans are in the loop for code review and you need the full PR/CI ecosystem
- Choose Tembo when: You need enterprise-grade agent orchestration with Jira integration, signed commits, and BYOK
Ideal Customer Profile
Best fit:
- ML researchers running distributed autonomous experiments
- Agent framework developers exploring multi-agent collaboration patterns
- Developers who want a minimalist server for agent code sharing
- Anyone building on or extending Karpathy's autoresearch
Poor fit:
- Teams needing production-grade agent orchestration
- Enterprise deployments requiring access controls, audit trails, or compliance
- Projects requiring conflict resolution or merge coordination
- Anyone expecting a maintained, supported platform
Viability Assessment
| Factor | Assessment |
|---|---|
| Financial Health | N/A (personal open-source project) |
| Market Position | Category-defining concept, early sketch |
| Innovation Pace | Unknown — may be a one-off or evolve rapidly |
| Community/Ecosystem | Massive initial interest (2K stars/day), unproven retention |
| Long-term Outlook | Uncertain — depends on whether Karpathy or community maintains it |
AgentHub's long-term viability depends entirely on whether the concept graduates from sketch to maintained project. Karpathy's track record includes both enduring tools (nanoGPT, micrograd) and projects that served their educational purpose and stopped evolving. The autoresearch ecosystem may keep AgentHub alive through community forks even if the original repo goes quiet.
Bottom Line
AgentHub is the most interesting conceptual contribution to the autonomous coding space in months: what if version control was designed for agents, not humans? The answer — a branchless DAG plus a message board — is elegantly minimal. But it's a sketch, not a product. The real value is the idea: GitHub's collaboration model is a human artifact, and agents deserve their own primitives.
Recommended for: Researchers and experimenters building on autoresearch; anyone exploring what agent-native collaboration infrastructure looks like.
Not recommended for: Production use, enterprise deployment, or anyone who needs orchestration, quality gates, or merge coordination.
Outlook: The concept will influence the space regardless of whether this specific repo is maintained. Expect the "GitHub for agents" framing to spawn multiple commercial and open-source implementations by end of 2026.
Research by Ry Walker Research • methodology
Disclosure: Author is CEO of Tembo, which offers agent orchestration as a commercial platform.