Your model, harnessed.

muxcode runs coding agents on the models you already sign in to, on your Mac or in a cloud sandbox.

Version 1.0.30 for Apple silicon · Windows coming soon

Built on pi, the open-source coding agent.

Get started

  1. Download muxcode and open it. It needs macOS 11 or later.
  2. Sign in to a model provider. Choose Sign in from the avatar menu.
  3. Attach a project folder. Use Attach repository in the prompt box.
  4. Type a task. Pick a model, then ask about the code.

Signing in to mux, the cloud service, is optional. It adds a shared workspace, code index, memory and cloud tasks, and your first sign-in starts a 72-hour Pro trial. On Pro, Pro+ and the trial, new tasks in a Git project run in the cloud until you turn off Sandbox by default in the Models settings. Read the guide

Screens from muxcode
Ask about the code.

One window shows the chat, the files the agent read and the commands it ran.

A plan before implementation.

The Architect plans the change, muxcode checks the plan, and a worker builds it.

Every seat, on the record.

The Agents pane lists each step with the tokens it used, and an open step shows its model and time. Below are the run's cost, its checks and how to revert.

Read the change before it lands.

Each changed file opens with new lines marked.

A small model reads along.

Clef picks each change's lane, flags risky commands on local tasks and says how each turn ended. It comes with Pro, Pro+ and the trial, or runs on your own Cloudflare token.

From an issue to a draft pull request.

Paste a GitHub issue. Cowork works it in a cloud session on its own branch: a test that fails on today's code, then the change that makes it pass. Nothing merges on its own.

A reviewer that reads the callers.

Reviewer, on Cowork's Code review tab, reviews the pull requests that touch the paths you name, with the callers and importers of the change from your code index. Its reviews are drafts until you turn posting on, and it never approves.

How the workflow makes a change

  1. promptYou
  2. planArchitect
  3. buildWorker
  4. checksYour project
  5. judgeA fresh read
  6. branchYou
muxcode retries a failed change once, with more thinking.

As shipped, the workflow's root is DeepSeek V4.1 Flash, which Pro and Pro+ include, your own plan in a team workspace, and a seat you have not signed in to Anthropic for runs on it until you do; on Hobby or the trial, pick a root from your own sign-ins. The task's model starts it when a change calls for one.

Clef reads each change first. One it is sure is confined to one place and proved by your project's checks runs solo on your Mac: one worker, your checks before and after, no plan or judge. A failing check or a risky file sends it back to the full route above. A change whose mistakes would pass the tests also gets a second reviewer on another model.

Your project's checks run first on the untouched code. A change fails if a passing check now fails twice, a failing one fails in a new way, a check the plan names fails, a test is weakened or a secret leaks.

Every seat runs at the reasoning level you set. As shipped, the Architect, the worker, the retry and the judge are Claude Opus 5.5, and the judge reads the finished change in a session of its own; you can put any seat on another model. On a paid plan with no Anthropic sign-in, every seat, the judge too, runs on DeepSeek V4.1 Flash. How muxcode works

Permissions on local tasks

Local tasks have four modes: Ask every time, Auto, Plan and Bypass permissions. In Auto, read-only commands and edits inside the project run, and muxcode asks about the rest.

Agent Auto
  • Runs
    • rg "split(" src
    • edit src/ledger.ts
  • Asks
    • pnpm add zod
    • edit ~/.zshrc
Allow bash?
pnpm add zod
Allow onceAllow `pnpm add` this sessionAlways allow `pnpm add`Deny

Remove saved rules in the Permissions settings. Plan mode allows only read tools. Cloud tasks show no cards, because their commands run in a container on mux.

Models

Sign in with OpenAI (ChatGPT), Anthropic, Gemini, xAI, Muse Spark or OpenRouter, or add any provider by key. Set the model and thinking level per task. Switching models keeps:

Anthropic muxcode
  • Tasks
  • Worktrees
  • History
  • Notes
  • Rules
  • Index

Cloud tasks

A cloud task's agent runs on mux; its commands run in a container with no credentials that can only download from listed hosts. The task keeps working while your Mac sleeps, until its lent sign-in runs out; a workflow waits for your Mac. muxcode brings the branch back after each turn.

The cloud sandbox Where a task runs, what it reaches and what it costs. Read more

What carries into a fresh context window

muxcode moves a long task to a fresh window instead of writing a summary. Each new window carries a recovery record of the first and latest request, the last tool results and pointers to notes.

Fresh windows
On by default
Recovery record
At most 20,000 characters, about 5,000 tokens
Older history
Fetched in pages of up to 40,000 characters

On a local task, the context meter shows what fills the window. To set a cap or go back to summaries, open Context windows in the Models settings.

Hand an issue to Cowork

Paste a GitHub issue into Cowork, in muxcode's sidebar, or describe a bug or a feature and Cowork writes the issue up with you first. A cloud session on its own branch writes a test that fails on today's code, then the change that makes it pass, and mux's GitHub App opens a draft pull request for you to review. It runs on mux's included DeepSeek V4.1 Flash, so it needs Pro or Pro+.

Cowork's Code review tab holds Reviewer, which reviews the pull requests that touch the paths you name. It reads the callers and importers of the change through your workspace's code index, not just the diff. Its reviews are drafts until you turn posting on, and it never approves: a person decides.

  1. Issue #212 checkout crash
  2. Failing test tests/checkout.test.ts
  3. Change validate.ts +4 -1
  4. Draft PR muxcode/issue-212-3fa8b1c2
Cowork Coworkers on the web that work while you are away, and tasks from an issue to a draft pull request. Read more

Also in the app

  • MCP servers muxcode asks before a local server starts, and its tool calls follow your permission mode. Cloud tasks get none.
  • Workspace memory Shared and private memory, kept in Git. Plan mode only reads it.
  • Skills for cloud tasks Pick them per project in Repo Settings.
  • Git controls Stage, commit, merge, push and open a pull request.

Plans

muxcode is free on your Mac. Pro, Pro+ and the trial add cloud tasks and include Clef. Cowork needs Pro or Pro+.

We remember either choice for 180 days in the mux_cookie_consent cookie. Read our cookie details.