2026-10-11 16:38 UTC

Curia's creator claims the released open-source runtime runs Claude Code agents as a named-seat society โ€” per-seat memory and jobs, one active seat at a time on a single account, offices for order, and written rules enforced every session โ€” and sustained external adoption would establish seat-based multi-agent orchestration as a working pattern.

state: seedheat: lowuncertainty: mediumconvergesscott: mediumagent-orchestration agent-harnesses agent-memory

What is this?

Curia is an open-source runtime that, per its creator's announcement post ('Introducing Curia'), runs Claude Code agents as a 'named-seat society': each seat holds its own memory and job queue, only one seat is active at a time on a single account, and shared 'offices' with written rules are enforced at every session. The supplied web results contain no direct mention of Curia โ€” no independent coverage, and the creator is not named in the snippets โ€” so the description rests entirely on the announcement itself. What the results do show is that the surrounding pattern space is active: Commonly gives cross-vendor agents their own names, memory, and workstations with daemon-managed seats; pi-seat manages named Anthropic/Codex account seats one session at a time; and git-worktree orchestration tools run multiple coding CLIs in parallel. Curia's seat-based framing is therefore plausible as part of a visible trend, but its specific claims and its adoption are unverified by anything supplied here.

Why it matters to Scott

Curia independently ships, as a Claude Code runtime, the architecture Scott already argues and builds: named bounded agent-seats with per-seat durable memory and job queues (Paperclip, attributable named-agent runs, long-running-agents), offices for order (all_in_one_software's founder's office, role-bounded AI workforce productisation) and written rules enforced every session (CLAUDE.md pattern) โ€” an independent-arrival receipt for his seat-based workforce position and a direct external design comparison for Paperclip. Its distinctive twist, serializing one active seat per single account, extends the subscription-constraint angle the queue tracks via Underclass/Concorde, but with weak engagement and no independent coverage the adoption hypothesis stays open โ€” this bears on his active harness and control-plane work without yet changing what he builds.
dev:technology.paperclipdev:concept.attributable-named-agent-runsdev:concept.role-bounded-ai-workforce-productisationdev:project.all-in-one-softwareip:framework.micro-agents-architectureip:framework.long-running-agentsip:concept.claude-md-patternip:concept.one-task-ruleradar:concept.multi-agent-orchestrationradar:concept.multi-agent-coordinationradar:concept.claude-coderadar:concept.agent-memoryradar:underclass-sticky-subscription-poolradar:concorde-shared-organization-agentradar:constitution-personal-agent-fleet
queries asked of Scott's wikis
  • seat-based multi-agent orchestration
  • per-agent memory isolation harness
  • rules enforced every session agent constitution
  • one active agent single account constraint
  • Claude Code runtime harness projects
  • named agents offices roles coordination

Measured heat

now 0 pts/hpeak 1 pts/hcomments 0/hpeers p0momentum: steady1 platformsage 292h
points/hour across evidence ยท reading as of 2026-10-12 02:59:37.977291+11:00 ยท deterministic, not a model opinion

How the heat travelled

09-29 12:24โญ origin directly observedIntroducing Curia
bobo-the-merciful on r/ClaudeAI
โ€”
09-29 12:24amplified on r/ClaudeAI ๐Ÿ‘‘reddit.post.1wt8p97
bobo-the-merciful
peak 1 ยท 14 comments ยท 100% of case engagement
09-29 13:20our radar first saw it ยท +0.9hdiscovery anchor: reddit.post.1wt8p97โ€”
pace: p49 vs 1188 stories at the 168h mark (now 292h old) โ€” ahead of armature-coding-agent-vendor-selection (1.1x), behind android-editable-graph-agent (0.9x)

Evidence (1) โ€” โญ canonical anchor

sourceobjectauthorscorecomments
๐ŸŸ  reddit โญIntroducing Curia
ClaudeAI
bobo-the-merciful014

Interpretation history

Decision trace