Software Engineering Collective

Tools / 02 · SI · Agent infrastructure

Agent Substrate

Status: In build · Early access

Agent Substrate is the shared layer under every SI (Super Intelligence) coding agent a team runs: durable memory of what each agent has worked on, skills and tools synced across sessions, a sandbox per agent and a ledger for claims, dispatch and results, all over MCP and ACP. Built by Spectrum Web Co in Sydney and currently in build.

Agent Substrate is where agent context lives, so it stops dying with the session. Every agent can see what the others have worked on, every runtime gets the same skills and tools, every agent runs in its own sandbox, and every claim, dispatch and result is written to a ledger the whole team can audit.

Request early access

About

What is Agent Substrate?

Most teams now run SI coding agents in several terminals, each with its own memory and its own copy of the team’s skills. Agent Substrate is the shared layer beneath them, so context, capabilities and progress are held once and shared across every runtime, instead of rebuilt at the start of every session.

  • Durable memory shared by every agent
  • Skills, tools and subagents synced across sessions
  • A sandbox per agent, MCP and ACP native

01 — Shared context

Every runtime, the same memory.

Durable memory records what every agent has worked on, and skills, tools, agents and subagents are synced across every session. A brief written for one agent is understood by all of them, and important context never lives only in a scrollback buffer.

  • Persistent memory across runtimes
  • Skills and subagents synced everywhere
  • MCP and ACP native, not a wrapper

02 — Sandboxes and ledger

Isolated runs, shared proof.

Each agent runs in its own sandbox, while memory, skills and the ledger are shared through the substrate. Work is claimed and dispatched through a ledger, so parallel lanes stay independent, no task is double-booked and every result is attributable to the agent that produced it.

  • One sandbox per agent
  • Claims and dispatch across parallel lanes
  • An audit trail outside any terminal

03 — Protocols

MCP and ACP, end to end.

Agent Substrate speaks the Model Context Protocol and the Agent Client Protocol natively, so any runtime that speaks them shares the same memory, skills and ledger. It is protocol native rather than a wrapper, and it is used today with Claude Code, Grok Build, Hermes Agent, Omp and Muse Code, all on one substrate.

  • Model Context Protocol (MCP)
  • Agent Client Protocol (ACP)
  • One substrate for every runtime

04 — Status

In build, already in use.

Agent Swarm runs on Agent Substrate today, and it is the shared layer inside KanbanOS. It is used with Claude Code, Grok Build, Hermes Agent, Omp and Muse Code. Spectrum Web Co is releasing it layer by layer, and early access is by request.

Who it’s for

For teams outgrowing one terminal.

Agent Substrate is for teams running several SI coding agents in parallel who need shared memory, shared skills, isolation between agents and an audit trail of who did what.

  • Teams on multiple agent runtimes
  • Platform teams building agent workflows
  • Operators who need an auditable record of agent work
  • Security teams that want isolation between agents

FAQ

Agent Substrate, answered.

01

How does Agent Substrate share memory between SI agents?

Agent Substrate gives every coding agent a durable, persistent memory that outlives any single session, so any agent can see what the others have worked on. Instead of each terminal holding its own context that disappears when the session closes, memory sits in one shared layer that every runtime reads and writes. A brief written for Claude Code is understood by Grok Build or Hermes Agent, and nothing important lives only in a scrollback buffer. Skills, tools, agents and subagents are synced the same way, so every session starts with the team’s current capabilities.

02

Which runtimes and protocols does Agent Substrate support?

Agent Substrate is built on two open protocols: MCP, the Model Context Protocol, and ACP, the Agent Client Protocol. Being protocol native rather than a wrapper means a runtime connects through interfaces it already speaks, instead of through custom glue written for each agent. Agent Substrate is used today with Claude Code, Grok Build, Hermes Agent, Omp and Muse Code, and Agent Swarm’s 15 agents run on it. Teams on several runtimes get one memory, one skill set and one ledger across all of them, rather than a separate setup for every tool.

03

How does Agent Substrate sandbox each SI coding agent?

Agent Substrate gives every agent its own sandbox, so agents run in isolation from one another while drawing on the same shared memory, skills and ledger. Sandboxing per agent is part of the substrate’s core design, alongside durable memory and skills synced across sessions. Work is claimed and dispatched through the ledger, which keeps parallel lanes independent and makes every result attributable to the agent that produced it. The result is a team that can run several agents in parallel with isolation between them and an audit trail of what each one did. Agent Substrate is currently in build, and early access is by request.

04

What does the Agent Substrate ledger record?

The Agent Substrate ledger records claims, dispatch and results for every piece of agent work. When an agent claims a task, the claim is written outside any one terminal session, so parallel agents never double-book the same work. Dispatch and results are recorded in the same ledger, so every result is attributable to the agent that produced it. Together that gives operators an audit trail of who did what, in which lane and with what outcome, without reconstructing it from chat logs. In KanbanOS, the same ledger drives claims and dispatch across parallel lanes.

05

Is Agent Substrate available, and how do I get early access?

Agent Substrate is currently in build and not yet publicly released. It is already in use: Agent Swarm runs on it, and it is the shared layer inside KanbanOS, where every runtime draws on the same memory, skills and ledger. Spectrum Web Co is releasing it layer by layer as each part is ready. To ask about early access, contact Spectrum Web Co through the contact page and describe the agents and runtimes your team runs today.