Let your agents run it.
Muxlio is a durable workflow coordinator for multi-step work across AI agents and shell tools. Your assistant authors an immutable plan; the coordinator runs it as a durable run you can follow in the bundled UI or through MCP after setup.
Claude · Codex · Cursor · Kiro · Antigravity (authoring) · command-line tools
For each feature: implement → review → test → fix if needed → commit after checks pass.
Implement Make the change and record the workAGENT
Review Inspect the change and address issuesAGENT
Verify & repair Run checks; fix failures and try againCHECKS
Commit locally You review the commit and choose when to pushYOURS
Plans, runs, and workers #
Use Muxlio when work needs dependent steps, verification, retries, or hand-offs—not for one-off answers in the client. You or your assistant authors a workflow; Muxlio compiles it to an immutable plan and executes a run on the coordinator. Steps run on workers through adapters (agent CLIs, remote A2A, command, and others).
Plan Validated Plan IR JSON with a content digest. A run always executes the exact bytes that were submitted.
Run One execution of a plan with your inputs—state, attempts, logs, and artifacts persist until completion or .
Workflow / recipe Authored logic in TypeScript, JSON, or a catalog template. Recipes in the repository are worked examples you can adapt.
Coordinator Go service that schedules steps, stores SQLite state, and exposes the HTTP API plus bundled UI (default port 7600). Streamable HTTP MCP listens separately when configured (default 7602).
Worker Process that claims steps and runs adapters in an authorized workspace (local machine, remote host, or sandbox).
Adapter Executor implementation on a worker—native agent CLIs, ACP, A2A, shell
command, and custom binaries.
Setup ports and MCP clients: Setup defaults. Architecture: overview and how it works.
How I use Muxlio to implement features #
I use this recipe to develop Muxlio itself. The workflow handles one feature at a time and runs the repository’s build and tests before creating a local commit.
Build the workflow with your assistant
Describe the steps and checks you want. Your assistant authors and validates a workflow, then starts a run with your inputs. Check the plan before starting the run.
Implement, review, test, fix
An agent implements the feature. A review step inspects and improves the change. Build and test commands run. If a check fails, an agent gets the failure report, fixes it, and the checks run again.
Review the result
After checks pass, the recipe creates a local commit and moves to the next feature. Inspect the diff, review notes, test output, and run history. You decide whether to push.
I run feature work overnight. #
I run Muxlio on a Mac mini and start workflows through my assistant. In the morning, I check the commits and reports. If a run stopped, I read the error and decide what to do next. The chat can be closed while it runs.
You choose where it runs: your workstation, another computer, or a server. Keep the execution machine running and use the UI or your assistant to check progress.
See what happened Live logs, review notes, check results, and attempts
See what needs attention A failed or d run keeps its progress and reason
Review before pushing The recipe creates local commits; you choose when to push
Install Muxlio, then start the service. #
Use Homebrew on macOS or Linux. It installs the CLI, adapters, UI, and MCP server without a manual checkout.
brew tap Muxlio/muxlio https://github.com/Muxlio/muxlio
brew install --HEAD Muxlio/muxlio/muxlio
muxlio version
Then, from the workspace you want to use:
muxlio init --client kiro --scope project
muxlio service start
init prepares workspace configuration, credentials, and agent instructions;
service start runs the coordinator and worker. Default ports and MCP client
rules match Start Muxlio → Setup defaults.
Verify stdio MCP with the MCP guide when appropriate, then ask your assistant to build a workflow for your task, validate it, and show you the plan before running it. You do not need Muxlio's source repository to use the installed service. The worker needs the files and tools your workflow uses.
For the feature example, the workflow and its verification commands are in the
implement-features recipe.
Use it as a starting point and adapt the steps, agents, and checks to your work.
The Docker Sandbox walkthrough shows two dependent features
running against one branch in a private clone with Claude Code, Codex, Cursor,
and command execution available on the sbx worker. Select localhost for the
host checkout or sandbox for the Docker checkout.
Follow a run at http://127.0.0.1:7600/ or ask your assistant for its status.
Guides and reference #
Build your own workflows with the CLI and SDK reference ↗