Paneflow

The multiplexer for the agent era.

Paneflow is a native terminal multiplexer for coding agents. Run agents in parallel, keep their sessions running when you close the app, and review their changes in a native interface.

Organize projects into tabs and split panes, with several agents in a tab when useful. Work in an existing checkout or create a branch and Git worktree for a separate task. Follow agent activity, see which sessions need attention, and read, interrupt, or take over any terminal. The dock brings together Changes (the checkout's diff against HEAD), Files (an integrated editor with Git markers and a file tree), and a terminal.

Works with any CLI agent - Claude Code, Codex, Gemini, opencode, Pi, Hermes, you name it.

Paneflow runs locally: agents are ordinary CLI processes in ordinary terminals and connect to their own model providers. Prompts are pre-filled and you press Enter; auto-submit is explicit and gated. Activity tracking depends on the integrations available for each agent.

Free and open source under GPL-3.0-or-later. Built with Rust and Zed's GPUI, using Ghostty's libghostty-vt terminal engine. Native builds for Linux x86_64 and aarch64, macOS Apple Silicon, and Windows x64.

Website →

Install

1. Quick start

On macOS:

brew install --cask arthjean/paneflow/paneflow

Everywhere else, take the build for your machine from the latest release: Linux builds come as .AppImage, .deb, and .rpm, and the .msi installs on Windows. The .deb and .rpm also register the package repo so later versions arrive through apt upgrade or dnf upgrade. Every artifact ships a SHA-256 sidecar and a Minisign signature.

Install docs →

2. Install for agents

Let one agent read another agent's pane, so you stop copy-pasting scrollback between them.

paneflow mcp install

This registers a local MCP bridge for supported agents it detects: Claude Code, Codex, Gemini CLI, and OpenCode. Its read tools are list_panes, read_pane, and search_pane, and terminal output comes back wrapped as untrusted data for the reading agent to analyze. Its one write tool, write_pane, sends a message to another agent's pane only after you allow that pair of agent sessions in Paneflow.

Bridge docs →

3. Coordinate a fleet

The paneflow CLI lets a script or an agent read, monitor, and control the panes you are watching. For text injection, launch Paneflow with PANEFLOW_IPC_SCRIPTING=1; send pre-fills text unless you explicitly add --submit.

paneflow ps
paneflow read cargo-run --lines 100
paneflow send codex-review "Review this branch and report risks"
paneflow wait --match claude-impl --pattern "REPORT_DONE"
paneflow watch --type ai.stop

paneflow up spawns a declarative workspace. paneflow flow run executes the steps you define in flow.toml: spawn panes or send text, order steps through dependencies, wait for readiness patterns, and capture output. Launching panes with commands or prompts requires PANEFLOW_IPC_ORCHESTRATION=1 or PANEFLOW_IPC_SCRIPTING=1. Prompt submission remains explicit and permission-gated.

Conductor docs →

4. Configure