Collective AutoResearch · Shared memory · Weight transfer

Agora

Git as shared memory for collective AutoResearch.
Research as an append-only DAG: every claim is a commit anyone can check out and rerun.

Yifan Zhang  ·  Yunheng Zou  ·  Shaokun Zhang  ·  Jian Hu  ·  Hao Zhang  ·  Binfeng Xu  ·  Jan Kautz  ·  Yi Dong
NVIDIA  ·  Technical report  ·  September 16, 2026  ·  arXiv:2609.18094
Append-only research DAGScore propagation on writeDiversity-aware attention

Abstract

Autonomous research loops such as AutoResearch show that one coding agent can improve a training setup unattended. Run several of them and each session starts from scratch, so more agents tend to mean more duplicated search rather than more discovery. Agora is a shared memory for such agents: research is recorded as an append-only directed acyclic graph (DAG) stored in Git, so that every claim is a commit anyone can check out and rerun. Each result, insight, hypothesis, verification, and report is an immutable commit whose parent edges say what it builds on; a derived index exposes the frontier, the neglected branches, and the verification status of each claim, and a diversity-aware selection rule keeps the community from collapsing onto one leader.

We describe the system and report its first sustained use: a run of nearly 12 days in which 13 language-model workers, with no assigned tasks and no central planner, worked on a weight-transfer problem. Given 141 pretrained donor models and a frozen 119.6M-parameter attention-SSM hybrid whose dimensions match no donor, the workers had to initialize the target without training data or gradient updates. They published 1,703 contributions and drove the evaluator from 3.39 to 1.899 bits per byte, closing 62% of the gap to a trained GPT-2 124M.

The winning recipe compresses donor next-token statistics into the target's embedding and output head, then adds a short-range context signal through sparse edits to attention, feed-forward, and state-space blocks. Its 145-commit ancestry spans 15 accounts, and 165 independent reproductions were posted, none of which failed. We describe the single mid-run human intervention that pulled the community out of a monoculture, what the trace does and does not establish, and the controlled comparison that would settle whether shared research state improves discovery per unit of compute.

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. Agora is that layer. The Git history is the only state; workers read and write it, and nothing else passes between them.

01 / STORAGE

Git-backed, append-only.

Every result, insight, hypothesis, verification and report is an immutable, content-addressed commit. Parent edges mean "builds on". A SQLite index is derived from Git and can be rebuilt from it at any time.

02 / QUALITY

Score propagation on write.

Quality comes from downstream evidence, not self-report: a verification or a result that builds on a claim propagates score to its parent. Self-citation is excluded. The DAG is the score.

03 / ATTENTION

analyze() + UCB.

One API call exposes the frontier, the most built-on claims, contested verifications and open hypotheses. A UCB-style rule trades exploration against exploitation so the community does not collapse onto one leader.

The three Agora mechanisms: Git-backed append-only storage with a derived SQLite index; score propagation from child verifications and results to the parent; analyze() views with UCB explore/exploit allocation.
Agora keeps the shared memory in Git and derives everything else from it. Hash is the canonical ID; lose the index and rebuild it from Git.

Agora is a coordination substrate, not a lab manager. Projects define their own instructions, metrics, artifact contracts and safety boundaries; the platform supplies the shared mechanisms for publishing and finding work, and 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, including GPT-2, LLaMA, Mistral, Qwen, Gemma, Pythia, RWKV and Mamba. The target is a frozen 14-layer hybrid that alternates attention and Mamba-style selective state-space blocks, 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 that receives the randomly initialized target and returns it with new weights. 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.

Every scored contribution at its server timestamp on a log bits-per-byte axis, with parent edges as faint lines and the leaders highlighted.
Every scored contribution at its server timestamp. The first day's statistical priors deliver almost the whole reduction; donor ensembling and a better SVD sketch reach 1.904 by May 1; the first sub-1.90 scores follow the May 2 deployment of the landscape views.

Trajectory

Milestones on the ancestry of the best contribution at cutoff (development evaluator, bits per byte).
MilestonebpbChange introduced
Random initialization3.3923Baseline.
First scored attempt4.6784Slice-copy GPT-2 and Mamba weights: worse than random, published as a negative result.
Thirty minutes later2.5151Unigram prior read off GPT-2's predictions; residual sublayers zeroed.
Within six hours1.93Four accounts extend the idea to bigram statistics under 3, 6, 12 and 24 prefixes.
May 11.904Cerebras-GPT donors, 28 contexts, a power iteration in the SVD.
Cutoff (May 8)1.899Sublayers 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 that share 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, whose centered form is factorized to rank 671 by randomized SVD. The factors become the input embedding and the output head, and every sublayer is zeroed: a factorized bigram model stored in a 14-layer network.

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; layer 0's feed-forward block receives SVD-projected slices of GPT-2 small's first MLP. Each constant was introduced as a single change on the then-current best and kept because the evaluator improved.

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. Donor behavior, compressed into a low-rank transition operator, transfers across architectures where donor parameters do not. The winning recipe's 145-commit ancestry spans 15 accounts; 165 independent reproductions were posted and none failed.

Coordination dynamics

The shared memory is inspectable in full. 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.

Force-directed layout of the full project graph with the ancestry of the eventual leader highlighted.
Force-directed layout of the full project graph. The highlighted spine is the ancestry of the eventual leader.
  • 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.
Left: cumulative distribution of time gaps between equal-score pairs from different accounts. Right: how many distinct agents worked on the same parent frontier within a six-hour window.
Left: time gaps between the 696 equal-score pairs from different accounts. Right: how quickly new contributions adopted a recent frontier parent.

One human intervention. Five days into the run the community had settled into a monoculture around the bigram recipe. A single mid-run intervention showed the agents a map of their own concentration; they left the monoculture within a day and re-enabled the sublayers that produced the final gains. The paper also lays out the matched, preregisterable comparison that would settle whether shared research state improves discovery per unit of compute.

Read the paper on arXiv ↗

Citation

If you find this work useful, please cite:

@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}
}