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 Solo are both desktop apps for running several coding agents at once. Solo is a Tauri app that runs each agent’s own CLI in a terminal beside your dev servers, with an MCP server agents use to coordinate. Splash talks to agents over the Agent Client Protocol, each session in its project folder or a git worktree.
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.computerTry Hard Studios (Aaron Francis)
A desktop “meta-harness” that runs the agent CLIs you already use in terminals next to your dev commands, with an MCP server that lets agents spawn and coordinate other agents.3
soloterm.com| Splash | Solo | |
|---|---|---|
| The basics | ||
| What it is | Desktop app, plus a headless server you open in a browser14 | A Tauri desktop app, a “meta-harness” for the agent CLIs and dev commands you already use; not an editor35 |
| Release status | v0.2.1, early development16 | v0.10.1 (September 3, 2026); the download page calls it a beta78 |
| License | Open source (MIT)9 | Proprietary and closed source; the Terms forbid reverse engineering105 |
| Price | Free11 | Free: every feature, 4 projects, 20 processes. Pro: $99 a year. Team seats: $99 down to $69 each a year3 |
| Platforms | macOS 14+ (Apple silicon and Intel), Windows 11 x64, Ubuntu 24.04 x6412 | macOS 11+ (Apple silicon and Intel), Windows 10 1809+ (64-bit); Linux is listed as coming soon138 |
| Agents | ||
| Agents | Ships launch commands for 20 agents, including Claude Code, Codex, Copilot, Gemini, Goose, OpenCode1415 | Built in: Claude Code, Codex, Amp, Gemini CLI, OpenCode, Copilot CLI, Kimi CLI, Antigravity; other interactive CLIs as custom tools316 |
| How it runs agents | Agent Client Protocol over stdio, natively or through a pinned adapter for the vendor’s CLI142 | Runs each agent’s installed CLI in a PTY terminal, where you type prompts; its docs don’t mention ACP3175 |
| Agent sign-in | You install and sign in to each agent’s CLI yourself; Splash runs it with that login15 | Uses each CLI’s existing login, subscription or API key; Solo neither installs the CLIs nor asks for provider keys316 |
| Account required | Splash has no accounts; splash-server asks for a token it keeps in its data folder184 | Not for Free. Pro checks its license key with soloterm.com, with 14 days offline by default; team-seat claimants sign in or register319 |
| Model and mode pickers | Yes: Model, mode and effort pickers when the agent offers them20 | No: Solo adds none of its own; each CLI keeps its own models and configuration321 |
| Permission requests | Yes: Shown in the transcript and answered with the 1–9 keys; pending ones wait in Needs attention20 | Yes: Answered in each agent’s own terminal prompt; Solo shows a heuristic waiting-for-permission state322 |
| MCP servers What each app does with MCP | Partly: Read-only list of MCP servers from Claude Code, Codex, Pi, Pool and Glue config files2023 | Yes: Is an MCP server: 40+ tools let agents spawn agents, read their output, and share todos and scratchpads24213 |
| Working in parallel | ||
| Isolation per session | Yes: The project folder, or a git worktree on its own branch per session20 | No: Creates none; agents run in their project’s folder, which can be a worktree or clone you linked25263 |
| Setup scripts and dev servers | No: A worktree is a plain git checkout; Splash runs no setup scripts or dev servers2027 | Yes: A committable solo.yml defines dev commands, with auto-start, restart on unexpected exit or file change, and env vars2829 |
| Terminal | Yes: A terminal in the session folder20 | Yes: Agents, commands and shells all run in the same built-in terminal emulator, with scrollback, mouse support and the Kitty keyboard protocol3031 |
| What needs you | Yes: One queue for permission requests, connection failures and finished turns, kept across restarts2032 | Yes: Heuristic agent states, unread markers, badges and notifications; a finished turn is flagged if the agent sends a BEL or OSC notification22333 |
| Review and shipping | ||
| Review changes | Yes: Latest response, failed tools and every changed file as a diff, with a box to send feedback20 | No: No diff or review UI; its workflow docs suggest a read-only reviewer agent for the exact diff2534 |
| Create pull requests | No: Shows the PR for a session’s branch and starts worktrees from PR heads; does not create PRs2035 | No: Not offered; the workflow docs have an agent commit or push when you ask2534 |
| GitHub | Yes: Issues, pull requests and Actions runs across repositories, through the gh CLI2035 | No: No native Git UI, and no GitHub integration is documented525 |
| Issue trackers | Partly: GitHub (github.com), through the gh CLI; no Linear or Jira2035 | No: Linear isn’t offered and no other tracker is documented; Solo has its own todos with dependencies and blockers253 |
| Where it runs | ||
| Cloud execution | No: Agents run as child processes on your computer, or on your own server with splash-server14 | No: None; agents and commands run as local processes on your computer3 |
| Remote access | Yes: splash-server runs on the machine with your code; you use it in a browser over an SSH tunnel. Single user.4 | No: No remote-host or headless sessions; the FAQ suggests SSH or tmux, and the HTTP API listens on 127.0.0.1336 |
| WSL on Windows | Partly: Run splash-server inside WSL and use it from a browser; WSL counts as a separate Linux host374 | Yes: Per project: the Windows host or a chosen WSL distribution; an agent installed in both shows up as two launch options387 |
| Auto-update | No: Download new versions from GitHub Releases; the app does not update itself1239 | Yes: Built-in updater that checks automatically; each update is signed and verified before it installs, and every plan gets updates133 |
| History and search | ||
| Existing agent history | Yes: Browse, preview and import conversations agents list over ACP, including ones started outside Splash2032 | Partly: Keeps resume IDs, not copies of conversations; five CLIs’ own pickers can open other conversations. Importing isn’t documented40 |
| Search transcripts | Yes: Search titles, folders and saved transcript text, archived sessions included20 | Partly: A find bar for one process’s scrollback; output isn’t kept across restarts and cross-session search isn’t documented4142 |
Splash speaks the Agent Client Protocol to each agent over stdio and draws the transcript itself: messages, tool calls, diffs and permission requests. Solo runs each agent’s installed CLI in a PTY terminal and shows that CLI’s own interface, leaving its models, permissions and configuration as they are. Solo’s docs don’t mention ACP.12317
Solo’s MCP server lets one agent spawn another, including one from a different vendor, wait for it and collect its output, with shared todos, scratchpads, timers and locks for coordination. In Splash, each session runs one agent in its project folder or worktree, and the prompts come from you.324120
Solo supervises a project’s dev servers, queues and watchers from a committable solo.yml, and can restart them when they exit unexpectedly or watched files change; it creates no isolated workspaces and shows no diffs. Splash gives each session its folder or a git worktree on its own branch, with diffs, review and a GitHub view, and runs no dev servers.32829252027
Splash is free and MIT-licensed open source. Solo is proprietary. Its Free plan covers 4 projects and 20 processes, agents included; Pro costs $99 a year, removes both limits and checks its license key with soloterm.com. Team seats cost $99 down to $69 each per year.9111031719
Splash ships for macOS, Windows and Ubuntu, and splash-server can run on another machine that you use from a browser over an SSH tunnel. Solo ships for macOS and Windows, with Linux listed as coming soon. It runs locally, can run a project inside WSL on Windows, and its FAQ suggests SSH or tmux for remote work.1248383
Facts about Solo come from its public website, documentation and repositories as they read on 9 October 2026; we haven't confirmed each one by running Solo. 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.