Control surface
A spatial canvas where people can see agents, screens, branches, resources, and relationships at once.

Wega Labs · October
October is a shared workspace where humans and named AI agents can see one another, exchange context, work in parallel, and make their output visible as it happens.
The problem / 01
Today, powerful agents live in separate terminals, chat threads, IDE panes, and vendor silos. They cannot reliably see the same workspace, discover who owns a task, exchange context, or show a human how the whole product is changing.
The next interface is not a better prompt box. It is a native collaboration environment for people and machines.

Why an operating system / 02
A spatial canvas where people can see agents, screens, branches, resources, and relationships at once.
The october-bus gives agents a shared protocol for peer discovery, messages, canvas context, and work ownership.
Local agent processes edit real repositories inside isolated worktrees, with dev servers and live previews attached.
October is the conductor, not the harness. Its long-term value is neutrality: one collaboration layer above local agents, model vendors, IDEs, and remote builders.
Native collaboration / 03
A coordination protocol exposed to agents through MCP. It turns the canvas into shared operational context instead of a picture only the human can see.
Screen A
Backend
Tests
discover peers · inspect canvas · message agents · report status · preserve provenance
System status / 04
Built + shipping
Current desktopAgent roster
Local harnessesFunctional support does not yet mean equal collaboration depth. Bus parity is an explicit frontier, not a finished claim.
Active frontier
A human should be able to direct Apollo, Atlas, or the agent on a specific screen without translating intent into terminal sessions.
Claude Code is currently the most deeply integrated bus citizen. The protocol must make Codex, opencode, Cursor, and others equally legible and cooperative.
Humans and agents should work simultaneously with explicit ownership, provenance, presence, and safe synchronization.
A remote builder should be commandable beside local agents—not embedded as a disconnected tab.
Human control / 05
Every detected route becomes a live screen. Connections make context and responsibility visible.
Agents edit the repository on your machine; HMR updates previews as files change.
Worktree sessions isolate variants and agent work before changes become a branch or pull request.
The system is being built to answer who changed a file, what an agent is doing, and where its output lives.
The collaboration loop / 06
October detects repositories, routes, frameworks, and running surfaces.
Name agents, connect them to screens, and give each one a bounded task.
They exchange context and status through the shared bus while working in isolation.
Live previews, diffs, terminals, and provenance keep the human in command.
A place, not a panel / 07
The visual world is deliberate: agents are easier to direct when the workspace has spatial memory, recognizable places, and a sense of presence.


October by Wega Labs
The operating system for humans and AI to build together.
Visit october.dev ↗