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 MonoCode are both open-source desktop apps that run the coding agent CLIs you already have, with git worktrees for parallel sessions. MonoCode, built on Tauri, has a separate adapter for each of its eleven agents, six of them over the Agent Client Protocol (ACP); Splash drives every agent over ACP.
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.computerNick (hardbeat920)
An open-source Tauri desktop app that runs eleven installed coding agent CLIs, with worktrees, an Inbox for issues and pull requests, automations, and experimental Monos and remote hosts.34567
usemono.dev| Splash | MonoCode | |
|---|---|---|
| The basics | ||
| What it is | Desktop app, plus a headless server you open in a browser18 | Tauri desktop app, Rust with a React frontend, for the agent CLIs on your machine; an experimental host service runs agents elsewhere95107 |
| Release status | v0.2.1, early development111 | v0.11.0 of 9 October 2026; 70 releases since 0.1.0 on 20 August, and the README calls it still early126133 |
| License | Open source (MIT)14 | Open source (MIT); provider names and logos remain their owners’ trademarks43 |
| Price | Free15 | No price, paid tier or checkout is listed, and MonoCode sells no tokens; models bill through your own agent plans or keys9316 |
| Platforms | macOS 14+ (Apple silicon and Intel), Windows 11 x64, Ubuntu 24.04 x6417 | macOS (Apple silicon and Intel), Windows x64, Linux x64 (.deb, AppImage, .rpm); the remote host also comes in arm64123187 |
| Account required | Splash has no accounts; splash-server asks for a token it keeps in its data folder198 | No MonoCode account is mentioned; the stated prerequisite is one supported agent CLI, installed and signed in316 |
| Agents | ||
| Agents | Ships launch commands for 20 agents, including Claude Code, Codex, Copilot, Gemini, Goose, OpenCode2021 | Claude Code, Codex, Cursor, Grok Build, OpenCode, Antigravity (macOS and Linux), Pi, omp, fx, Hermes Agent and Devin; adding others isn’t documented93622 |
| How it runs agents | Agent Client Protocol over stdio, natively or through a pinned adapter for the vendor’s CLI202 | Each CLI as a child process: ACP for six agents, plus Claude Code stream-json, Codex app-server, OpenCode’s HTTP server and Pi/omp RPC23242526272867 |
| Model and mode pickers | Yes: Model, mode and effort pickers when the agent offers them29 | Yes: Model and effort pickers; hand a finished turn to another provider, or ask one for a second opinion, in a split pane beside it6 |
| Agent sign-in | You install and sign in to each agent’s CLI yourself; Splash runs it with that login21 | Reuses each CLI’s login and can open browser sign-in for five agents; Claude Code and Codex take several named accounts3166 |
| 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 | Yes: Approval and question prompts in the transcript; access modes such as Supervised and Full Access; with supported agents, /plan waits for you to approve a plan6 |
| MCP servers | Partly: Read-only list of MCP servers from Claude Code, Codex, Pi, Pool and Glue config files2930 | Yes: Settings finds, adds and removes servers for Claude Code, Claude Desktop, Codex, Cursor and OpenCode; /mcp picks which ones to use6 |
| Working in parallel | ||
| Isolation per session | Yes: The project folder, or a git worktree on its own branch per session29 | Yes: Picked per session: your current checkout, a worktree you already have, or a new worktree and branch made on its first turn631 |
| Terminal | Yes: A terminal in the session folder29 | Yes: Built-in terminals belong to the project, dock to any edge and start in the current session’s worktree; remote projects have none67 |
| What needs you | Yes: One queue for permission requests, connection failures and finished turns, kept across restarts2932 | Yes: A sidebar status filter that includes needs approval; pending prompts stay visible in the transcript, and sessions can carry reminders6 |
| Notifications | Yes: Notifies when a background session needs permission or finishes a turn; can be turned off3334 | Yes: Optional system notifications when a turn ends or an agent waits in a hidden session; sounds, banners and mutes set per project6 |
| Agents handing off work One agent launching or messaging another | No: Each session is one agent in one folder; sessions don’t hand work to each other129 | Yes: A lead agent directs up to four workers; with /operator, or as a Mono, an agent can start and message sessions6353 |
| Scheduled tasks Agents that start without a prompt from you | No: No scheduler; an agent starts when you create, continue or prompt a session36 | Yes: Automations on hourly-to-weekly schedules or tracker events from GitHub, GitLab, Linear, Jira or Azure DevOps; experimental Monos repeat Habits while the app is open6373 |
| Review and shipping | ||
| Review changes | Yes: Latest response, failed tools and every changed file as a diff, with a box to send feedback29 | Yes: Staged and unstaged diffs with line-by-line comments sent to the agent as one prompt; session checkpoints can be undone6 |
| Files and diffs | Partly: File tree, git changes and diff tabs; files open read-only, with no editor2938 | Yes: A file tree and an editor that shows diffs, with full-text search across the project6 |
| Create pull requests | No: Shows the PR for a session’s branch and starts worktrees from PR heads; does not create PRs2939 | Yes: Commit, push, pull and switch branches, then open a PR through gh; merge, close, reopen or change draft state in the app67 |
| GitHub | Yes: Issues, pull requests and Actions runs across repositories, through the gh CLI2939 | Yes: Through your gh login: PR checks in the Inbox, failed checks sent to an agent, sessions linked to issues and PRs6 |
| Issue trackers | Partly: GitHub (github.com), through the gh CLI; no Linear or Jira2939 | Yes: An Inbox for GitHub, GitLab, Linear, Jira Cloud and Azure DevOps items: read, comment, discuss with an agent or start a session637 |
| 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.8 | Partly: Experimental: over SSH, installs a host service on a Windows, Linux or macOS machine that stays awake; sessions survive a dropped tunnel37 |
| Auto-update | No: Download new versions from GitHub Releases; the app does not update itself1740 | Yes: Built-in updater with stable and beta feeds; the AppImage updates itself, while .deb and .rpm need the newer package installed18416 |
| 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 Splash2932 | Not documented: Not documented; MonoCode keeps its own sessions per project, and several agents resume the ones it started6 |
| Search transcripts | Yes: Search titles, folders and saved transcript text, archived sessions included29 | Yes: Global search across files, projects and earlier conversations, including message text; Find within an open transcript6 |
MonoCode has its own adapter for each of its eleven agents: ACP for six, plus Claude Code’s stream-json mode, Codex’s app-server, OpenCode’s HTTP server and Pi and omp RPC. No documented route adds others, and new adapters are paused for now. Splash speaks the Agent Client Protocol to every agent, natively or through a pinned adapter.24252627286722202
Both start agents as child processes on your computer, and neither documents a hosted service. MonoCode’s experimental remote mode installs a host service over SSH on a Windows, Linux or macOS machine that stays awake; terminals, automations and orchestration don’t work there yet. Splash can run as splash-server on the machine with your code, opened in a browser over SSH.23718
Both are MIT-licensed. Splash is free and has no accounts; MonoCode lists no price or paid tier, and its docs mention no MonoCode account. MonoCode ships for macOS (Apple silicon and Intel), Windows x64 and Linux x64, with arm64 builds of its remote host; Splash builds for macOS 14+, Windows 11 x64 and Ubuntu 24.04 x64.4931214151917
MonoCode extends into the work around a session: an Inbox for GitHub, GitLab, Linear, Jira and Azure DevOps, PR creation, scheduled and event-driven automations, a lead agent with up to four workers, and experimental Monos, persistent agents with memory. Splash centers on the sessions: a Needs attention queue, a GitHub view across repositories and importing conversations agents started elsewhere.63293239
Facts about MonoCode come from its public website, documentation and repositories as they read on 10 October 2026; we haven't confirmed each one by running MonoCode. 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.