octomux
Assemble your own
AI dev stack.
octomux is the layer that holds it together. Every part of it is yours to pick.
- which agentone harness, or five at once
- how it runsa session you drive, or one that drives itself
- what it doesany task you can describe
- how you watchany screen — or one you build
What you can do
Four jobs.
Four different shapes.
A schedule starts the work while you are asleep.
swap for · a ticket landing · a failing build · you, right now
How it works
Six layers.
You choose five.
The dark layer is the only one we hold. It keeps the queue, gives every run its own git worktree, records what happened, and refuses to merge until you say so — identically, whatever you put in the other five. What is and is not swappable →
a dashed chip is on the roadmap, not shipped. Solid works today.
Documentation
Every detail, one level down.
This page is the shape of it. The docs are how it works.
Questions
The awkward ones first.
Do plugins run sandboxed?
Not by default. They run in-process with full Node privileges — install them like any dependency that runs on your machine. Registrations are namespaced so nothing can overwrite a built-in, and dangerous verbs must be declared in the manifest and approved at install.
What happens to running agents when I reload a plugin?
Nothing. Agents are their own processes; the runtime only supervises them. Unmount and remount takes about a second, and tasks in flight don't notice.
Is there a cloud?
No. It runs on a machine you own and drives the subscriptions you already pay for. No sync, no telemetry. For phone access, put the host on a tailnet.
Bring your own agent.
Two commands to run it. One file to extend it.