Context for your agent.
Compute for its tasks.

Ship more, and better with models you already use.

Create your workspaceDashboard Explore muxcode

muxcode's Agents settings: workflows that plan and delegate, and the skills every agent can load.

Bring your own subscription

Plug in the plans you already pay for. muxcode orchestrates them, you keep your plan.

Claude Code claude auth login
Codex CLI codex login
Grok CLI grok login
Muse Code Meta sign-in
Antigravity Google sign-in
OpenRouter API key

No compaction. Fresh context windows.
Durable notes across windows.
Full session history, searchable.

Ask the codebase in plain words

A workspace keeps one index of your team’s repositories. Search it by pattern on every plan, or by meaning with Pro and Pro+.

Search the workspace

Try asking:

Where do we validate checkout?
What calls the billing webhook?
How does sign-in refresh a session?

Shared workspaces

One place for your team’s repositories, people and agents. Grant code once, and every member and agent searches the same index.

Search by meaning

Ask a question and get the passages that answer it, each with its file, lines and commit, over search_code and ask_code.

storefront checkout/validate.ts validatePostcode(address) Lines 24–38 Checks each address against the postcode pattern before checkout accepts it, and returns a field error the form can show, read at commit 8c4e9b1.

api billing/webhook.ts handleBillingEvent(event) Lines 12–41 Called by the /webhooks/billing route once the signature checks out, then updates the workspace's plan, read at commit 3f1a2c7.

storefront auth/session.ts refreshSession(token) Lines 51–77 Swaps an expiring token for a fresh one before each request, and signs the user out if the refresh fails, read at commit 8c4e9b1.

One workspace in the middle

GitHub, muxcode, cloud sandboxes and every MCP agent meet at one shared code index, with one set of members and keys.

muxcode harness Plan, route, implement and review, on your desktop.
Plan-first workflow An Architect plans; Jev matches each package to a worker.
MCP access Give any MCP client the workspace index.
Scoped keys Mint and revoke keys for each member.
Re-index on push Pro and Pro+ keep every repository current.
Pattern search Match the shape of the syntax tree with grep_code, on every plan.
Fresh context windows On by default: notes carry into a new window.
Members and devices One index shared by the whole team.

A considered plan. A well-matched worker.

The Architect plans and reviews; Jev, the classifier, helps choose a worker and how hard it thinks.

Architect · Fix the postcode check in checkout

Planned steps

Find where checkout validates postcodes
Change the pattern and add a test
Run the suite in a sandbox

Jev matches the worker

It reads each planned package and picks the cheapest worker that clearly covers it. Unsure? It keeps the one you set.

Package 2 · change and testWorker · medium effort

The host enforces scope

Permissions and workflow gates stay on your desktop. The classifier advises; it never widens what a worker may do.

Edit files in checkout/
Run tests in the sandbox
Push the branch · asks first

Meet the workflow

Know what runs where.

What is mux, and what is muxcode?

mux is the cloud workspace: code indexing, sandbox execution and team access. muxcode is the desktop coding harness that connects to it and owns the agent session, worktree and permission decisions.

Can I use mux with other coding agents?

Yes. The code index is available over MCP and the API. Connect your agent with a scoped workspace key. muxcode adds the integrated desktop workflow and cloud sandbox experience.

What can I start with for free?

Hobby includes one indexed repository, pattern search and scoped MCP access. The desktop harness and permission gate are free. Pro and Pro+ add cloud sandboxes and semantic search. Compare the plans.

Does the classifier control permissions?

No. Jev helps assess planned work and reasoning effort. muxcode’s host applies permissions and workflow gates. An uncertain classifier result keeps the configured worker rather than choosing a different one.

What does Triage do with an issue?

It reads the bug report, investigates in a clone of the project, and leaves a branch you can land. Follow the run’s commands and diff, then checkpoint it and fetch the branch into muxcode. See the Triage workflow.

How do fresh context windows work?

They are on by default. When a long task nears its limit, muxcode starts a fresh window instead of writing a summary: agents check how much context is left, keep durable notes and can search the full session history. You can switch back to summary compaction in Settings.

Give your next task somewhere to run.

Create a workspace, connect GitHub and index one repository. Then run the agent from your desktop, or the cloud.

Compare plans