Reference

FAQ

My agent vendor already ships scheduling and worktrees. Why add this?

If you only ever run one vendor’s agent, don’t — theirs is good and it is included. octomux earns its place the moment there are two, because no vendor’s control plane will drive a competitor’s agent, or let you register a third. The same goes for your tracker, your sandbox and your channels.

What is a metaharness?

A harness is the wrapper that runs a coding agent — it launches the model, feeds it context, captures output and cleans up. A metaharness sits one layer above and coordinates harnesses rather than replacing them. octomux has no agent loop of its own.

What does it cost to run?

Nothing beyond what you already pay. octomux is MIT and adds no inference cost of its own — it drives the agent subscription you have.

What if two agents need the same file?

They cannot collide. Each task runs in its own git worktree on its own branch, so several agents can edit the same file at once and your working tree never moves.

Does an agent post to GitHub without me?

No. Review comments are drafted locally against the real diff and sit there until you accept them. When you do, they publish as one batched review.

Does my code leave my machine?

No. Everything runs locally. No cloud sync, no telemetry.

Does it run on Linux?

Yes — the CLI runs on macOS and Linux. There is also a macOS desktop app if you would rather not keep a terminal open.

What if my laptop reboots?

Run octomux start. Tasks, branches, terminals and review progress all come back. For scheduled work to survive a closed lid, host it on a machine that stays up.

Are plugins sandboxed?

No. They run in-process with full Node privileges. Namespacing stops plugins overwriting each other or a built-in, but that is collision safety, not a security boundary. Read the source of anything you install.