Supacode
A native macOS command center for running coding agents in parallel, each with its own worktree and terminal.
Evidence shows: README describes SSH remote repos, session persistence, auto-updates, but lacks specific implementation details for least privilege, user confirmation, data flow transparency, sensitive data handling, dependency security, external effects, rollback, or source attribution. Deductions: lack of concrete evidence, only descriptive claims, cannot confirm actual security measures.
Evidence shows: README and CI workflow provide build, test, lint commands, but no specific examples of failure messages or error handling. Deductions: dependency availability mentioned (mise, Xcode), but failure messages not detailed.
Evidence shows: README clearly states target users (macOS developers), use cases (parallel coding agents), capability boundaries (local and SSH), trigger methods (CLI, deeplink, hotkeys), and environment requirements (macOS 26+). Deductions: capability boundaries and trigger precision described, but no detailed configuration options or limitations.
Evidence shows: README well-structured with install, build, development, tech stack, contributing; LICENSE clearly FSL-1.1-ALv2; SECURITY.md provides vulnerability reporting. Deductions: missing version history or changelog, limited examples and FAQ, maintenance responsibility not explicit.
Evidence shows: README describes output as real terminal, notifications, PR tracking; marginal value in parallel worktrees and session persistence; cost-benefit via open source and auto-updates. Deductions: no performance benchmarks or user feedback, cost-benefit based on description only.
Evidence shows: README claims (e.g., agent support, SSH features) lack test or verification evidence; CI workflow exists but no test results shown. Deductions: claims lack traceability, cross-source corroboration insufficient, facts and inferences not clearly separated.
- Static review cannot verify actual security measures like least privilege and data flow transparency.
- Dependency security lacks specific versions or vulnerability scanning evidence.
- Version history and changelog missing, may affect update tracking.
What does this agent do, and when should you use it?
Supacode is a native macOS application that serves as a command center for coding agents. It allows you to run multiple coding agents (e.g., Claude, Codex, Copilot) side by side, each in its own git worktree and real terminal, ensuring they don't interfere with each other. Sessions persist in the background via the lightweight session daemon zmx, so quitting the app or dropping an SSH connection loses nothing, including scrollback. Beyond local repositories, it supports managing worktrees on remote hosts over SSH (Beta), reusing a multiplexed connection and reattaching after disconnects. The app integrates GitHub pull request tracking, live agent status badges, custom scripts, a command palette, deep links, and a CLI for powerful control. It is built on The Composable Architecture and libghostty for terminal rendering, and supports auto-updates via Sparkle.
Supacode provides the following concrete operations: creates and manages git worktrees from the sidebar, hotkeys, command palette, CLI, or deep links; starts a real terminal session (based on libghostty) in each worktree, with tabs and split panes; detects the coding agent (e.g., Claude, Codex, Copilot) in each pane via installed hooks, displaying a live status badge (busy, awaiting input, idle) and sending notifications when attention is needed; persists sessions using the zmx daemon, allowing reattachment after app quit or SSH disconnection with scrollback intact; manages worktrees, tabs, splits, and repos via the supacode CLI and deep links (supacode://); integrates with GitHub to track each worktree's pull request state, checks, and merge readiness; runs custom scripts (per repository or global) added to the Script Menu, palette, and deep links; and supports remote SSH repositories by sharing one multiplexed SSH connection for git probes and terminal sessions.
- A developer juggling multiple feature branches wants to run several coding agents in parallel without collisions.
- A developer who maintains code on a remote server via SSH wants to manage worktrees and keep terminal sessions alive through disconnects or laptop sleep.
- A team lead needs to monitor the live status of multiple agent tasks and respond promptly via notifications.
- A power user uses the command palette and CLI to quickly switch between worktrees and repositories, boosting workflow efficiency.
- A user wants per-repository setup and archive scripts, and to trigger actions from other apps via deep links.
What are this agent's strengths and limitations?
- Each task gets its own worktree and real terminal, enabling true parallelism and isolation.
- Session persistence via zmx runs in the background; quitting the app or losing connection does not lose state, and scrollback reattaches.
- Live agent status detection (Claude, Codex, Copilot) with notifications enables timely responses.
- Comprehensive control interfaces: CLI, deep links, command palette, and hotkeys.
- GitHub integration for PR tracking and custom scripts enrich the workflow.
- Only supports macOS 26.0+ and requires Xcode 26.3 (on macOS 26.4+) for building, tying it to the Apple ecosystem.
- Remote SSH support is in Beta, with some local-only features reduced.
- Build depends on multiple toolchains (mise, GhosttyKit, Metal Toolchain), making setup complex.
- No precompiled binaries; users must build from source.
How do you install or deploy this agent?
Clone the repository with submodules: git clone --recursive [email protected]:supabitapp/supacode.git; then cd supacode and run mise install to install the pinned toolchain. Ensure ~/.local/bin is in your PATH. Run make doctor to check build prerequisites (mise, submodules, Zig-linkable Xcode, Metal Toolchain) and follow its output to fix anything missing. Finally, make run-app builds and launches the Debug app. Note: on macOS 26.4+ (Tahoe), you must install Xcode 26.3, accept its license, run first launch, and download the Metal Toolchain because the pinned Zig version cannot link the newer SDK.
How do you use this agent?
After launching the app, create a new worktree from the sidebar, hotkeys (⌃1-⌃9), command palette, or CLI. Select or clone a repository, and assign a coding agent. The app detects agent status automatically and shows badges. Use the CLI (supacode) to manage sessions, e.g., list worktrees, split panes, run scripts. Deep links (supacode://) let other apps trigger actions. Sessions persist in the background even when you quit the app, and they reattach exactly where you left off when you relaunch. For remote SSH repositories, add the remote host and the app reuses the SSH connection.