by Spectrum Web Co

Product · by Spectrum Web Co

An operating system, not another chat window.

KanbanOS is an agentic software-delivery platform built by Spectrum Web Co in Sydney. It plans work before AI coding agents start, shares memory, skills and a ledger across every runtime, coordinates a 15-agent SDLC swarm with signed, fail-closed gates, and runs delivery on a Kanban board that agents move and humans govern.

KanbanOS is the operating layer between your ask and a mergeable pull request. It injects planning into the agents your team already runs, gives every runtime the same substrate, runs a governed SDLC swarm and keeps the work on a board humans control.

Get early accessRead on

What it is

What is KanbanOS?

Most teams now run coding agents in five different terminals. Plans die with the session, the board has no idea what an agent just claimed, and review is optional. KanbanOS applies operating-system ideas — isolation, shared services, verifiable state, clear ownership — to the agentic software development lifecycle.

  • Works with Claude Code, Grok Build, Hermes Agent, Muse Code and Omp — it never replaces your agents
  • One Graph ID per request, carried across the board, Linear and Notion
  • Signed, fail-closed gates at every handoff; humans keep the merge
  • Built and operated by Spectrum Web Co, a Software Engineering Collective in Sydney, Australia

01 — Plane 01 · Planning

Every ask becomes a brief.

Ultrathink is injected into the agents you already use. Each request is filtered, uplifted into an XML spec with a dependency graph, expanded into a graph of thought with parallel execution waves, and checked with human-in-the-loop questions before a line of code is written. Planning fails open, so it never blocks a run.

  • Filter → XML uplift → graph of thought → workflow waves → HITL
  • One Graph ID across every tracker
  • Never writes .planning/ into your working directory

02 — Plane 02 · Substrate

Every runtime, the same context.

Agent Substrate gives each runtime shared memory of what every agent has worked on, skills and tools synced across sessions, a sandbox per agent and a ledger that records claims, dispatch and results. It speaks MCP and ACP, so a brief written for one agent is understood by all of them.

  • Runtime · Memory · Skills · Sandbox · Ledger
  • Claims written outside any one terminal, so agents never double-book
  • Notion and Linear as sources of truth; lanes A / B / C for dispatch

03 — Plane 03 · Swarm

Autonomy with a ceiling.

Agent Swarm coordinates fifteen specialised agents, A01–A15, across the whole lifecycle: requirements, design, backend, frontend, data, QA, review, security, DevOps, release, observability, maintenance and documentation. An orchestrator delegates, every artifact has a single writer, and quality gates fail closed.

  • Signed verdicts in the swarm.v1 message protocol
  • Parallel worktrees without parallel noise
  • Stalled work escalates to a human, never to a guess

04 — Plane 04 · Board

Kanban as the operator surface.

The board is where people and agents meet. Agents claim and move cards through dependency chains, hooks and linked worktrees; operators see work, owners and progress without reconstructing it from chat logs. The ship loop opens a pull request and drives review until it passes — and a human approves the merge.

  • Agents claim and move cards
  • Parallel cards, worktrees, hooks and dependency chains
  • Humans approve merges, releases and anything irreversible

Who it serves

For teams whose developers now include agents.

KanbanOS is for product and engineering teams that run AI coding agents and need plans, shared context and gated delivery on one board they control.

  • Platform teams that own the substrate their agents run on
  • Product and engineering leads turning intent into visible, gated delivery
  • Security and quality teams that want verification inside the loop
  • Agencies and studios orchestrating many clients

FAQ

Product questions.

How KanbanOS fits next to the tools your team already has.

01

Is KanbanOS a replacement for my coding agents?

No. KanbanOS is the layer around the AI coding agents your team already runs, including Claude Code, Grok Build, Hermes Agent, Muse Code and Omp. Ultrathink is injected into each agent as a planning plugin, Agent Substrate gives every runtime the same memory, skills and ledger, and Agent Swarm runs those agents as specialists inside a governed lifecycle. You keep your agents, your prompts and your accounts; KanbanOS adds planning, shared context, gates and a board on top of them.

02

What does 'fail open' planning and 'fail closed' swarm mean?

Planning fails open: if Ultrathink cannot produce a brief for any reason, the agent carries on with the original prompt, so planning never blocks a run. The swarm fails closed: every handoff between the fifteen agents is a signed verdict, and when a verdict is missing or uncertain the work stops and escalates to a human rather than guessing. The two defaults are deliberate — planning is cheap to skip and expensive to block, while unverified delivery is expensive to let through.

03

Does KanbanOS store my code or run in my infrastructure?

KanbanOS is built to run next to your existing repositories and runtimes. Agents work in parallel git worktrees in your own environment, the Agent Substrate ledger records claims and results for those agents, and the ship loop opens pull requests in your repositories. Spectrum Web Co is releasing each layer as it is ready, with the swarm and planning plugin already open source under github.com/swcstudiospace; the hosting model for the operator board is being finalised with early-access teams.

04

Is KanbanOS open source?

Two of the four components underneath KanbanOS are open source today: Ultrathink, published as claude-ultrathink, and Agent Swarm, both under github.com/swcstudiospace. Agent Substrate is in build and in use inside KanbanOS, and the KanbanOS product itself is licensed AGPL-3.0 by Spectrum Web Co. Early-access teams work directly with the makers as each plane comes online.

Early access

Put your agents on an operating system.

Early access is open. Teams join as each plane comes online, with onboarding from Spectrum Web Co in Sydney.

Talk to Spectrum Web Co