# CmdBrief vs iTerm + tmux + Claude Code: the stack you already run, or founder workspace?

> The iTerm + tmux + Claude Code stack against CmdBrief: what the panes-and-worktrees setup already does well, and what it cannot roll up across several products and vendors.

- **Category:** Comparisons
- **Updated:** 2026-09-29
- **Reading time:** 9 min
- **Canonical page:** https://cmdbrief.com/compare/iterm

The useful answer is not a replacement.

Do not compare CmdBrief to iTerm2 alone. The stack founders already run is **iTerm2 + tmux + Claude Code**: a macOS terminal, a multiplexer that keeps sessions alive, and Anthropic’s CLI (often with `claude --worktree` or `claude agents`). CmdBrief includes a real terminal, but the product is the local Mac workspace that pins agents, tasks, terminals, diffs, and browser context to each product. You can keep the stack. You can run CmdBrief. They overlap on “Claude Code in panes,” and since iTerm2 3.7 on seeing which Claude session is waiting for you. They do not do the same job.

Provider terms and product behavior can change. Confirm details in iTerm2, tmux, and Claude Code docs, and on [cmdbrief.com](https://cmdbrief.com/).

## The short answer

Keep **iTerm + tmux + Claude Code** when you already think in panes, you want sessions that survive SSH drops and app restarts (`tmux -CC` in iTerm2), and your parallelism problem is still *inside one product and one vendor*. Anthropic already ships three ways to run Claude Code in parallel: a second terminal with `claude --worktree`, `claude agents` for a dashboard of background sessions, and the desktop app (a worktree per session, as an option). All three are included with a Pro or Max plan. iTerm + tmux is the terminal-native way to hold that, and iTerm2 3.7 now shows each Claude session’s state on its tab.

Pick **CmdBrief** when the unit you supervise is the *product*, not the pane: several products at several stages, Claude Code on some and Codex or Grok CLI on others, attention rolled up, usage windows side by side. Apple silicon, macOS 26+, local-first. It creates worktrees only for a lead agent’s crew builders; pair your own sessions with `claude --worktree` if they share a repo. It is not an iTerm2 replacement.

If you only run Claude Code on one product, start with Anthropic’s tools and stop. See [How to manage multiple Claude Code sessions on a Mac](https://cmdbrief.com/guides/manage-multiple-claude-code-sessions).

## The data behind this comparison

Every value here comes from iTerm2’s own feed or documentation, linked beside it. Version, release date and licence refresh automatically from the vendor’s feed; pricing, platform support and the verdicts below are read by a person and dated. **Data checked 2026-09-29.**

|  | iTerm2 | CmdBrief |
| --- | --- | --- |
| Latest version | 3.7.3 · [source](https://iterm2.com/appcasts/final_modern.xml) | 0.5.35 · [source](https://cmdbrief.com/features) |
| Released | 2026-09-23 · [source](https://iterm2.com/appcasts/final_modern.xml) | 2026-08-06 · Generally available since 2026-08-06. |
| Platforms | macOS only; the stable update feed offers 3.7.3 for macOS 13 or newer and keeps 3.6.11 for macOS 12.4 · [source](https://iterm2.com/appcasts/final_modern.xml) | Apple silicon · macOS 26+ |
| Pricing | iTerm2 and tmux are free and open source; Claude Code needs a Pro, Max, Team, Enterprise or Console account, billed by Anthropic · [source](https://iterm2.com/) | €29.99/month or €299.90/year · 14-day money-back guarantee |
| Licence | GPL-2.0 (GNU General Public License v2.0) · [source](https://github.com/gnachman/iTerm2) | Proprietary |

*Checked 2026-09-29. Prices and platform requirements change — follow the source links before you decide.*

| Tool | Agent CLIs | Agent status | Usage windows | Usage across vendors | Per-product workspace | Diff review | Browser pane | Cloud execution | Windows / Linux | Open source |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| iTerm2 + tmux + Claude Code (v3.7.3) | Partial — Any CLI runs in a pane, and tmux keeps it alive. iTerm2 3.7 adds an optional Claude Code integration; other CLIs report status only through a control sequence, `it2` or a trigger you set up. | Yes — Since iTerm2 3.7, the Session Status tool and the Cockpit window show each session as working, waiting or idle across windows; the Claude Code integration sets it through hooks. | Partial — Claude Code’s `/usage` shows plan usage limits inside a session; neither iTerm2 nor tmux documents a usage view. | No — Claude Code’s `/usage` covers your Anthropic plan only. | Partial — Arrangements, tab groups, Workgroups and tmux sessions restore and group panes, and Session Notes persist per session; the docs describe no per-product home with tasks. | Yes — The Claude Code Workgroup puts a side-by-side Diff of working-tree changes and a Code Review session one click from the Claude conversation. | Yes — Web Browser profiles, since iTerm2 3.6, open pages in tabs and split panes beside terminal sessions. | No — Local, or whatever you SSH into. | No — iTerm2 is macOS-only; tmux and Claude Code are not. | Yes — GPL-2.0, at gnachman/iTerm2. |
| CmdBrief (v0.5.35) | Yes — Claude Code, Codex, Grok CLI, Kimi CLI, OpenCode, and Cursor CLI, supervised with the same states. | Yes — Working, needs-action, completed and failed, rolled up across every product. | Yes — Claude Code 5-hour and weekly, Codex weekly, Grok CLI weekly credits, OpenCode Go rolling / weekly / monthly, Cursor CLI monthly Cursor-models and Other-models pools; Kimi CLI exposes none | Yes — Several vendors’ windows side by side in the sidebar. | Yes — Agents, tasks, terminals, files, diffs and browser panes per product, with saved layouts. | Yes — A git diff viewer beside the agent that made the change. | Yes — Embedded macOS webviews. | No — Local-first. CmdBrief is not a cloud agent orchestrator. | No — Apple silicon · macOS 26+ only. | No — CmdBrief is not open source. |

*A dash means iTerm2 does not document the capability, not that it is missing. Pick a heading to read one column across both tools.*

> **Tip:** Spotted something out of date? Email hello@cmdbrief.com and it gets corrected at the source, on every page that uses it.

## What the iTerm + tmux + Claude Code stack is for

From iTerm2’s site and [3.7 release notes](https://iterm2.com/downloads/stable/iTerm2-3_7_0.changelog), tmux’s wiki, and Claude Code docs (fetched 2026-09-29):

- **iTerm2** is “a replacement for Terminal and the successor to iTerm”: free, GPL v2, source on GitHub. Its stable update feed offers 3.7.3 for macOS 13 or newer and keeps 3.6.11 for macOS 12.4 (the homepage still says 10.14). Documented features include split panes, a hotkey window, search, shell integration (prompt, command, host, directory awareness), triggers, Notification Center (activity, bells, job completion), a large profile system, and since 3.6 an AI Chat and Web Browser profiles that open pages in tabs and splits.
- **iTerm2 3.7** (September 2026) adds an optional [Claude Code integration](https://iterm2.com/claude-code-integration.html): hooks report each Claude session as working, waiting or idle in the Session Status tool, and a Cockpit window shows that status across every window. A ready-made Workgroup puts a side-by-side diff and a code-review session one click from the Claude conversation. 3.7 also adds tab groups, Session Notes, and iTerm2 Buddy, an iOS companion app for iTerm2’s AI chat.
- **Native tmux integration** (`tmux -CC`) turns tmux windows into real iTerm2 windows and tabs, so you get tmux persistence without living in tmux’s text UI. When iTerm2 quits or the SSH session drops, tmux keeps running; `tmux -CC attach` restores the windows. iTerm2’s docs also note two people attaching to the same tmux session to collaborate.
- **tmux** is a terminal multiplexer. Official wiki: switch between programs in one terminal, detach them (they keep running), reattach later. That is the persistence layer the stack is famous for.
- **Claude Code** is Anthropic’s terminal agent. System requirements on the getting-started page: macOS 13.0+, Windows, Linux; Pro, Max, Team, Enterprise, or Console (the free Claude.ai plan does not include Claude Code). Parallelism: `claude --worktree <name>` gives each session its own git checkout; `claude agents` lists background sessions as Needs input / Working / Completed; the desktop app can give each session its own worktree (separate comparison).

iTerm2 holds the panes. tmux keeps them alive. Claude Code does the work. Claude Squad and similar tools sit on this stack if you want a TUI session list; they are not required to call it “the real stack.”

## What CmdBrief is for

CmdBrief is a native Rust macOS app for the founder running several products. Each product gets a persistent workspace: agents, tasks, terminals, files, a diff viewer, and browser panes. The sidebar rolls attention up across all of them.

It supervises Claude Code, Codex, Grok CLI, Kimi CLI, OpenCode, and Cursor CLI with the same working / needs-action / completed / failed states, and shows each vendor’s usage windows side by side where the provider reports them (Claude Code 5-hour and weekly, Codex weekly, Grok CLI weekly credits, OpenCode Go rolling / weekly / monthly, Cursor CLI monthly Cursor-models and Other-models pools; Kimi CLI exposes none). Session resume lists local threads across those CLIs.

In the Standard view, Claude Code, Codex, Grok CLI and OpenCode run as agent panes that draw the conversation, edits and questions instead of a terminal. A lead agent (Claude Code or Codex) can start a crew of Claude Code, Codex and OpenCode agents in one tab, each on a Core, Standard or Light tier of model and effort, with progress counted in plan steps and the questions that need you in one **Needs you** list.

The terminal is a hand-written VT emulator with a GPU text path, not a chat box with a shell bolted on. The product is still the supervision layer, not the emulator.

Constraints that are real: Apple silicon, macOS 26+, local-first, generally available since 2026-08-06. One plan, CmdBrief Pro, display prices €29.99/mo or €299.90/yr, 14-day money-back, no free trial. It gives a lead’s code builders their own git worktrees when several share a repo; for sessions you open yourself, pair it with `claude --worktree` if you need isolated checkouts. It does not replace tmux’s detach/reattach over SSH.

## Where they overlap

You can run Claude Code in iTerm2. You can run Claude Code in a CmdBrief terminal pane. Both can split panes. Both can notify you (iTerm2: activity, bells, job completion, and since 3.7 a session status change; CmdBrief: agent needs-action, completed, failed, native macOS notifications).

Since iTerm2 3.7 the overlap is larger. Its Claude Code integration shows which Claude session is working, waiting or idle, puts a diff and a code-review session beside it, and iTerm2 can open a web page in a split. That covers Claude Code; other CLIs get a status only if you wire one up with a control sequence, `it2` or a trigger.

tmux + iTerm2 persist shell sessions across disconnects. CmdBrief persists *workspace layout* (tabs, panes, startup commands) and can resume *agent threads* via each CLI’s own resume flags. Those are different kinds of persistence. Do not equate them.

The [multiple sessions guide](https://cmdbrief.com/guides/manage-multiple-claude-code-sessions) already compared this stack: tmux-based tools solve isolation and some visibility; they do not show usage windows, and they are organised around sessions, not a founder portfolio.

## What iTerm + tmux + Claude Code does that CmdBrief does not

- **iTerm2 as a general macOS terminal**: hotkey window, profiles, shell integration, triggers, tmux -CC, AI Chat, macOS 13+ (12.4+ on 3.6.11), free GPL v2.
- **A phone companion**: iTerm2 Buddy pairs with your Mac over an encrypted relay so you can use iTerm2’s AI chat from iOS.
- **tmux persistence**: detach, reattach, survive SSH loss, share a session with another person attached to the same tmux session.
- **Remote-first workflows**: ssh to a host, `tmux -CC`, get native windows, come back later. CmdBrief is a local Mac workspace; it does not document itself as a remote multiplexer.
- **Claude Code’s own parallel tools, included with the plan**: `--worktree`, `claude agents`, desktop worktree sessions. CmdBrief does not replace those, and creates worktrees only for the code builders a lead agent starts.
- **Runs on older macOS** than CmdBrief (iTerm2 3.7: 13+, 3.6.11: 12.4+; Claude Code CLI: 13.0+). CmdBrief: macOS 26+.
- **No CmdBrief subscription.** iTerm2 and tmux are free. Claude Code is billed by Anthropic. CmdBrief is a paid workspace on top.

## What CmdBrief does that the stack does not

The stack is organised around sessions inside a project. CmdBrief is organised around products.

Documented on CmdBrief’s site; not provided by iTerm2 or tmux:

- **A persistent workspace per product** (not per tab or per tmux window): repos, tasks with acceptance criteria, terminals, diffs, browser panes, saved layouts.
- **Attention rolled up across several products**, so a blocked agent cannot disappear behind another product’s pane. iTerm2 3.7’s Cockpit groups session status by window, by state or by Workgroup, not by product.
- **A lead agent that directs a mixed crew**: Claude Code, Codex and OpenCode agents started from one lead, each on a Core, Standard or Light tier, with their own worktrees when several builders share a repo.
- **Usage windows from several vendors side by side** (Claude Code, Codex, Grok CLI, OpenCode Go, Cursor CLI). `claude agents` does not show usage in the list; `/usage` is in-session. The desktop usage ring is Anthropic-only. In the [GUI comparison](https://cmdbrief.com/guides/claude-code-gui-mac), Superset and Nimbalyst also document Claude and Codex usage side by side as of 2026-09-29; CmdBrief adds Grok CLI, OpenCode Go and Cursor CLI and rolls them up across products.
- **Session resume across Claude Code, Codex, Grok CLI, Kimi CLI, OpenCode, and Cursor CLI** from local metadata, reopened with the provider’s own resume flags.

iTerm2 will not invent those features because you tiled five `claude` tabs. That is not a knock on iTerm2. It is a terminal.

## Who should pick which

**Keep iTerm + tmux + Claude Code** if you are terminal-native, one product or one vendor, and the missing piece is isolation (`--worktree`) or a session list (`claude agents`, iTerm2 3.7’s Session Status tool, or a tmux-based manager). The stack is free besides your Anthropic plan.

**Choose CmdBrief** if your day is “I operate five products.” Switching products means switching repos, agent CLIs, tasks, and browser tools, and you want that operating context to come back attached. You can still use `claude --worktree` inside CmdBrief panes.

**Skip CmdBrief** if you wanted a prettier iTerm2. You do not. Skip the stack as your portfolio control room if you are already missing which product is blocked, which vendor’s window is exhausted, and where the launch checklist lives.

**A mixed setup is valid.** Some founders keep iTerm2 for SSH and one-off shells, and CmdBrief for product workspaces. CmdBrief is not asking you to uninstall iTerm2.

## Questions

### Should I compare CmdBrief to iTerm2 alone?

No. The realistic alternative is iTerm2 + tmux + Claude Code (often with worktrees). iTerm2 alone is a Terminal.app replacement. CmdBrief is not in that category.

### Does CmdBrief replace tmux?

No. tmux detaches and reattaches shell sessions, including over SSH. CmdBrief saves local workspace layouts and resumes agent threads with `claude --resume` / `codex resume` (and the equivalent for other supported CLIs). Different persistence.

### Can I run this stack and CmdBrief?

Yes. A mixed setup is valid. Keep iTerm2 for the shell you already like; use CmdBrief for the products you operate.

### When is the built-in Claude Code tooling enough?

When you supervise one product and one vendor. Use `claude --worktree`, `claude agents`, or the official desktop app. Third-party windows earn a place when you have several products or several vendors, or you want usage from several vendors on one screen.

## Primary sources

Provider terms and product behavior can change. Confirm plan, pricing, model, and permission details in the current official documentation.

- [iTerm2](https://iterm2.com/)
- [iTerm2 features](https://iterm2.com/features.html)
- [iTerm2 documentation](https://iterm2.com/documentation.html)
- [iTerm2 tmux integration](https://iterm2.com/documentation-tmux-integration.html)
- [tmux wiki](https://github.com/tmux/tmux/wiki)
- [Claude Code getting started / system requirements](https://code.claude.com/docs/en/getting-started)
- [Claude Code worktrees](https://code.claude.com/docs/en/worktrees)
- [iTerm2 3.7.0 release notes](https://iterm2.com/downloads/stable/iTerm2-3_7_0.changelog)
- [iTerm2 Claude Code integration](https://iterm2.com/claude-code-integration.html)
- [iTerm2 Session Status and Cockpit](https://iterm2.com/documentation-session-status.html)
- [iTerm2 Web Browser](https://iterm2.com/documentation-web.html)
- [iTerm2 stable update feed](https://iterm2.com/appcasts/final_modern.xml)
- [Claude Code agent view](https://code.claude.com/docs/en/agent-view)
- [CmdBrief](https://cmdbrief.com/)
- [CmdBrief features](https://cmdbrief.com/features)
- [How to manage multiple Claude Code sessions on a Mac](https://cmdbrief.com/guides/manage-multiple-claude-code-sessions)
- [Claude Code GUI for Mac](https://cmdbrief.com/guides/claude-code-gui-mac)

## Keep reading

- Comparisons: [CmdBrief vs Ghostty](https://cmdbrief.com/compare/ghostty)
- Comparisons: [CmdBrief vs Warp](https://cmdbrief.com/compare/warp)
- Comparisons: [CmdBrief vs Cursor-as-workspace](https://cmdbrief.com/compare/cursor)
- Comparisons: [CmdBrief vs Claude Desktop](https://cmdbrief.com/compare/claude-desktop)
- Comparisons: [CmdBrief vs Conductor](https://cmdbrief.com/compare/conductor)
- Comparisons: [CmdBrief vs opcode (Claudia)](https://cmdbrief.com/compare/opcode)
- Comparisons: [CmdBrief vs Emdash](https://cmdbrief.com/compare/emdash)
- Comparisons: [CmdBrief vs JetBrains Air](https://cmdbrief.com/compare/jetbrains-air)
- Comparisons: [Compare hub](https://cmdbrief.com/compare)
- Workflows: [How to manage multiple Claude Code sessions on a Mac (2026)](https://cmdbrief.com/guides/manage-multiple-claude-code-sessions)
- Comparisons: [Claude Code GUI for Mac: the options compared (2026)](https://cmdbrief.com/guides/claude-code-gui-mac)

---

Markdown mirror of https://cmdbrief.com/compare/iterm, generated at build time from the same data the HTML page renders. Machine-readable index: https://cmdbrief.com/llms.txt