๐ฌ๐ผ๐ ๐ฑ๐ผ๐ปโ๐ ๐ป๐ฒ๐ฒ๐ฑ ๐บ๐๐
๐ฐ๐ผ๐ฑ๐ฒ ๐๐ผ ๐๐๐ฒ ๐บ๐๐
.
In 3 minutes: Claude Code and Codex connect to ๐บ๐๐
with one config line and a key. Both answer a real question from your teamโs code index, down to the file and line. What they learn waits for an ownerโs approval before any other agent sees it.
Keep your agents. Give them your whole codebase.
We just published a 14-part video series taking one real project from initial setup to a reviewed pull request.
Step by step, the series builds on a production todo app running on Cloudflare Workers:
ย โข ๐ฆ๐ฒ๐๐๐ฝ: Sign up, connect GitHub, and index your code
ย โข ๐ ๐๐ฃ ๐๐ป๐๐ฒ๐ด๐ฟ๐ฎ๐๐ถ๐ผ๐ป: Use mux directly from Claude Code or Codex
ย โข ๐ง๐ฎ๐๐ธ ๐ ๐ผ๐ฑ๐ฒ๐: Choose between chat, plan, workflow, or sandbox
ย โข ๐๐ผ๐ป๐๐ฒ๐
๐ ๐ ๐ฎ๐ป๐ฎ๐ด๐ฒ๐บ๐ฒ๐ป๐: Keep long tasks going with fresh context windows instead of summaries
ย โข ๐ช๐ผ๐ฟ๐ธ๐ณ๐น๐ผ๐๐: Plan, build, check, and judge a change end-to-end
ย โข ๐๐ฒ๐น๐ฒ๐ด๐ฎ๐๐ถ๐ผ๐ป: Hand an issue to Cowork and get a draft PR back
ย โข ๐๐ผ๐ฑ๐ฒ ๐ฅ๐ฒ๐๐ถ๐ฒ๐: Get AI reviews on your PRs, drafts first
ย โข ๐๐ผ๐น๐น๐ฎ๐ฏ๐ผ๐ฟ๐ฎ๐๐ถ๐ผ๐ป: Bring in your team and configure billing
Start with the 11-minute explainer, then watch the episodes in order: youtu.be/4FQnMd3n-Jc
Your agents, your whole codebase. mux adds the cloud.
A pull request can look harmless and still break something in a file it never touched.
Try Reviewer in Cowork: usemux.com/cowork
Writing code with agents is fast.
Reviewing it is the bottleneck.
That was the #1 piece of feedback we got on Cowork. An agent can open a PR in minutes, but someone still has to verify it. And the bugs that actually break production rarely look obvious in an isolated diff.
Today, we're launching Reviewer. It is live now in Cowork's new Code Review tab, in muxcode, and on the mux web app.
Point Reviewer at any repository in your workspace index and define the paths you care about. It reviews every matching open PR immediately, and re-checks every 10 minutes. It runs in the background on mux, so it keeps working when your laptop is closed.
Most tools only read the diff. Reviewer reads the surrounding system:
โ Upstream callers of modified symbols, even across untouched files
โ Downstream imports and the exact lines where changed files are consumed
โ Your repository's REVIEW.md and workspace context
Why this matters in practice:
In one of our test repos, a PR updated surcharge rates from fractions (0.12) to percentages (12). The diff itself looked clean. Because Reviewer traced the callers, it saw that src/quote.js still multiplied the return value as a fraction. A 1,200 surcharge would have turned into 120,000. Reviewer marked the PR as blocking, wrote the fix, and generated a test covering quote.js end-to-end.
Every review gives you the failure mode, severity, proposed fix, and a test to catch it, linked to exact files and line numbers. If it hits a blind spot it cannot read, it states that explicitly instead of hallucinating a clean bill of health.
Two invariants we built in from day one:
1. Reviews remain private drafts until you explicitly enable posting.
2. Reviewer never approves. It comments or requests changes; a human always merges.
To everyone who told us review was the bottleneck: thank you. We built this for you.
Cowork and Reviewer are included in mux Pro, Pro+, and Team plans.
muxcode isnโt trying to replace Claude Code or Codex. Itโs built for developing and maintaining systems where mistakes are expensive, bringing codebase context, planning, checks and review together, with cloud sandboxes for isolated execution.
usemux.com
15
Introducing mux: the durable harness for your coding agents. Now in Preview.
Start with muxcode, a free Mac app. Your agent runs on your machine and only does what you allow.
Try it: usemux.com
