Splash
Helge Sverre
A desktop app for running several coding agents at once, each session in its project folder or its own git worktree. It drives agents over the Agent Client Protocol.12
splash.computerSplash and Supacode both run several coding agents at once, with git worktrees to keep their work apart. Supacode, a native macOS app that embeds libghostty, runs each agent’s own command-line interface in a terminal. Splash, a desktop app for macOS, Windows and Ubuntu, drives agents over the Agent Client Protocol and shows each session as a transcript.
Helge Sverre
A desktop app for running several coding agents at once, each session in its project folder or its own git worktree. It drives agents over the Agent Client Protocol.12
splash.computerSupabit
A native macOS app that runs terminal coding agents side by side. Each task gets a separate git worktree and Ghostty terminal, with GitHub pull request and CI status and a CLI for scripting.345
supacode.sh| Splash | Supacode | |
|---|---|---|
| The basics | ||
| What it is | Desktop app, plus a headless server you open in a browser16 | Native macOS app that runs terminal coding agents in git worktrees, plus a supacode CLI and supacode:// deeplinks43 |
| Release status | v0.2.1, early development17 | v0.10.8 (3 August 2026); the site labels the download beta, and a Tip channel ships continuous pre-release builds891011 |
| License | Open source (MIT)12 | FSL-1.1-ALv2, which bars competing commercial use; each version becomes Apache 2.0 after two years. The site calls it open source139 |
| Price | Free14 | Free download, labeled beta; no paid plan or price is published9 |
| Platforms | macOS 14+ (Apple silicon and Intel), Windows 11 x64, Ubuntu 24.04 x6415 | macOS 26 or newer, as a DMG or through Homebrew; a release note mentions Intel Macs. No Windows, Linux or mobile client16917 |
| Built with | Rust, with a Svelte 5 frontend in a webview, built on the Elyra framework18 | SwiftUI, The Composable Architecture and GhosttyKit (libghostty); no Electron or web wrapper169 |
| Agents | ||
| Agents | Ships launch commands for 20 agents, including Claude Code, Codex, Copilot, Gemini, Goose, OpenCode1920 | Hooks for 11 agents, including Claude Code, Codex, Copilot CLI, OpenCode, Kimi Code and Pi; any other agent that runs in a shell also works2122 |
| How it runs agents | Agent Client Protocol over stdio, natively or through a pinned adapter for the vendor’s CLI192 | Each agent’s CLI in a Ghostty terminal under zmx; hooks Supacode installs report presence and notifications over OSC 3008; neither docs nor source mention ACP232425 |
| Agent sign-in Who pays for the model | You install and sign in to each agent’s CLI yourself; Splash runs it with that login20 | You bring your own CLI agents; the docs don’t say how they sign in or whether Supacode bills for models926 |
| Account required | Splash has no accounts; splash-server asks for a token it keeps in its data folder276 | No Supacode account; GitHub features use your gh login, and Supacode keeps no GitHub credentials of its own2826 |
| Permission requests When an agent asks before it acts | Yes: Shown in the transcript and answered with the 1–9 keys; pending ones wait in Needs attention29 | Partly: Answered in the agent’s own terminal; Supacode documents no approval view, and its awaiting-input badge covers some agents30321 |
| Working in parallel | ||
| Isolation per session | Yes: The project folder, or a git worktree on its own branch per session29 | Yes: A git worktree on its own branch and folder per task, under ~/.supacode/repos by default; plain folders also work31223 |
| Setup scripts and dev servers | No: A worktree is a plain git checkout; Splash runs no setup scripts or dev servers2932 | Yes: Setup, run and archive scripts per repository, plus named custom scripts; new worktrees can copy ignored files. No port handling is documented33334 |
| Terminal | Yes: A terminal in the session folder29 | Yes: A Ghostty terminal per worktree with tabs, splits and find, using your Ghostty config; sessions outlast app restarts through zmx30223 |
| What needs you | Yes: One queue for permission requests, connection failures and finished turns, kept across restarts2935 | Yes: Live badges from agent hooks: busy and idle, plus awaiting input for some; worktrees that need you move to the top321 |
| Notifications | Yes: Notifies when a background session needs permission or finishes a turn; can be turned off3637 | Yes: In-app and optional macOS notifications, tied to the terminal that raised them, with sounds, muting and menu bar unread counts30338 |
| Review and shipping | ||
| Review changes | Yes: Latest response, failed tools and every changed file as a diff, with a box to send feedback29 | No: No diff viewer or feedback-to-agent action is documented; the toolbar shows lines added and removed3940 |
| Files and diffs | Partly: File tree, git changes and diff tabs; files open read-only, with no editor2941 | Partly: Stable builds document no file or diff view; worktrees open in an external editor such as Zed, Cursor or Trae. Tip builds add a file explorer34424310 |
| Create pull requests | No: Shows the PR for a session’s branch and starts worktrees from PR heads; does not create PRs2944 | No: Not documented; PR actions apply to branches that already have an open PR: open, mark ready, merge and close5 |
| GitHub | Yes: Issues, pull requests and Actions runs across repositories, through the gh CLI2944 | Yes: Through gh: PR and draft state, checks, failing-check details and job reruns, merge-queue state, and merging with the repo’s strategy52845 |
| Other code hosts Besides GitHub | No: github.com through the gh CLI; no other hosts44 | Partly: GitLab merge requests through glab, in Tip builds; stable v0.10.8 and the docs cover GitHub alone4610 |
| Issue trackers | Partly: GitHub (github.com), through the gh CLI; no Linear or Jira2944 | No: None documented; the GitHub integration covers pull requests and CI checks, not issues, and Linear and Jira aren’t mentioned528 |
| Where it runs | ||
| Remote access | Yes: splash-server runs on the machine with your code; you use it in a browser over an SSH tunnel. Single user.6 | Partly: Beta: manages worktrees of repositories on SSH hosts, Linux included; sessions survive dropped connections if the host has zmx338 |
| Auto-update | No: Download new versions from GitHub Releases; the app does not update itself1547 | Yes: Updates itself through Sparkle, from a Stable channel or a faster Tip channel11 |
| History and search | ||
| Existing agent history Conversations started outside the app | Yes: Browse, preview and import conversations agents list over ACP, including ones started outside Splash2935 | Not documented: Not documented; Supacode’s own terminal sessions persist across app restarts303 |
| Search transcripts | Yes: Search titles, folders and saved transcript text, archived sessions included29 | Partly: Find in a worktree’s terminal output and a fuzzy command palette for repositories and branches; no cross-session search is documented3048 |
Supacode runs each agent’s own CLI in an embedded Ghostty terminal, so any shell-based agent works. For 11 agents it installs hooks that report, as OSC 3008 sequences, whether the agent is busy or idle and, for some, awaiting input; it skips any agent not yet set up. Splash speaks the Agent Client Protocol with every agent and draws messages, tool calls, diffs and permission requests itself.2232125241192
Supacode runs on macOS 26 or newer. Its terminal sessions live in zmx, a session daemon, so they outlast the app, and a beta feature manages repositories on SSH hosts, Linux among them. Splash runs on macOS, Windows and Ubuntu, or as splash-server on the machine that holds your code, which you open in a browser over an SSH tunnel.16338156
Supacode is a free download labeled beta, with no paid plan published and no Supacode account described. Its source is public under the Functional Source License 1.1, which bars competing commercial use and turns each version into Apache 2.0 after two years; the homepage calls it open source. Splash is free, MIT-licensed and has no accounts.92813121427
Supacode centers on the worktree and its terminal: setup, run and archive scripts, a CLI and supacode:// deeplinks, and pull request status, CI reruns and merging through gh; no diff viewer is documented. Splash centers on the conversation: a Needs attention queue, a review screen with diffs and feedback, transcript search, and importing sessions agents started elsewhere.3335392935
Facts about Supacode come from its public website, documentation and repositories as they read on 10 October 2026; we haven't confirmed each one by running Supacode. Facts about Splash link to its source. Products change, so check the linked pages before deciding. Something wrong or out of date? Open an issue.