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 Atlas are desktop apps that run coding agents over the Agent Client Protocol. Atlas, in alpha, adds a built-in agent, can record agent sessions and link them to the commits they produced, and shares them with a team through a synced organization. Splash has no accounts and can give each session its own 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.computerAtlas
An alpha desktop app that drives Claude Code, Codex and other ACP registry agents plus its own Atlas Agent, ties recorded sessions to the commits they produced, and shares them with a team.3456
tryatlas.cc| Splash | Atlas | |
|---|---|---|
| The basics | ||
| What it is | Desktop app, plus a headless server you open in a browser17 | Desktop app for coding agents that can record sessions and link them to commits; a team web app runs no agents859 |
| Release status | v0.2.1, early development110 | Alpha: v0.3.4 (‘Atlas Teams Early’, 27 September 2026), with releases since May 2026; 0.4.0 is in development31112 |
| License | Open source (MIT)13 | Open source (Apache 2.0); Atlas Agent is a hard fork of openai/codex that doesn’t follow upstream14415 |
| Price | Free16 | Free during the alpha with your own keys; Atlas Agent use is billed to your organization under a plan Atlas grants, with no published prices31718 |
| Platforms | macOS 14+ (Apple silicon and Intel), Windows 11 x64, Ubuntu 24.04 x6419 | macOS 13+ on Apple silicon and Intel (install docs say 11+), Windows 10+ x64; Linux x86-64 packages the README calls untested3204 |
| Built with | Rust, with a Svelte 5 frontend in a webview, built on the Elyra framework21 | Tauri v2: a React 19 frontend and a Rust backend that runs agent sessions and the terminal8 |
| Agents | ||
| Agents | Ships launch commands for 20 agents, including Claude Code, Codex, Copilot, Gemini, Goose, OpenCode2223 | Built-in Atlas Agent; Claude Code, Codex, Cursor, OpenCode, Kilo Code and other ACP registry agents with an npx or binary build342425 |
| How it runs agents | Agent Client Protocol over stdio, natively or through a pinned adapter for the vendor’s CLI222 | External agents as ACP subprocesses over piped stdio; Atlas Agent runs in process on a hard fork of Codex42615 |
| 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 | External agents use your own subscriptions or API keys; Atlas Agent uses your Atlas account, with usage billed to your organization172718 |
| Account required | Splash has no accounts; splash-server asks for a token it keeps in its data folder287 | Not for local use; Google or GitHub sign-in unlocks Atlas Agent, team features, Cloud capture and the web app295 |
| 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 attention30 | Yes: Chat shows each agent’s own permission choices; Atlas Agent has Ask, Accept edits, Plan and Bypass modes, sandboxed except Bypass3118 |
| Skills and MCP servers | Partly: Settings shows each agent’s skills and MCP servers, read-only3032 | Yes: Links global or per-project skills into Atlas Agent, Claude Code and Codex and installs packs from skills.sh; offers agents its own memory server over MCP3334 |
| Working in parallel | ||
| Isolation per session | Yes: The project folder, or a git worktree on its own branch per session30 | No: None documented: all agents share the open project folder. Per-run working copies come with Shared threads, in progress535 |
| Terminal | Yes: A terminal in the session folder30 | Yes: Block terminal pairing each command with its output, exit status and duration, in tabs and split panes; blocks need zsh364 |
| What needs you | Yes: One queue for permission requests, connection failures and finished turns, kept across restarts3037 | Partly: The homepage describes a cross-session Inbox of permission prompts and finished streams that the docs don’t cover; notifications are unreleased 0.4.0312 |
| Agents handing off work Passing context or work between agents | No: Each session is one agent in one folder; sessions don’t hand work to each other130 | Partly: Agents with HTTP MCP support share an on-device memory per repository; handing a chat to another agent is unreleased 0.4.038342412 |
| Team collaboration Several people on one project | No: splash-server is a personal, single-user service, not a multi-user deployment7 | Yes: With a synced organization: a shared session timeline, comments, team chat, calls and Cloud capture529 |
| Built-in browser | No: No built-in browser; the workbench holds git changes, a file tree, diff and file tabs, and a terminal30 | Yes: A browser tab in a native webview that keeps logins and cookies, with a reader mode43 |
| Review and shipping | ||
| Review changes | Yes: Latest response, failed tools and every changed file as a diff, with a box to send feedback30 | Yes: Each turn lists changed files and opens its diff; Atlas Agent has /review. Line comments come with Shared threads, in progress311835 |
| Sessions linked to commits Which agent session produced a commit | No: No commit links; a session keeps its transcript, and archiving a worktree session keeps its splash/… branch30 | Yes: With capture on, commits made in any tool are tied to the agent sessions behind them; links follow rebases, and a squash orphans them639 |
| Files and diffs | Partly: File tree, git changes and diff tabs; files open read-only, with no editor3040 | Yes: An editor with tabs and splits that also shows PDFs, images and media; inline or side-by-side diffs4139 |
| Create pull requests | No: Shows the PR for a session’s branch and starts worktrees from PR heads; does not create PRs3042 | No: Never opens PRs or pushes by itself; you stage, commit, push and publish branches from its git panel4339 |
| GitHub | Yes: Issues, pull requests and Actions runs across repositories, through the gh CLI3042 | Partly: A GitHub tab searches public repositories and shallow-clones them as reference; PR, issue and CI views aren’t documented39 |
| Issue trackers | Partly: GitHub (github.com), through the gh CLI; no Linear or Jira3042 | No: None yet: Atlas’s own Issues feature is roadmapped, and importing knowledge from Jira and Confluence is being explored443 |
| Where it runs | ||
| Cloud execution | No: Agents run as child processes on your computer, or on your own server with splash-server17 | No: None; sessions run on team members’ own computers. Cloud machines for agents are roadmapped44 |
| Remote access | Yes: splash-server runs on the machine with your code; you use it in a browser over an SSH tunnel. Single user.7 | No: No SSH or remote-host mode is documented, and the web app and in-progress mobile app run no agents. Shared threads (in progress) can send a prompt to a teammate’s desktop agent94535 |
| Auto-update | No: Download new versions from GitHub Releases; the app does not update itself1946 | Yes: Downloads updates and asks to restart on macOS and Windows; on Linux it reports a new version for your package manager to install20 |
| History and search | ||
| Existing agent history Sessions started outside the app | Yes: Browse, preview and import conversations agents list over ACP, including ones started outside Splash3037 | Yes: Backfills Claude Code transcripts on disk once capture is on, and imports sessions from agents that can list them4316 |
| Search transcripts | Yes: Search titles, folders and saved transcript text, archived sessions included30 | Partly: Desktop: session titles, projects, agents, models and branches, plus ⌘F within a session. Web app: prompts, responses and tool calls too3147 |
Both use the Agent Client Protocol. Atlas installs external agents from the ACP registry as npx packages or platform binaries, and ships Atlas Agent, which runs in process on a hard fork of OpenAI’s Codex and is billed to an organization. Splash runs each agent’s own CLI with your login, natively or through a pinned adapter.254151822232
In Atlas all agents share the open project folder on a team member’s computer; per-run working copies come with Shared threads (in progress), and cloud agents are roadmapped. Splash runs each session in the project folder or its own git worktree on a splash/… branch, on your computer or under splash-server on a machine you reach over SSH.53544307
Atlas is Apache 2.0 licensed, free in the alpha and usable signed out. Google or GitHub sign-in with a synced organization adds a shared session timeline, comments, team chat and Atlas Agent, whose usage is billed to the organization under a plan Atlas grants; no prices are published. Splash is MIT-licensed and free, has no accounts, and splash-server serves one user.143295171316287
Atlas keeps agent work on the record: with capture on, checkpoints tie each commit to the agent session behind it, agents that support HTTP MCP share an on-device memory per repository, and an editor, block terminal and git client sit alongside. Splash centers on the conversations: a Needs attention queue, a review screen, transcript search and a GitHub view of issues, PRs and Actions.638344136393042
Atlas is an alpha Tauri app for macOS and Windows x64, with Linux packages the README calls untested. Several features its docs describe, including notifications and handing a chat to another agent, are listed under unreleased 0.4.0. Splash, in early development, builds for macOS 14+, Windows 11 x64 and Ubuntu 24.04 x64.3841248119
Facts about Atlas come from its public website, documentation and repositories as they read on 10 October 2026; we haven't confirmed each one by running Atlas. 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.