DWG No. TT-003SCALE 1:1macOS 26 · APPLE SILICONREV 2026-09-03SHEET 03
◇ COMPARISON SHEET
thaytool vs Superset vs Conductor vs Maestri vs tmux
thaytool, Superset, Conductor, and Maestri all run several AI coding agents side by side on a Mac; tmux is the terminal multiplexer people reach for first. the differences that matter are how each one isolates work (a git worktree, a filesystem clone, or nothing), whether terminals outlive the app, whether an account or a cloud is in the loop, and how you pay (one-time or monthly). the table is compiled from each vendor's own site and says "not stated" where a vendor doesn't say.
↓ DOWNLOAD FOR macOS
$ brew install rafa-thayto/tap/thaytool
signed · notarized · no cloud · no telemetry · no account
§ 01side by side
Same job, different trade-offs.
| axis | thaytool | Superset | Conductor | Maestri | tmux |
|---|---|---|---|---|---|
| what it is | native macOS app: one git worktree and one persistent terminal per task, for CLI coding agents | "one workspace for Claude Code, Codex, and any coding agent" (superset.sh) | "run parallel Claude Code, Codex, and Cursor agents in isolated workspaces on your Mac" (conductor.build) | "the infinite canvas for orchestrating AI agents" (themaestri.app) | a terminal multiplexer: many terminals from one screen, no agent-specific features (github) |
| platform | macOS 26+, Apple silicon | macOS desktop app | macOS (docs) | macOS 15.4+ on Apple silicon; a separate Windows build | OpenBSD, FreeBSD, NetBSD, Linux, macOS, Solaris |
| isolation per task | a git worktree per workspace, on its own branch; one worktree per repo for multi-repo projects | a git worktree per agent | a git worktree per workspace (docs) | an APFS copy-on-write clone of the directory, not a worktree | none — sessions and windows only |
| agents | Claude Code and Codex out of the box; any CLI agent, the launch command is overridable | Claude Code, Codex, Cursor, OpenCode, Gemini, Mistral Vibe, Kimi Code, Grok CLI, Hermes | Claude Code, Codex, Cursor, OpenCode | Claude Code, Codex, OpenCode, or a shell | anything that runs in a terminal |
| terminals survive quitting the app | yes — a detached daemon owns every PTY, so sessions survive quit, self-update, and reboot; claude resumes with --resume | "closing a laptop doesn't kill the sessions" | not stated | not stated | yes — detach and reattach; the tmux server keeps running |
| account, cloud, telemetry | no account, no cloud backend, no telemetry; zero TCP ports | local-first; "cloud sync covers account and organization metadata only" | not stated | no account required; data stays on the machine; zero telemetry (vendor's own claim) | none |
| source | closed source; signed, notarized binary | source-available under the Elastic License 2.0 (github) | not stated | not stated | open source, ISC license |
| pricing | $20 one-time for up to three Macs; a 40-day trial that keeps working after it ends | free tier; Pro $20/month or $180 per user/year; enterprise custom (pricing) | free tier; Pro $50/month; Teams $60 per user/month; enterprise custom (pricing) | free tier; Pro R$95 one-time for up to two Macs; 7-day trial | free |
| built with | SwiftUI, a Metal terminal renderer, one binary; on-device Apple Intelligence for naming and routing | not stated | not stated | native; Metal-accelerated canvas | C |
prices and features change. every third-party cell is what that vendor's own site said on the date above, and the sources are linked below. "not stated" means their site doesn't say — it is not a claim that the product lacks the thing.
spotted something wrong? tell @thayto_dev and it gets fixed.
§ 02questions
Which one, and why.
❯ thaytool faq "which tool is best for running claude code and codex in parallel?"
it depends on what you're optimising for. thaytool if you want everything local (no account, no cloud), terminals that outlive the app, and a one-time $20 price. Superset if you want a free tier, the widest list of agent integrations, and team metadata synced through their cloud. Conductor if Cursor is part of your workflow. Maestri if you prefer a canvas UI and APFS clones over git worktrees. tmux if you only need terminals to persist and will manage branches yourself.
❯ thaytool faq "can I run thaytool next to Superset or Conductor?"
yes. thaytool uses fully disjoint namespaces — sockets, directories, URL schemes, environment variables — so nothing collides. its claude code hooks merge additively into ~/.claude/settings.json, and existing .superset and .conductor setup scripts run as-is in a thaytool workspace.
❯ thaytool faq "is thaytool a tmux replacement?"
no, it sits a layer above. tmux multiplexes terminal sessions; thaytool manages git worktrees — each workspace is its own branch, working tree, and persistent terminal — plus agent-aware status, macOS notifications, in-app diffs, and PR state. you can still run tmux inside a thaytool terminal.
❯ thaytool faq "why a git worktree per task instead of copying the repo?"
a worktree shares one .git with your main checkout, so branches, stashes, and objects stay in one place and merging back is an ordinary git merge. a filesystem clone duplicates the directory, including its own copy of .git — instant on APFS, but it is a separate repository copy you reconcile afterwards.
❯ thaytool faq "how does the pricing compare?"
thaytool is $20 once for up to three Macs, with a 40-day trial that keeps working. Superset and Conductor are subscriptions above their free tiers ($20/month and $50/month for their Pro plans). Maestri is R$95 once for up to two Macs. tmux is free and open source.
❯
§ 03sources