swe-mux: run several Codex sessions with live status, and the same sessions on your phone

[jatoran]

I run several Codex sessions at once, alongside Claude Code and pi, and built swe-mux to see which one is waiting on me.

• It runs the real codex CLI in a real terminal on your machine, logged in as you. Nothing is proxied.
• Each session shows working, done, or waiting on you, from what Codex itself reports plus the terminal.
• The same live sessions open on your phone over your own Tailscale network: the terminal, git diff review, files, previews of dev servers on the host, and a push notification when a session needs a decision.
• Sessions survive the app restarting or updating, because a separate supervisor process owns the terminals.
• A prompt queue holds what you think of mid-turn until the turn is done.

Windows has a desktop app. macOS and Linux run the daemon and use a browser. The installer is unsigned, so uv tool install swe-mux is the way around SmartScreen.

Demo, the real UI with simulated sessions: https://swemux.dev/demo/
Repo (Apache-2.0): https://github.com/jatoran/swe-mux

Not affiliated with OpenAI. If the install breaks, tell me which step.

[TheodorNEngoy]

I tried the simulated browser demo and opened Alerts. The Now / Review next split was easy to follow, but the interrupt-budget counter left me unsure what happens to a pending permission request. Your attention-ranking doc answers it: cheap blocking work does not spend that budget. Could that distinction be a short note beside the counter, or in the in-app help? It would make it easier to tell what still needs a check before leaving the desk. This is demo feedback; I have not installed it or tested real sessions.

Written with Codex assistance.

[jatoran]

Fair point, the counter doesn't say that. A pending permission request is cheap-blocking work, so it never spends the interrupt budget, however many are waiting. The budget (4 a day by default) only covers interrupt-now items: something getting worse, with a concrete action, at 0.8 confidence or higher. The session itself still shows waiting on you in the list either way.

A line beside the counter should say that. I'll add one.

[TheodorNEngoy]

Thanks, that resolves the ambiguity I hit in the demo. A short note that permission requests stay visible and never use the interrupt budget would make the counter clear to me.

[jatoran]

Added. The counter in Alerts now has a line under it: "Permission prompts and anything else quick to resolve never count as interrupts, however many are waiting, and a session waiting on you shows as awaiting even with the budget spent." It's in 0.3.0, which went out today, and the demo has it too: https://swemux.dev/demo/

[bomtobe-hgkim]

Disclosure: I work on Orke at BOMTOBE, a desktop workspace for Claude Code and Codex. The existing reply raises permission waits; I’m curious about a separate concurrency boundary: when two sessions edit the same repo, do you recommend one worktree or branch per session, or a shared worktree with serialized writes? A status view can show who is waiting, while the Git boundary decides whether parallel edits collide.

[jatoran]

One worktree and branch per session. A shared worktree with serialized writes still lets one agent build on another's half-finished edit, and serializing the writes doesn't fix that.

Nothing writes to trunk except a queue that lands one branch at a time: it merges trunk into the branch, runs the project's verification command, and fast-forwards trunk. A conflict or a failed check goes back to the agent that owns the branch instead of being resolved by the queue. Between Aug 21 and Sep 8 it landed 339 branches that way on my machine.