10,000 Agents
Later.

Orchestration that works.
Chris McDermut
Boulder Startup Week • May 6, 2026 • Boulder Public Library
Hook

The model is
the least important
part of orchestration.

You and I have the same Claude. The harness around it is the moat.
HARNESS Tools Context Sandbox environment Prompts Orchestrator Model commodity
By the numbers

What I've actually run.

1,226
PRs since Dec 1
156
days
~7.9
PRs / day
GitHub contribution graph: 3,573 contributions in the last year
The HQ pattern

The HQ pattern.

One directory. Source of everything. Workspace, staff, tickets, context. All in one place.
An agent is only as good as the context you point it at.
HQ workspace repos/ agents/ pmo/ CLAUDE.md .proletariat/ tickets
HQ pattern · Demo
DEMO

01

Walk the HQ.
Hot take

Tight specs.
Tickets, not markdown.

A spec that fits in a ticket lands in one PR. A spec that doesn't, doesn't.
Everyone wants you to write specs in markdown files. Put them in your project management system instead. Assignable, trackable, subscribable. Markdown isn't.
spec.md not assignable PRLT-128 Tight spec @alice · due Fri labels: orch, mvp PR #1227 merged ✓
Integration

Connect the tools
you already use.

Linear. Jira. GitHub. Notion. Slack. The MCPs and APIs your team already uses are part of the agent's workspace.
Stop writing prompts. Write tickets.
Agent via MCP Linear GitHub Notion Slack Jira …more
Integration · Demo
DEMO

02

Linear ticket → PR.
Scale

Run them
in parallel.

One repo. Many worktrees. Many PRs in flight at once. Each agent in its own sandbox.
Container per agent. Worktree per task. CI on every PR. Default deny on everything else. It's just good engineering. Pays off 10x once you scale.
main repo worktree-a agent · sandbox worktree-b agent · sandbox worktree-c agent · sandbox worktree-d agent · sandbox PR PR PR PR
Mental model

The orchestrator
pattern.

The orchestrator never implements. Implementation belongs to the staff.
1. Plan what needs to happen? 2. Investigate gather info 3. Delegate to staff 4. Review what came back?
Scale · Demo
DEMO

03

Meet the staff.
Watch them ship.
What breaks

The gotchas.

!
Anywhere

Work from
anywhere.

Remote dev servers. Dedicated agent machines. Your laptop sleeps. They don't.
Once the agents are remote, you don't need to be at a desk.
Cloud agents always on laptop phone $ ssh running. PR open. watch
Anywhere · Demo
DEMO

04

From your phone.
Beyond code

This isn't
just for code.

Research. Content. Data pipelines. Operations. Same orchestration patterns, different work.
{ } Code PRs · refactors 🔍 Research surveys · synthesis ✎ Content drafts · briefs ⚙ Ops data · pipelines
Stay in touch

10,000 Agents Later.

Build the orchestrator. Sandbox the staff. Ship in parallel.
GitHub repo
Star on GitHub
Install CLI
Install the CLI
npm i -g @proletariat/cli
Chris McDermut • chrismcdermut@gmail.com
@chrismcdermut on X • linkedin.com/in/chrismcdermut
proletariat.ai • orchestration that works