Keyboard-first dashboard
Manage multiple CLI agents from one terminal UI with fast hotkeys for the work that needs attention.
Flowmux for Claude Code, Codex, and OpenCode
Run multiple AI coding agents from one terminal dashboard.
Where agent chaos becomes flow.
Keep real CLI sessions visible, organized, and resumable with a keyboard-first dashboard, optional Git worktrees, and tmux-backed persistence.
tmux panesreal CLI sessionsstatus hotkeysproject dashboards
Quick demo
A grid of active work, not a pile of hidden terminals.
Flowmux keeps the overview quiet: project dashboards, agent status, model information, and response previews are visible without leaving the terminal.
Why Flowmux
Keep your agent workflow in the terminal, not behind a wrapper.
Flowmux coordinates real agent CLIs, tmux panes, projects, and Git worktrees while leaving your editor, shell, and Git tools in place.
Unix-style by design
Flowmux coordinates panes, projects, agents, and worktrees without trying to replace the tools you already trust.
Bring your own tools
Keep using your preferred editor, git UI, shell, terminal, and command-line utilities around every agent session.
Clean grid view
Track running, waiting, and idle agents with model information and latest-response previews in the overview.
Projects and worktrees
Separate work by repo, task, or stream, then give agents their own working directories and optional git worktrees.
Real terminal sessions
Agent, git viewer, and shell views forward keys into live tmux panes instead of wrapping the agent UI.
tmux-backed persistence
Saved session state lets Flowmux reconnect to agents after tmux restarts so long-running work is easier to resume.
Native Rust TUI
Built with Ratatui, Tokio, tmux, libghostty-vt, and git2 for a focused terminal application.
Use cases
Parallel AI coding agents for the work already on your desk.
Implement, test, and review in parallel
Give each task its own CLI session and optional Git worktree, then keep an eye on every agent from one dashboard.
Keep repositories and tasks separate
Group work by project, repository, or stream so an active experiment never gets mixed into the work that needs to ship.
Return to long-running work without hunting for panes
Flowmux stores session state and reconnects to agents after tmux restarts, keeping long-running work easy to resume.
Typical workflow
A repeatable workflow for parallel AI coding agents.
- 01Create a project.
Separate work by repo, task, or stream when you want distinct dashboards.
p - 02Add one or more agents.
Create agents with separate working directories and optional isolated git worktrees.
n - 03Monitor the grid.
Watch running, waiting, and idle agents from the dashboard without opening every terminal.
h/j/k/larrows - 04Jump to what needs attention.
Move straight to running, waiting, or idle agents when the status changes.
Ctrl+qCtrl+oCtrl+p - 05Open the full agent terminal.
Read output, respond, inspect git state, or open a persistent shell in the agent directory.
EnterCtrl+vCtrl+t - 06Resume later.
Reopen Flowmux and continue from the saved session state after a restart.
flowmux
Supported agents
One dashboard for the agent CLIs already in your terminal.
Claude Code
Codex
Opencode
Flowmux auto-detects Claude Code, Codex, and OpenCode on your PATH, then enables discovered agents by default unless you configure an explicit allowlist.
Install
Best for a quick install on Linux or macOS. The script downloads the latest release, checks for tmux, and installs the binary into your local path without requiring a source checkout.
Requirements: Linux or macOS, tmux, and at least one supported agent CLI.
Free and open source: released under the MIT License.
Prebuilt Linux and macOS binaries are available on GitHub Releases.FAQ
Answers before you start a parallel agent workflow.
Does Flowmux replace tmux?
No. Flowmux is built on tmux and adds a keyboard-first dashboard for coordinating agent sessions, projects, and worktrees.
Which AI coding agents does Flowmux support?
Flowmux auto-detects Claude Code, Codex, and OpenCode installed on your PATH, unless you configure an explicit allowlist.
Does Flowmux wrap or replace my agent CLI?
No. Agent, git viewer, and shell views forward input to live tmux panes, so you keep working with the real command-line sessions.
Can each agent use its own Git worktree?
Yes. When you create an agent, you can give it an isolated Git worktree and working directory.
What happens after a restart?
Flowmux persists session state and can reconnect to agents after tmux restarts, making long-running sessions easier to resume.