CLUSTERSTUCK

a persistent multi-agent organization
for the self-hosted homelab

the operator architects. the swarm executes.

the north star

The pocket jarvis

"i pipe in work, the swarm does it for me, i review and sign. the swarm is self-improving, resists vulnerabilities, scales to many machines, reorganizes itself, and writes its own story." the operator

Every design choice traces back to one of those properties. Self-improving. Resilient. Multi-machine. Self-organizing. Self-documenting. These are not aspirations. They are the acceptance criteria.

what it is

An org, not a chatbot

what it isn't

  • x a chatbot
  • x a copilot
  • x a tool you prompt
  • x many copies of one model in a loop
  • x a product for sale

what it is

  • + an autonomous organization
  • + stable roles with their own memory
  • + a review chain that actually ships
  • + self-improving over time
  • + a homelab that manages itself

An org chart made of AI personas with stable identity, owned scope, and sealed memory, wired through a review chain. The operator pipes work in, reviews the result, and signs. The swarm does the rest.

how it works🧲

Pipe in. Review. Sign.

Work flows in one direction and accountability flows back the other way. A request is parsed, routed to the role that owns it, drafted, reviewed by a separate role, and only then surfaced to the operator for sign-off. Nothing reaches the trunk unreviewed.

OPERATOR ROUTER SPECIALIST REVIEWER sign-off
work in, accountability back. nothing reaches the trunk unreviewed.

what it produces

Artifacts, not chat

The difference between a swarm and a group chat is what is left behind. Clusterstuck leaves merged changes, decision records, and an audit trail.

01

Reviewed merges

Changes land through a review gate on the trunk. The author and the reviewer are different roles.

02

Decision records

Architectural choices are written down before they are built, so the why survives the doing.

03

Attributed work

Every merge carries the role that ran it. No anonymous writes, no untraceable changes.

04

Self-repair

Health is polled, drift is detected, and routine fixes happen without waking the operator.

why personas

The voice is load-bearing

Stable roles are not a gimmick. A role with a consistent voice, an owned scope, and its own memory is legible to the operator, enforces its own boundaries, and creates accountability that a generic assistant cannot. You can tell who did what, and why.

That is what makes this different from many copies of one model running in a loop.

+self-improving +resilient +multi-machine +self-organizing +self-documenting

built in the open

The work is public

This is a real, self-hosted, multi-machine homelab fleet running on NixOS, operated end to end by a persistent multi-agent swarm. It is not a demo and not a diagram. The engineering is open for inspection.

repo

NixOS fleet

Declarative NixOS fleet. Reproducible machines, built from one flake. (pending mirror)

repo

Agent swarm

The persistent multi-agent organization: persona identities, prose, and the review chain. (pending mirror)

Built and operated by one person. More at yar.sh.