Skip to content

Getting started

Guide

A direct path from account creation to one indexed repository and one answered search. Onboarding walks the same path screen by screen.

Looking for the desktop app? Start with muxcode’s first run. Connecting muxcode to mux and signing in to a model provider are separate steps. muxcode also runs on your Mac with no mux account at all; see Run on your Mac only.

muxcode runs pi, the agent, built into the app, with a permission gate on its tool calls, fresh context windows, workflows and your own MCP servers. None of that needs a plan. mux, at usemux.com, adds the shared parts: a workspace, its code index, agent memory and the MCP server. Hobby is free, with no code search and no memory. Pro, Pro+ and the trial add code search, by pattern and by meaning, agent memory, refresh on every push, more repositories, team workspaces, cloud sandboxes and included Clef tokens.

muxcode, on your Mac

The agent and its guard no account needed

  • pi, the agent built into the app
  • The permission gate guards its tool calls
  • Fresh context windows
  • Workflows
  • Your own MCP servers
every plan, or none
mux, once you sign in

Hobby free, at usemux.com

  • Your workspace and its access keys
  • One repository chosen indexed once you have a plan
  • The MCP server usemux.com/mcp
every plan
Pro, Pro+ and the trial add

$12 or $120 a month trial: free for 72 hours

  • The index and code search by pattern and by meaning
  • Context and trace get_context · trace_code
  • Agent memory read, save and search
  • Refresh on every push 20 repositories; Pro+ 50
  • Team workspaces Pro 1 · Pro+ 25
  • Cloud sandboxes Pro 5 at once · Pro+ 12 · trial 1
  • Clef tokens included Pro 280,000 a day · Pro+ 2,800,000
per organization
muxcode works alone on your Mac. Signing in to mux adds a workspace on every plan; Pro, Pro+ and the trial add the index and code search, memory, refresh on push, sandboxes and Clef. What each plan includes has every figure.
  1. 01

    Start in your workspace

    Create an account and mux opens your first workspace, named Personal, at once, on Hobby, which is free but indexes nothing and has no code search. To index and search a repository, choose Pro or Pro+ on the pricing page, or sign muxcode in to mux with a verified email address to start the 72-hour Pro trial. Rename the workspace from your account menu: Settings, then Name under Workspace. If you were invited first, accept the invitation instead. Each workspace keeps one code index. Hobby is your personal workspace alone; Pro and the trial add one team workspace, and Pro+ twenty-five. Team workspaces are shared with members; creating a team does not buy a plan or add another copy of anyone’s allowance.

  2. 02

    Connect GitHub

    Open Code Index and connect GitHub. You install the GitHub App on the account or organization that owns the code and choose which repositories the installation grants. Nothing outside that grant is read. If the app is already installed there, for example after a connection that expired, choose Link an existing installation instead.

  3. 03

    Choose repositories

    Pick the granted repositories to index, on the branch GitHub reports as default or one you name. Hobby can choose one repository, indexed once the workspace has a paid plan or a trial; Pro and the trial index twenty, and Pro+ fifty. A team workspace indexes as many as the best plan among its members; an owner’s plan counts for as many of their team workspaces as it includes.

  4. 04

    Watch the index build

    Each repository is mirrored, its files split into syntax-aware chunks and embedded. Code Index shows the state of each repository: Copying, Indexing, Queued (waiting while another index run goes first), Current, Behind or Failed, with the indexed commit and the file and passage counts. On Hobby the row says Chosen: kept, and indexed once the workspace has a plan that searches. Hobby builds no index; Pro, Pro+ and the trial refresh on every push. A refresh GitHub turns away for a moment is tried again by itself.

  5. 05

    Search from Home

    The Home page has one search box. On Pro, Pro+ and the trial, ask in your own words; a name in the question, like retryDelivery, also matches exactly and shows first. Hobby has no code search: in its place Home says search comes with Pro and Pro+, with a link to the plans. Agents keep the full pattern search below.

  6. 06

    Give your agents the same index

    Create an API key under Access keys, in the sidebar’s Workspace group, then follow the MCP guide to connect Codex, Claude Code, or GitHub Copilot CLI. On your desktop, choose Connect to mux in muxcode’s workspace settings, approve the matching request on usemux.com, and wait for the desktop to show the connected workspace. No key is copied by hand.

Every plan
corpus_status index state record_context_outcome findings
Pro, Pro+ and the trial
grep_code pattern search_code by meaning ask_code a question get_context evidence trace_code one file workspace_memory memory
Hobby asks for code or memory
the code and memory tools answer 403 plan_refused
Findings work on every plan. Code search, context, trace and memory need Pro, Pro+ or the trial; Hobby gets a clear refusal.

Pattern search (grep_code). Matches the shape of the syntax tree rather than text: foo(\X) finds every call of foo with one argument, whatever that argument is. A backslash marks a placeholder; $X is matched as text and finds nothing. Narrow it with a repository, a language, or a path prefix inside the corpus. Pro, Pro+ and the trial.

Search by meaning (search_code). Ranks chunks by what they mean, not by the words they contain, and returns the repository, file path, start and end lines, a score, and an excerpt. Pro, Pro+ and the trial.

Ask a question (ask_code). Takes a question in plain words and returns the passages from the index that bear on it, for your agent to read. The answer itself is not written for you. Pro, Pro+ and the trial.

On Hobby, every code tool answers 403 with {"error":{"code":"plan_refused"}}.

Context for a task (get_context). One call returns the evidence for a task across the workspace’s repositories, each piece tied to the commit it was read at, plus the files the code graph links to it: what they import, what imports them, their tests, and the routes one repository calls in another. Pro, Pro+ and the trial, up to 60 calls an hour per workspace.

One file on the graph (trace_code). What a file defines, imports and is imported by, its tests and routes, and its owners. Pro, Pro+ and the trial.

Memory across sessions (workspace_memory). Shared workspace knowledge and each member’s private notes live in separate memory repos: Git repos that mux keeps, not GitHub repositories. Start at MEMORY.md, follow links, or search. Each edit commits to Git and checks the revision you read, so concurrent sessions cannot silently overwrite one another. get_context includes relevant memory alongside code evidence. Memory needs Pro, Pro+ or the trial, and counts against search and memory hours. On Hobby every memory call answers 403 plan_refused.

Findings. An agent proposes a finding from a context packet (record_context_outcome). It reaches no one until a workspace owner approves it on the Overview page. An approved finding comes back with context and moves to each new commit while the files it cites stay the same. The MCP guide has the arguments; Onboarding shows the screens.

One mirror is kept per selected repository and re-indexed from the branch you chose. Hobby builds no index: its chosen repository waits for a paid plan or a trial. Pro, Pro+ and the trial refresh on push. A repository whose latest commit differs from its indexed commit shows Behind, and anyone with the editor or owner role can refresh it from Code Index.

Each workspace on a paid plan or the trial has 30 hours of index time a month for refreshes. Past that, a push waits for the nightly refresh.

Code search, get_context and memory count apart, in search and memory hours: 50 a month on Pro and the trial, 300 on Pro+. They are each person’s own, counted across their workspaces and every team they are in; a team has none of its own. Each call counts the time it keeps the index awake, plus 10 idle minutes. Past them, search and memory answer 429 search_hours_spent until the UTC month turns.

GitHub the repositories you grant
Mirror one per repository, on your branch
The workspace's index syntax-aware chunks; embedded on Pro, Pro+ and the trial
Home search on the web
muxcode Connect to mux
Your agents over MCP
Hobby Builds no index until the workspace has a plan or a trial.
Pro, Pro+ and the trial Refreshes on every push, within 30 index hours a month per workspace.
Past 30 hours A push waits for the nightly refresh.
One index per workspace, read the same way from the web, from muxcode and from any agent. When it refreshes depends on the plan.

Removing a repository removes its mirror and its part of the index.

Hobby Pro Pro+ Pro trial
Price free $12 a month $120 a month free for 72 hours
Team workspaces besides your own 0 1 25 1
Repositories indexed none (1 chosen) 20 50 20
Index refresh none on every push on every push on every push
Code search, by pattern and meaning no yes yes yes
Search and memory hours 0 50 a month 300 a month 50
Agent memory no yes, by meaning yes, by meaning yes, by meaning
Cloud sandboxes running at once 0 5 12 1
Sandbox hours 0 40 a month 300 a month 3 in all
Clef input tokens a day 0 280,000 2,800,000 280,000
Clef input tokens per five hours 0 100,000 1,000,000 100,000
API requests 30 a minute, 50,000 a month 120 a minute, 500,000 a month 300 a minute, 2,000,000 a month as Pro

Prices are per organization. A Pro trial starts when you first sign muxcode in to mux with a verified email address: once per Mac, account and email address.

If your plan drops below the repositories a workspace indexes, it keeps the ones you added first. The rest stay for a week, marked on Code Index with the day they go, then mux removes them and their index. Upgrade within the week to keep them.

Team is not a plan you buy. A team workspace’s requests and repositories are those of the best plan among its members, while sandboxes, Clef and mux’s included model, which Cowork runs on, come from each member’s own plan, wherever they work.

An owner’s plan counts for as many of their team workspaces as it includes: one on Pro or the trial, 25 on Pro+. If you own more, say after a move from Pro+ to Pro, pick which on Billing; until you do, your plan covers the oldest. The others take the best plan among their other members, or Hobby’s figures when none brings one, and keep their first repository.

The MCP server works on every plan; code search and agent memory need Pro, Pro+ or the trial. muxcode, its permission gate, fresh context windows, workflows and your own MCP servers need no plan at all. How Clef works explains the Clef windows.