A cloud computer for each task.

On mux, muxcode's cloud service, a task's agent runs beside its own Linux container and keeps working while your Mac sleeps, until its lent sign-in runs out.

muxcode 1.0.30 for Apple silicon

Pro, Pro+, Ultra and the 72-hour trial

Start a cloud task

  1. Sign in to mux in muxcode. Open the avatar menu, then Workspace settings.
  2. Open a Git project. The task gets uncommitted edits, not ignored files, files named like credentials or your Git history.
  3. Keep the mode on Sandbox. If it is missing, turn on Sandbox by default in Settings, then Models.
  4. Send your task. A first start can take a few minutes.

Read the guide

Where a cloud task runs

  1. Your Mac muxcode

    • Starts the task
    • Lends a sign-in

    To the agent: short-lived sign-in

  2. The agent pi, on mux

    • Model turns, transcript and notes

    model requests go to the model provider

    To the container: commands and files

  3. The container Linux, one per task

    • Commands, files and git
    • Toolchains
    • No credential

    To the gateway: every request

  4. The gateway on mux

    • Logs every decision

    reads only go to the listed hosts

    the task's branch, back to your Mac

Sandbox tasks show no permission cards. muxcode answers the task's permission checks while your Mac is connected. With no Mac, a workflow waits.

Your Mac lends an access token, or your API key for 12 hours, never the refresh token. When it runs out, the task waits for your Mac.

What the container can reach

The gateway forwards only reads (GET, HEAD, git fetch) to listed hosts: package registries, Debian mirrors, nodejs.org and public GitHub repos.

It strips sign-in headers and adds one credential: a 5-minute token for the task's fork. The only writes that leave are mux's own pushes to that fork; the gateway refuses a git push the agent runs.

gateway log
GET registry.npmjs.org/zodforwardeddownload-read PUT registry.npmjs.org/zodrefusedread-only-methods GET paste.example.com/rawrefusedhost-allowlist

Sleep, wake and the branch

After each turn
muxcode brings the branch back; you choose what reaches your files.
Away from your Mac
Watch it at usemux.com, under Sessions; while your sign-in is lent, send prompts or stop it.
After 10 idle minutes
mux pushes the work to the fork, snapshots the container's disk and stops it, or after 20 while a process the task started keeps running. Starting it again wakes it.
If a snapshot is lost
A rebuild drops ignored files, installed packages and build output.
After 14 days stopped
mux deletes the task and its fork.

Access and limits

  • Private to you Teammates see who started your task and when; only you can open it.
  • 30 minutes per command mux stops a command that runs longer.
  • Environment variables PI_ variables and up to 64 names from .muxcode/sandbox.json, minus credential-like ones.
  • Path limits File tools and a command's working directory stay in /workspace and /home/agent; a shell command can read elsewhere.

Toolchains

Pinned by version and sha256
Rust 1.98, Go 1.27, Bun, uv, Gradle, pnpm, cargo-llvm-cov, cargo-mutants
Pinned by version
Node 24 (major), Yarn 1.22
From Debian trixie
JDK 21, Maven, PHP 8.4, Composer, Python 3, pytest, git, git-lfs, ripgrep, fd, jq

Sandbox hours

PlanHoursAwake at once
Pro, $12/month40 a month5
Pro+, $120/month300 a month12
Ultra, $240/month750 a month30
72-hour trial3 in all1

Only time awake counts, and team members each use their own hours. At 90%, the Workspace page on usemux.com warns you; at the limit mux stops the task and keeps its files.

Plans

Pro, Pro+ and Ultra add cloud tasks. Pro includes 40 sandbox hours a month, Pro+ 300 and Ultra 750.

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