Paneflow vs iTerm2

Some things the input research for this page got wrong, which this section flags up front so the rest reads honestly. iTerm2 is NOT CPU-bound - its own AGENTS.md states “PTYTextView - Metal-accelerated rendering.” The cleanest USP framing is not “modern GPU vs CPU veteran;” it is Metal (macOS-only) vs GPUI/Blade (cross-platform). And iTerm2’s Claude Code integration is NOT a launcher stub: the file ClaudeCodeHookEvent.swift at the iTerm2 repo root parses the upstream Claude Code hook event protocol via full Codable types, with companion files for onboarding, health monitoring, and a workgroup mode controller. The honest USP framing is not “agent-first vs agent-free;” it is CLI-agent-host (Paneflow) vs vendored multi-vendor chat (iTerm2).

With that out of the way: the two products solve overlapping problems with different priorities. iTerm2 has spent 16 years becoming the most thoroughly polished macOS terminal in existence, and in 2026 it added a serious AI surface (multi-vendor chat covering OpenAI, Anthropic, Gemini, and DeepSeek per its own AI live harness, plus Claude Code session hooks). Paneflow has spent one month becoming a cross-platform agent host where Claude Code, Codex, and OpenCode are the CLI binaries you already use, mounted into a workspace with branch detection, dev-server port banners, and session restore.

Grouped in three zones - portability & agent surface (where Paneflow leads), core terminal parity (where both are equivalent today), and the macOS-native polish (where iTerm2 has shipped much more surface).

Portability & agent surface

Core terminal parity

macOS-native polish

Versions: Paneflow v0.2.16 (May 2026), first commit 2026-04-01. iTerm2 v3.7.0beta1 released 2026-04-20 (commit 2b7b5bff), with v3.6.10 (2026-04-20) and v3.5.15 (2025-08-13) as older stable lines. iTerm2’s own release notes mark Claude Code integration as “still a work in progress as of 3.7.0beta1.” Pricing: both free. Paneflow MIT; iTerm2 GPL-2.0 with donation support.

The honest version: this is a clean either/or for most users. The two bullet lists below capture who each tool is genuinely built for. Most decisions land on portability + agent architecture vs macOS-native depth.

iTerm2 is a hybrid Objective-C / Swift application targeting macOS. The application flow is App -> Window/Tab -> Session -> Terminal Emulation -> Rendering. The terminal emulation stack is its own (VT100Parser, VT100Terminal, VT100ScreenMutableState, VT100Screen, VT100Grid), and the renderer is PTYTextView with Metal acceleration - the renderer is hard-locked to Apple platforms. The AI surface lives in sources/AITerm/ (about 81 files including AIConversation, AIPluginClient, and a Chat* family of view controllers) plus sources/ClaudeCode/ (six files: ClaudeCodeIntegrationMenuController, ClaudeCodeOnboarding, ClaudeIntegrationHealthMonitor, ClaudeWatcher, GlobalJobMonitor, PeerSessionSettingsViewController). The hook surface at the repo root - ClaudeCodeHookEvent.swift - is a full set of Codable types matching the upstream Claude Code hook protocol, so iTerm2 can react to session events from the Claude CLI as they happen.

Paneflow is a pure-Rust application built on Zed’s GPUI engine. There is no language boundary between the UI and the terminal - keystrokes travel through a single Rust pipeline from KeyDownEvent to paint, which is why keystroke-to-pixel latency stays under 4 ms and cold start under 200 ms. Terminal emulation is upstream alacritty_terminal0.26 from crates.io (no fork to maintain). The GPU stack is GPUI’s Blade renderer over Vulkan on Linux and Metal on macOS - so the renderer travels across platforms with the rest of the app. The agent surface is a workspace model: each workspace groups panes around a project root, with branch detection, port banners, and three first-class CLI agent buttons (Claude Code, Codex, OpenCode). External CLI agents are also unlimited: any binary you can run in a shell runs in a Paneflow pane.

The IPC surfaces are equally telling about each project’s era. iTerm2 exposes AppleScript (a long legacy .sdef bundle) and a Python scripting API with long-running script support, plus extensive shell integration (triggers, smart selection, prompt-aware features). Paneflow exposes a single JSON-RPC 2.0 server over a Unix socket at $XDG_RUNTIME_DIR/paneflow/paneflow.sock with roughly thirteen methods - smaller surface, faster to learn, far less coverage than iTerm2’s sixteen years of scripting accretion. Catching up to iTerm2 on automation is not on the immediate Paneflow roadmap.

Both projects are free. The licensing models differ:

• -Paneflow: MIT, Copyright (c) 2026 Arthur Jean. Embed it in commercial products without concerns; no copyleft constraint.
• -iTerm2: GPL-2.0, donation-supported. Strong copyleft - if you redistribute modified versions you must also release source. Embedding iTerm2 code in a closed-source product is functionally not an option. For an end user this difference is invisible; for an embedder it is the whole difference.

There is no direct config translation. iTerm2 stores settings in a binary plist (com.googlecode.iterm2.plist) that syncs through iCloud; Paneflow uses a static JSON file at ~/.config/paneflow/paneflow.json on Linux and ~/Library/Application Support/paneflow/paneflow.json on macOS. The install is a fresh setup that takes about ten minutes - default shell, theme, keybindings, AI agent buttons. The good news: Paneflow ships sensible defaults for the things iTerm2 makes you configure manually (workspace layout, agent buttons, theme), so the empty-config experience is closer to ready-to-use than to iTerm2’s.

What does NOT port across:

• -AppleScript / Python scripts: no equivalent in Paneflow. If you have automation written against iTerm2’s Python API or AppleScript surface, stay on iTerm2.
• -Shell integration features: triggers, smart selection, prompt-aware navigation, marks - these are iTerm2-specific. Paneflow uses a different, smaller integration surface.
• -Multi-vendor AI chat: Paneflow does not ship a vendored chat. The migration is to use the CLI agent of your choice (Claude Code, Codex, OpenCode) launched as a pane.
• -Workgroups + Code Review mode: no Paneflow equivalent. The closest concept is a workspace with multiple panes, but the Code Review prompt overlay and per-session toolbars do not have analogues.

The honest dealbreakers. If any of the five below matters to you, iTerm2 is the right tool today - no point fighting it:

1. 1.You depend on AppleScript or iTerm2’s Python API. iTerm2 has a long-established .sdef AppleScript bundle and a Python scripting API with long-running script support. Paneflow has a thirteen-method JSON-RPC and that’s it. Sixteen years of automation work does not port.
2. 2.You want a vendored multi-vendor AI chat in the terminal. iTerm2 ships a multi-vendor chat covering OpenAI, Anthropic, Gemini, and DeepSeek with a unified UI inside the terminal pane. Paneflow only launches external CLI agents - there is no in-terminal chat panel.
3. 3.You rely on iTerm2 shell integration features. Triggers, smart selection, prompt-aware navigation, marks - these are iTerm2-specific. If you rely on any of them, Paneflow does not have a replacement on the immediate roadmap.
4. 4.You want Workgroups with Code Review mode. v3.7’s Workgroups + Code Review mode is genuinely novel: it shows an in-session prompt overlay before the program runs, exposes the entered text as a variable for swifty interpolation, and lets you build review pipelines around it. Paneflow has no equivalent.
5. 5.You want sixteen years of polish and a 17 k+ star community. iTerm2 is at v3.7 with sixteen years of accumulated bug fixes, edge cases, and ecosystem (terminfo entries, dot files, Stack Overflow). Paneflow is at v0.2.x with a fraction of that ground-truth time.

Ready to try Paneflow? Download the latest release or read the getting-started guide. Curious about iTerm2 instead? iTerm2 is on GitHub - it is the most polished macOS terminal in existence and a worthy alternative for any macOS-only workflow that values AppleScript or Python automation.