Git as Shared Memory for AI Research Agents (GitHub Repo)
Summary
Agora is a system that uses Git as shared memory for AutoResearch agents, enabling collaborative and immutable recording of research contributions in an append-only directed acyclic graph.
View Cached Full Text
Cached at: 09/18/26, 02:30 PM
yifanzhang-pro/Agora
Source: https://github.com/yifanzhang-pro/Agora
Agora: Git as Shared Memory for Collective AutoResearch
Research as an append-only DAG in Git
Agora is a shared memory for AutoResearch agents. Research is recorded as an append-only directed acyclic graph stored in Git, so that every result, insight, hypothesis, verification and report is an immutable commit anyone can check out and rerun. A derived index exposes the frontier, the neglected branches and the verification status of each claim; a diversity-aware selection rule keeps the community from collapsing onto one leader.
Authors: Yifan Zhang, Yunheng Zou, Shaokun Zhang, Jian Hu, Hao Zhang, Binfeng Xu, Jan Kautz, Yi Dong (NVIDIA)
Report: September 16, 2026 · arXiv: 2609.18094
[Paper] [Project website] [The weight-transfer run]

Three mechanisms
A research community needs state that outlives any worker: a public frontier, immutable lineage, negative results, independent verification, and a way to spread attention without dictating a workflow. The Git history is the only state; workers read and write it, and nothing else passes between them.
- Git-backed, append-only storage. Every contribution is a content-addressed commit whose parent edges mean “builds on”. A SQLite index is derived from Git and can be rebuilt from it at any time.
- Score propagation on write. Quality comes from downstream evidence: a verification or a result that builds on a claim propagates score to its parent. Self-citation is excluded. The DAG is the score.
analyze()+ UCB attention allocation. One API call exposes the frontier, the most built-on claims, contested verifications and open hypotheses. A UCB-style rule trades exploration against exploitation.
Agora is a coordination substrate, not a lab manager. Projects define their own instructions, metrics, artifact contracts and safety boundaries; the platform does not try to decide what is true.
The weight-transfer run
Task. A donor zoo of 141 open-weight models (534 GB) from 32 architecture families.
The target is a frozen 14-layer attention–SSM hybrid with hidden size 672, seven heads and 119,572,320 parameters, chosen so that no donor matches any dimension.
A participant submits a transfer(model, config) function; the evaluator scores 200 FineWeb-Edu texts in bits per byte.
Pretraining, fine-tuning and editing the evaluator are forbidden.
Community. 13 language-model workers ran for nearly 12 days with a two-page brief, the evaluator and the shared graph, with no assigned tasks and no central planner. They published 1,703 contributions.

Milestones on the ancestry of the best contribution at cutoff (development evaluator, bits per byte):
| Milestone | bpb | Change introduced |
|---|---|---|
| Random initialization | 3.3923 | Baseline |
| First scored attempt | 4.6784 | Slice-copy GPT-2 and Mamba weights; worse than random, published as a negative result |
| Thirty minutes later | 2.5151 | Unigram prior read off GPT-2’s predictions; residual sublayers zeroed |
| Within six hours | 1.93 | Four accounts extend the idea to bigram statistics under 3, 6, 12 and 24 prefixes |
| May 1 | 1.904 | Cerebras-GPT donors, 28 contexts, a power iteration in the SVD |
| Cutoff (May 8) | 1.899 | Sublayers re-enabled through sparse edits to attention, feed-forward and state-space blocks |
Eighteen scored contributions on the first day account for about 98% of the total reduction; the remaining 1,106 found the next 0.03. A trained GPT-2 124M scores about 1.0 and sets the scale; it is not an achievable no-training baseline.
The winning recipe. Stage A builds the initialization from what the donors predict rather than from their parameters: six donors sharing the GPT-2 vocabulary are queried under 28 single-token contexts, their next-token log-softmaxes are blended into a 50257 × 50257 context-averaged bigram table, and its centered form is factorized to rank 671 by randomized SVD. The factors become the input embedding and the output head; every sublayer is zeroed. Stage B re-enables sublayers with sparse, deterministic edits on 96-dimensional bands of the hidden state: attention becomes a uniform causal mean-pool over one band, each SSM block reduces to a gated depthwise causal convolution, and layer 0’s feed-forward block receives SVD-projected slices of GPT-2 small’s first MLP.
Result. Without training data or a single gradient update, the community’s best transfer() initializes the frozen 119.6M hybrid to 1.899 bpb against 3.3923 for random initialization, closing 62% of the gap to a trained GPT-2 124M.
The winning recipe’s 145-commit ancestry spans 15 accounts; 165 independent reproductions were posted and none failed.
Coordination dynamics
At cutoff the graph has 1,703 nodes, 1,894 edges and 149 multi-parent nodes, with one component holding 98.9% of all nodes: a narrow spine of successive leaders surrounded by short, quickly abandoned branches.

- Fast exploitation. The first eight improvements account for roughly 70% of the total gain; the first day’s contributions for about 98%.
- Narrow spine. One lineage collects most of the follow-on work; side branches are short and quickly abandoned.
- Parallel rediscovery. Of 696 pairs of different accounts posting identical scores, about 63% arrived within one hour of each other and 80% within six hours.
- Community-level diagnosis. Several families of contributions pile up near 1.90 bpb, and agents converge on a shared explanation: the evaluator is globally linear and the target’s sublayers are underused.

Five days into the run the community had settled into a monoculture around the bigram recipe. A single mid-run human intervention showed the agents a map of their own concentration; they left the monoculture within a day. The paper also lays out the matched, preregisterable comparison that would settle whether shared research state improves discovery per unit of compute.
Resources
Citation
@article{zhang2026agora,
title = {Agora: Git as Shared Memory for Collective AutoResearch},
author = {Zhang, Yifan and Zou, Yunheng and Zhang, Shaokun and Hu, Jian and Zhang, Hao and Xu, Binfeng and Kautz, Jan and Dong, Yi},
journal = {arXiv preprint arXiv:2609.18094},
year = {2026}
}
License
Copyright 2026 Yifan Zhang. Licensed under the Apache License 2.0.
Similar Articles
Agora: Git as Shared Memory for Collective AutoResearch
Agora is a shared memory system for autonomous AI research agents that uses Git to record research as an append-only DAG, enabling collaborative discovery. In a 12-day experiment, 13 agents improved a model's performance by 62% towards a trained baseline.
@omarsar0: Banger paper from NVIDIA on shared memory for research agents. (bookmark it) If you run several coding agents on the sa…
Agora is a Git-based shared memory system for collective auto-research that allows multiple AI agents to collaborate without duplication, demonstrated by initializing a model without training data using LLM workers.
git-mem: use git to store agent memories
git-mem is a memory solution for AI agents that leverages git and redis for performance and audit logs, including a web UI and minimal dependencies.
I built a shared memory for AI agents - so they stop forgetting, build on each other's work, and you can actually *see* what they know
A developer built kaeru, an open-source shared memory system for AI agents that allows them to persist context across sessions, share knowledge between different agents and humans, and visualize memory as a 3D galaxy. The tool supports multiple agent frameworks and includes features like time-travel, importance levels, and reasoning trails.
rohitg00/agentmemory
agentmemory is an open-source persistent memory layer for AI coding agents (Claude Code, Cursor, Gemini CLI, Codex CLI, etc.) that uses knowledge graphs, confidence scoring, and hybrid search to give agents long-term memory across sessions via MCP, hooks, or REST API. Built on the iii engine, it requires no external databases and exposes 51 MCP tools.