06-reference

every 100 agent software factory

2026-05-19·reference·source: Every·by Katie Parrott

Inside the 100-agent Software Factory — Every (Context Window)

Why this is in the vault

Third same-shape signal in 24 hours pointing at parallel-narrow-scope multi-agent as the operational pattern (after [[2026-05-19-cloudflare-cyber-frontier-models]] Glasswing 50-concurrent-agent harness and [[2026-05-19-alex-vacca-3-phases-ai-layer-services-as-software]] spine-agents-loop). Every — a technically-fluent publication with a paying-prosumer audience — is now centering "100 agents merging 50 PRs/day" as the reference frame, not 1-shot generic agents. This corroborates the harness-thesis cluster ([[2026-05-18-agentway-harness-engineering-claude-code-design-guide]]) directly: the operational unit is the orchestration system, not the model. Also a fresh receipt on the HTML-as-agent-output substrate shift first filed at [[2026-05-08-thariq-unreasonable-effectiveness-html]].

⚠️ Sponsorship

Issue carries a paid placement for HighLevel (CRM / lead-routing platform, gohighlevel.com) positioned between the Gas City summary and the "Sells and Knutsen use Gas City to build Gas City" section. Standard "Want to sponsor Every? Click here" tag. Sponsor is unrelated to editorial — does NOT bias the multi-agent argument — but flagging per protocol.

The core argument

Three converging frames, each reinforcing the harness-over-model thesis:

  1. Gas City as the reference 100-agent system. Steve Yegge's "Gas Town" (20-30 agent coordination) was rebuilt by Chris Sells (ex-Google Flutter) and Julian Knutsen (ex-Block) as Gas City — Knutsen's Atlanta server runs ~100 agents merging ~50 PRs/day, burning ~1B tokens/day (roughly 1/5 the English Wikipedia corpus). The toolkit is not production-ready (took experienced engineers a full day to stand up) but the three load-bearing ideas inside are worth internalizing:
    • Dark factory vs light factory. Human-visible work (planning, design, review) is "light"; agent-grinding on well-defined tasks is "dark." Trust shifts work from light to dark over time.
    • One pet, many cattle. A single persistent named supervisor ("the mayor") that the human talks to, dispatching to anonymous disposable workers ("polecats") that do one job and shut down. You manage one conversation, not 100 agents.
    • Multiple opinions on every code review. Same code to Claude + Codex + Kimi in parallel. Three different models catch different bugs than one model run three times.
  2. Verdict from Mike Taylor (Every's head of tech consulting): 🟨 "Learn from the ideas. Skip the toolkit for now." Already-shipping alternative: OpenAI's Symphony (released a few weeks ago) — a written ruleset that turns your existing Linear board into the agent dashboard. Lower behavior-change cost.
  3. HTML displaces Markdown as the default agent-output format. Thariq Shihipar's "Unreasonable Effectiveness of HTML" post (May 8) hit 4.4M views in 16 hours; Karpathy backed it 3 days later; Simon Willison (long-time Markdown advocate) flipped. Rule of thumb from the issue: Markdown if it's for humans, HTML if it's for agents. Wrinkle: Slack/Google Docs/GitHub diffs were built for Markdown — tooling has to catch up.

Issue contents

Mapping against Ray Data Co

Direct hits:

Calibration:

Related