Jmux

jmux

From ticket to shipped feature, in the terminal you already use.

Define the workflow stages you actually think in, then run your whole backlog through a fleet of coding agents on them — Claude Code, Codex, or any agent, each in its own isolated session. jmux shows you who's working, who finished, and who's blocked on you. You're still the pilot.

▶ Watch the walkthrough — real agents, nothing staged.

Ticket in, MR out — Linear · GitHub · GitLab, self-hosted GitLab and GitHub Enterprise included.

Get running

- Install — the command above needs no runtime; it installs a self-contained
  binary. Also on Homebrew (brew install jarredkenny/tap/jmux) and npm
  (bun install -g @jx0/jmux, which needs Bun 1.3.8+ and is
  the only option on Alpine/musl).
- Requirements — tmux 3.2+. jmux offers to install it on first run.
- Just want to look around? jmux --demo runs with mock data — explore every feature, no credentials needed.
- New to tmux? Start with the Getting Started guide.

Features

Define your own workflow

Your tracker has a lot of statuses — Ready for Development, Awaiting QA Sign-off, Pending Release Approval — most of them named for someone else's process. You don't think in 25 states. You think in five.

So jmux has you define your own workflow stages and sit each one on top of one or many of your tracker's statuses:

A stage shows up as a tab in the info panel, but that's how it *appears*, not what it *is* — it's one rung on the ladder you actually work by, and its place in the list is its priority. Every status then has exactly two settings: which stage it belongs to, and whether it parks.

That second one is what keeps a fleet manageable:

- Park what you've handed off. A teammate has it in review, QA has it, it's blocked on someone else — that session…