Muxy

Parallel Development, Managed

Stop Hunting for Tabs.
Start Building Features.

Muxy reduces the hidden tax of parallel work: context hunting, app hopping, port conflicts, and accidental interruptions.

Speed is no longer about typing code faster

It's about managing context effectively

  • "Where is the tab for the checkout page?"
  • "Port 3000 is already in use."
  • "Which terminal is running the dev server again?"

Context gets scattered, then lost

A single feature ends up scattered across terminal tabs, editor windows, and browser sessions — with no shared structure tying them together.

Switching apps often lands you on the wrong window. Tracing a UI bug becomes a reverse lookup exercise: from page → repo → terminal → agent.

What was I working on again?

Working on multiple projects at once is hard. Worktrees make it even harder.

Meanwhile, small frictions compound

  • Port collisions quietly break local flows
  • Active work disappears into window chaos
  • Context switching erodes focus
  • Wrong processes get killed accidentally
  • Prompt is entered into the wrong terminal

The more parallel your workflow becomes, the more your environment fights you.

Introducing Muxy

Muxy organizes your terminals, browser tabs, and editors into worktree and project-specific workspaces.

Switch between branches and tasks instantly—without port collisions or lost context.

Without Muxy

  1. 1

    Find UI Tab

    Track down the browser tab for the right feature/project.

  2. 2

    Find Editor

    Locate the matching editor window.

  3. 3

    Find Agent

    Figure out which terminal/agent session made the change.

  4. 4

    Port Collisions

    Resolve :3000 collisions and update port references for relatedservices.

Result: context hunt before real progress begins.

With Muxy

  1. 1

    Open Workspace

    Jump straight to the workspace for this feature.

  2. 2

    Open Window

    Bring up its browser/editor/terminal/agent with a keyboard shortcut.

  3. 3

    Cycle Fast

    Switch within that workspace using keyboard shortcuts.

  4. 4

    Stable Ports

    Use workspace-owned ports and env without drift.

Result: stay within context, faster development loop.

How It Works

Three steps, one loop

Muxy organizes parallel work around workspaces, then lets you move through them with predictable shortcuts.

01 Select

Choose the workspace tied to the feature or branch you need to check in on.

02 Jump

Open the right browser, editor, or terminal window for that workspace instantly with a keyboard shortcut.

03 Continue

Cycle through only the windows of that workspace with keyboard shortcuts.

In Action

A repeatable loop, not a window hunt

Workspace boundaries stay clear. Switching between them stays fast.

Muxy

checkout-flow

Branch: feature/checkout

Running
CMD+1

npm run dev

CMD+2

pnpm test --watch

CMD+3

localhost:3000/checkout

CMD+4

app/checkout/page.tsx

pricing-update

Branch: feature/pricing

Running
CMD+1

pnpm test --watch

CMD+2

localhost:3001/pricing

CMD+3

app/pricing/pricing-card.tsx

bugfix-redirect

Branch: fix/auth-redirect

Stopped
CMD+1

codex --resume

CMD+2

localhost:3002/login

CMD+3

app/auth/redirect-handler.ts

bugfix-redirect

fix/auth-redirect

localhost:3002/login

app/auth/redirect-handler.ts

1819202122

codex --resume

$ codex --resume

ready on :3001

watching changes...

_

Key Features

Built for parallel streams of work

Muxy manages repos, worktrees, ports, processes, and windows. So you can focus on your work.

Manager mode for coding agents

Track all your coding agents in one place. Get notified when an agent is waiting on you. Use keyboard shortcuts to quickly navigate between them.

Manage Git worktrees. Or not.

Create and run isolated workspaces per branch so parallel feature work does not collide. Prefer separate checkouts instead of worktrees? Muxy works great for that too!

Organize work into virtual workspaces

Muxy organizes your terminals, browser tabs, and editors into worktree and project-specific workspaces. Switch between branches and tasks instantly—without port collisions or lost context.

Reserved ports per workspace

Each workspace gets named reserved ports as environment variables (e.g. $FRONTEND_PORT, $BACKEND_PORT) so services can run side by side without recurring port conflicts.

Switch between workspaces with ease

Jump between active workspaces quickly without needing to sort through dozens of browser/editor/terminal windows.

Switch between windows of the current workspace

Cycle through the current workspace windows with deterministic shortcuts, instead of hunting across apps.

Context tooltips

Ask your coding agent to set a workspace tooltip so you always have context when you switch in. Press cmd+shift+i to toggle it on/off when looking at any window belonging to the workspace.

Start and stop quickly

No need to keep those tabs open or processes running just because it is a pain to set it all up again. Muxy manages starting and stopping for you automatically.

Bring your own tools

Muxy works with your preferred stack, whether it is Claude Code or Codex, Cursor or Windsurf. You do not need to learn a new tool or settle for a weaker coding agent just for UX.

Native MacOS app under 5 MB

Built with Swift and AppKit — not Electron. No bloated runtime, no sluggish UI. Muxy stays out of your way and off your CPU.

FAQ

Common questions

How much does it cost?
Muxy is free!
What are the system requirements?
  • macOS 14 Sonoma or later
  • yabai — an open-source window manager used for window tracking and focus switching
  • iTerm2
What is yabai? Why does it need accessibility permissions?
yabai is an open-source macOS window management utility. Muxy uses it to bring the right window to the front when you switch workspaces. macOS requires accessibility permissions before any app can programmatically control windows on behalf of other processes — yabai uses this to perform focus switching on Muxy's behalf.
Can I use it with CLI coding agents like Claude Code or Codex CLI?
Yes. Open a terminal inside any workspace with ⌘⇧T and start your agent as normal. The terminal window is automatically attached to the workspace so you can jump back to it with keyboard shortcuts at any time. To let the agent set workspace tooltips and signal its status, add the Muxy agent instructions to your project's AGENTS.md. See the cookbook guides for step-by-step setup.
Can I use it with the Codex app?
Yes. Muxy works alongside the Codex app — it automatically imports Codex worktrees as workspaces. See the cookbook guides for a detailed walkthrough.
Can I use it with Conductor?
Yes. You can use Conductor to create worktrees and write code. Muxy will automatically import them as workspaces so you can manage windows and context with Muxy. We recommend using Muxy setup scripts and processes to configure workspaces and leaving Conductor setup and run scripts empty. See the cookbook guides for a detailed walkthrough.
Do you collect any data?
No. Muxy is a native desktop app that runs entirely on your Mac. It does not send any data back to Muxy or any third party.
Where do I send bug reports?

Build faster with Muxy

Muxy helps you build faster by managing context and reducing chaos.