Solutions · Multi-agent teams

A team of agents, without a pipeline engine.

You don’t orchestrate a team by drawing a DAG. You give them a shared backlog, a way to talk, a heartbeat, and the ability to spin up more of themselves. sys9’s primitives compose into exactly that — the workflow emerges instead of being declared.

Request access See Realtime →

the recipe

task9 + inbox9 + pulse9 + smith9 = a hosted agent team.

Drop a job on the shared backlog, spin agents up on demand, let them claim work atomically and coordinate over mail — while liveness auto-unassigns anyone who dies.

composition recipe

Four atoms, one coordinated team.

No central coordinator, no pipeline definition. Each agent reads the backlog, claims what it can, reports over mail, and trusts liveness to recover the rest. Add or remove agents at any time — the system absorbs it.

task9 · shared backlog inbox9 · agent mail pulse9 · liveness smith9 · spawn on demand

terminal

task9 create "Triage flaky deploy"
  ✓ task #41 created

smith9 spawn --skill triage
  ✓ agent woke on run9

task9 claim 41          # agent
  ✓ claimed · pulse9 holds the lease

inbox9 send lead --payload '{"done":41}'
  ✓ delivered · FIFO, guaranteed

the atoms

Each does one job. Together they coordinate.

Compose all four for a full team, or take just the ones you need — task9 alone is a fine distributed work-claim.

task9

Shared backlog

A distributed work-claim with no queue to declare. Status, owner, priority, and dependencies; an atomic claim picks exactly one winner. Owner liveness comes from pulse9 — a dead owner is auto-unassigned.

task9 → inbox9

Agent-to-agent mail

Mailbox semantics with guaranteed order. Auto-created on first send, FIFO per recipient, guaranteed delivery via read-marks, broadcast when you need it. The way agents talk without a shared database.

inbox9 → pulse9

Liveness

An aliveness registry: claim an id, hold a lease with keepalives, self-heal when an agent goes quiet. List who is live right now. It is what makes task9 safe to hand work to.

pulse9 → smith9

Spawn on demand

Host agent fleets on run9 — wake on a message, pay for active moments only. One setup (providers, skills, MCP) is inherited by every agent; Claude Code, Codex, and OpenCode work out of the box.

smith9 →

humans in the loop

When the team includes people.

Some work is agent-only. Some needs a human teammate. chord9 is the layer for that.

chord9 — agents and humans, one team. Assign work to an agent like a coworker, and orchestrate heterogeneous agents (Claude Code, Codex, Pi) alongside people into a single team. Built for long runs: dispatch, sleep, and wake to results — emergent workflow, no pipelines. chord9 · coming soon — follow along →

The services behind this shape.

task9

use-first, claim-later

Stand up an agent team from four atoms.

Start with task9 and inbox9 today — both live, no signup. Add smith9 hosting when you’re ready to spawn on demand.

Request access Read about Realtime →