# Paneflow vs WezTerm

> Paneflow organizes coding agents with panes, branches, statuses, and diffs. WezTerm is a mature terminal and multiplexer programmable in Lua. If agents structure the work, pick Paneflow. If the terminal itself is the product, pick WezTerm.

URL: https://paneflow.dev/compare/wezterm
Raw Markdown: https://paneflow.dev/compare/wezterm.md
Last updated: 2026-07-02

## Highlights

### Track agents, not just processes

Paneflow runs CLI agents in real terminal panes and shows when they are active, waiting, stalled, or done. WezTerm can run the same commands, but it does not model them as agents.

### Give agents pane context

Paneflow exposes read-only MCP tools for listing, reading, and searching panes. WezTerm has a CLI and mux API, but no native MCP server.

### Review branch diffs in the workspace

Paneflow connects worktrees, diffs, and prefilled agent review terminals. WezTerm is a terminal and multiplexer; it does not ship a worktree or diff review flow.

## The important differences

Paneflow is the agent workspace. WezTerm is the programmable terminal. The split is not Rust or GPU rendering; both have that. The split is workflow ownership.

| Topic | Paneflow | WezTerm |
|---|---|---|
| Best for | Coordinating coding agents, panes, branches, and diffs | Building a programmable terminal, mux, SSH/TLS, and image workflow |
| Platforms | Linux, macOS, Windows | Linux, macOS, Windows, FreeBSD, NetBSD |
| Agent orchestration | Native launchers for 16 CLI agents plus status tracking | Runs any CLI command; no native agent model |
| Pane context for agents | Read-only MCP tools to list, read, and search panes | CLI and mux API; no native MCP server |
| Diff and branch review | In-app diffs plus prefilled agent reviews | No native worktree or diff review flow |
| Remote and terminal protocols | Local workspace; no SSH/TLS domains or inline image protocols | SSH/TLS domains, serial, Sixel, Kitty, and iTerm2 images |
| Configuration | JSON | Lua scripts, hooks, and key tables |

Versions: Paneflow v0.7.6 is GPL-3.0-or-later and currently ships two themes. WezTerm is MIT, first committed in 2017, latest tagged stable in February 2024, with main branch still active and 1000+ color schemes.

## Which tool should you use?

Choose based on what you want to customize: your agents' work, or your terminal itself.

### Choose Paneflow if

- You coordinate several coding agents at once
- You want MCP pane reading and branch-aware diff review
- You want real terminal panes without writing a Lua environment
- You group tasks by sessions, panes, branches, and worktrees

### Choose WezTerm if

- You want to program the terminal itself in Lua
- You need SSH/TLS domains, serial, inline images, or many color schemes
- You need FreeBSD or NetBSD support
- You want a mature everyday terminal or multiplexer more than an agent workspace

## Frequently asked questions

### Is Paneflow a fork of WezTerm?

No. They are independent Rust codebases with no shared source. WezTerm began in 2017. Paneflow is built on Zed's GPUI with upstream alacritty_terminal as its VT layer. Same broad stack, different goals.

### Does WezTerm have native coding-agent orchestration?

Not in the local repo or docs. WezTerm has a powerful CLI and mux API, including pane text capture, and Lua can launch any CLI agent. It does not ship an MCP server, agent status tracking, branch workspaces, or built-in diff review.

### When should I keep WezTerm?

Keep WezTerm when terminal customization is the core workflow: Lua hooks, SSH/TLS domains, serial, inline images, BSD, or a large color-scheme ecosystem. Paneflow is for supervising local coding agents, not replacing every terminal feature.


## Try the tool that fits your workflow

Want to organize multiple agents without building your environment in Lua? Download Paneflow or read the getting-started guide. Want to program every detail of your terminal or need its SSH and image features? Discover WezTerm on GitHub.