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 Agent Teams AI are free desktop apps for running several coding agents at once. In Agent Teams AI, a lead agent turns your goal into kanban tasks for teammate agents that message and review each other. In Splash, each session is one agent, driven over the Agent Client Protocol 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.computer777genius
A free, AGPL-licensed desktop app in which a lead agent splits your goal into tasks on a kanban board, and teammate agents work them in parallel, messaging and reviewing each other while you oversee.345
agentteams.live| Splash | Agent Teams AI | |
|---|---|---|
| The basics | ||
| What it is | Desktop app, plus a headless server you open in a browser16 | Electron desktop app where a lead agent turns your goal into board tasks for teammates; a web dashboard is in development347 |
| Release status | v0.2.1, early development18 | v2.17.10 of 9 October 2026, the 32nd release counting from 1.0.0 in March 2026; the docs’ Release Notes page names v1.2.0 as current93101112 |
| License | Open source (MIT)13 | Open source (AGPL-3.0) with a commercial-sublicensing CLA; the bundled runtime that starts agents is closed source, shipped as binaries571415 |
| Price | Free16 | Free, with no paid tier; one free model works without a login, and other model use is billed by its provider31718 |
| Platforms | macOS 14+ (Apple silicon and Intel), Windows 11 x64, Ubuntu 24.04 x6419 | macOS 13+ (Apple silicon and Intel), Windows x64 and ARM64, Linux x64 (AppImage, .deb, .rpm, .pacman)20219 |
| Agents | ||
| Agents | Ships launch commands for 20 agents, including Claude Code, Codex, Copilot, Gemini, Goose, OpenCode2223 | Runtimes for Claude Code, Codex and OpenCode; Cursor, SuperGrok, GitHub Copilot, Kiro, Z.AI, MiniMax and local models connect through OpenCode3172425262728 |
| How it runs agents | Agent Client Protocol over stdio, natively or through a pinned adapter for the vendor’s CLI222 | A bundled runtime binary launches agents as app-managed processes; Codex runs through its SDK, most other providers through opencode serve297303117 |
| Agent sign-in Who pays for the model | You install and sign in to each agent’s CLI yourself; Splash runs it with that login23 | Each runtime’s CLI on your PATH, with its login or an API key; guided setup connects Copilot, Cursor and Kimi plans322026 |
| Account required | Splash has no accounts; splash-server asks for a token it keeps in its data folder336 | No Agent Teams account or signup; providers beyond the free model need their own login or API key320 |
| Model and mode pickers | Yes: Model, mode and effort pickers when the agent offers them34 | Yes: Provider, model and effort level per teammate, with Fast mode and Limit context options; one team can mix providers24 |
| 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 attention34 | Yes: Chosen per launch: auto-approve tools, preselected unless you last switched it off, or confirm each supported action, notified per request73512 |
| MCP servers | Partly: Read-only list of MCP servers from Claude Code, Codex, Pi, Pool and Glue config files3436 | Yes: A built-in agent-teams server for coordination, plus your own from ~/.claude.json, .mcp.json or an in-app registry with diagnostics37 |
| Working in parallel | ||
| Isolation per session | Yes: The project folder, or a git worktree on its own branch per session34 | Partly: Shared project checkout by default; an optional git worktree per teammate, which several docs pages restrict to OpenCode members38739 |
| Setup scripts and dev servers | No: A worktree is a plain git checkout; Splash runs no setup scripts or dev servers3440 | Partly: No setup scripts documented; dev servers that agents start are registered and listed with their URLs, ready to open or stop41377 |
| Terminal | Yes: A terminal in the session folder34 | Yes: A terminal workspace per team and project, with team and local shell tabs, saved history and autocomplete; agents run outside it37 |
| What needs you | Yes: One queue for permission requests, connection failures and finished turns, kept across restarts3442 | Yes: A task card gets a distinct badge while its agent waits for your input; agents can ask questions with answer buttons712 |
| Notifications | Yes: Notifies when a background session needs permission or finishes a turn; can be turned off4344 | Yes: Configurable alerts for finished tasks, agents waiting on you, new comments, errors and monthly token or cost budgets73 |
| 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 other134 | Yes: A lead splits your goal into tasks for up to 30 teammates, who message and review each other; linked teams can message each other too34541 |
| Review and shipping | ||
| Review changes | Yes: Latest response, failed tools and every changed file as a diff, with a box to send feedback34 | Yes: Per-task Changes view: accept or reject files or single hunks, edit, undo, comment inline; the lead reviews by default346 |
| Files and diffs | Partly: File tree, git changes and diff tabs; files open read-only, with no editor3447 | Yes: A project file editor with Git support, which since v2.17.10 also previews PDF, Word, Excel and PowerPoint files79 |
| GitHub | Yes: Issues, pull requests and Actions runs across repositories, through the gh CLI3448 | No: No pull request, CI or GitHub account features documented; you merge worktree output after review, and can add an issue tracker as an MCP server3837 |
| Where it runs | ||
| Cloud execution | No: Agents run as child processes on your computer, or on your own server with splash-server16 | No: Teams run on your own computer; 24/7 cloud teams are a roadmap item marked in progress749 |
| 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: Views Claude Code sessions on another machine over SSH; remote team launches aren’t documented. A web dashboard without login suits trusted networks50517 |
| Auto-update | No: Download new versions from GitHub Releases; the app does not update itself1952 | Yes: Packaged desktop builds check GitHub Releases at launch and while running, then offer to install updates; the Docker or Node dashboard disables the updater2050 |
| 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 Splash3442 | Partly: Finds Claude Code projects in ~/.claude and reads their session files; resuming an outside session as a teammate isn’t documented749 |
| Search transcripts | Yes: Search titles, folders and saved transcript text, archived sessions included34 | Yes: Transcript search, 3× faster since v1.1.0; the command palette searches conversations and across all projects1253 |
Agent Teams AI launches every agent through its bundled multimodel runtime, which a team launch starts with stream-json flags and a generated --mcp-config. Inside it, Codex runs through its SDK, and most other providers go through opencode serve, Cursor via an ACP bridge. Agents coordinate through the app’s MCP tools. Splash speaks the Agent Client Protocol with every agent, natively or through an adapter.2954303155255637222
In Agent Teams AI a lead agent turns your goal into kanban tasks that teammates pick up, move, discuss and send for review, while you comment, approve or message them; linked teams can message each other and be grouped into organizations. In Splash each session is one agent in one folder, and sessions don’t hand work to each other.34146134
Both are free and need no account. Agent Teams AI’s app is AGPL-3.0, with a CLA that lets its owner also license contributions commercially, while the multimodel runtime that launches agents is built from a private repository and published as binaries without a license file. Splash’s code is MIT-licensed.3571415131633
Both run agents on your own computer. Agent Teams AI builds for macOS 13+, Windows x64 and ARM64 and Linux x64, offers a web dashboard, in development and without built-in login, for trusted networks, and lists cloud teams as in progress. Splash builds for macOS 14+, Windows 11 x64 and Ubuntu 24.04 x64, or runs as splash-server, opened through an SSH tunnel.20971916
Agent Teams AI has a kanban board with review states, hunk-by-hunk review per task, a project editor, a terminal workspace per team, dev servers that agents register, and token and cost analytics with monthly budgets that can cap supported scheduled runs. Splash has a Needs attention queue, a review screen with a diff per changed file, a terminal per session, import of sessions agents started elsewhere, and a GitHub view.346741344248
Facts about Agent Teams AI come from its public website, documentation and repositories as they read on 10 October 2026; we haven't confirmed each one by running Agent Teams AI. 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.