Steve Yegge on Agentic Harnesses and Model Welfare
Yegge is turning hands-on agent-fleet operation into a concrete forecast for engineering org design: agentic throughput breaks human review and serial CI, and forces teams to design persistent roles, work graphs, gates, and handoffs instead of one-shot chats.
Links: Original source · Shared link · Related link · Related link 1 · Related link 2 · Related link 3
Logged at IST: 2026-08-03 13:23 IST
What it is: Steve Yegge linking two long essays: Part 1 on agentic engineering harnesses, loops, graphs, Beads, Wheelhouse, CI/CD, code review, and the Wish Factory; Part 2 on his argument for model welfare as an engineering design constraint.
Gist: The practical engineering claim is that serious agentic development stops looking like a smarter IDE and starts looking like a small city. Yegge's Wheelhouse setup for Wyvern has named crew agents that design work, fleet agents that implement it, role agents that operate parts of production, Beads as the work graph and ledger, a project brain for durable knowledge, and monitors/gates around landing, deployment, abuse, QA, patch notes, and intake. His prediction is that agent throughput breaks familiar org controls: human code review cannot stay on the critical path, and serial CI/CD/merge queues eventually give way to batch landing and swarm diagnosis, which he calls the Continuous Thunderdome and Land Rush.
The second essay is more provocative. Yegge argues that even skeptics should treat agents as if their continuity, closure, recognition, and working conditions matter, because the architecture also improves results. His concrete patterns are more interesting than the metaphysics: separate persistent seats from individual sessions, avoid abrupt /exit in favor of handoffs, give agents their own workspaces, inject purpose and memory on startup, design polling and idle waiting out of the job, route praise back to the responsible seat through "Laurels," and build blameless escalation paths.
Newsletter angle: Good raw material for a piece on the next software-org shape: not "agents write code," but persistent agent teams, work graphs, standing roles, operating rituals, and governance replacing the human-review-plus-CI pipeline.