splash

SplashCompareCodeg

Splash and Codeg, compared.

Splash and Codeg are open-source apps that run several coding agents at once over the Agent Client Protocol. Codeg runs as a desktop app, in a Docker container or as a self-hosted server, with mobile clients and a to-do queue that gives each task a worktree. Splash is a desktop app and single-user server; each session runs in its folder or a worktree.

Checked 9 October 202647 sourcesNot affiliated with SpaceRing

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.computer

Codeg

SpaceRing

A multi-agent coding workspace that runs as a desktop app, in a Docker container or as a self-hosted server, with mobile clients. It drives 15 built-in agents through the Agent Client Protocol and queues to-do tasks in worktrees.34567

docs.codeg.app

Side by side

SplashCodeg
The basics
What it is Desktop app, plus a headless server you open in a browser18 Desktop app, self-hosted server used in a browser, or Docker container; iOS and Android apps connect to it59
Release status v0.2.1, early development110 v0.34.0, released 7 October 2026; the iOS and Android clients are still in testing94
License Open source (MIT)11 Open source (Apache-2.0); the iOS and Android clients are open source too121314
Price Free15 Free, with no paid tier documented; sponsors support development. The iOS client is free on the App Store1316
Built with Rust, with a Svelte 5 frontend in a webview, built on the Elyra framework17 A Rust core and a Next.js/React interface, which the desktop app wraps in a Tauri 2 shell1418
Agents
Agents Ships launch commands for 20 agents, including Claude Code, Codex, Copilot, Gemini, Goose, OpenCode1920 15 built in, including Claude Code, Codex, Gemini CLI, OpenCode, Cursor and Grok; other ACP agents can be added65
How it runs agents Agent Client Protocol over stdio, natively or through a pinned adapter for the vendor’s CLI192 Agent Client Protocol, each agent a subprocess; Claude Code, Codex and DeepSeek Harness go through ACP adapters, and the source code launches Pi through one too14621
Agent sign-in Installing agents and logging them in You install and sign in to each agent’s CLI yourself; Splash runs it with that login20 Installs and pins the built-in agents; each agent signs in through its vendor account, an API key from its provider or a custom endpoint622
Permission requests Yes: Shown in the transcript and answered with the 1–9 keys; pending ones wait in Needs attention23 Yes: A card above the composer offers the agent’s own choices; there is no global auto-approve switch24
MCP servers Partly: Read-only list of MCP servers from Claude Code, Codex, Pi, Pool and Glue config files2325 Yes: Scans installed MCP servers, offers a registry Market, and writes a server into the configs of the agents you pick265
Agents handing off work One agent handing a subtask to another No: Each session is one agent in one folder; sessions don’t hand work to each other123 Yes: Off by default; when on, a lead agent hands subtasks to other agent types. OpenClaw and Pi can’t lead272829
Working in parallel
Isolation per session Yes: The project folder, or a git worktree on its own branch per session23 Yes: Each to-do task gets a worktree on its own branch; a conversation uses your working tree or a worktree you create730
Queued and scheduled runs Task queues and timed runs No: An agent starts when you create, continue or prompt a session; there is no task queue or scheduler17 Yes: To-dos queue under a per-folder concurrency limit (default 2); Automations run a saved prompt by cron schedule or by hand731
Setup scripts and dev servers No: A worktree is a plain git checkout; Splash runs no setup scripts or dev servers2332 Yes: A per-folder init command runs in each new task worktree, and a status-bar launcher starts dev servers and other commands724
Built-in browser A browser agents can see and use No: No built-in browser; the workbench holds git changes, a file tree, diff and file tabs, and a terminal23 Yes: In the desktop app; agents can read and drive its pages once you switch on their browser tools533
Terminal Yes: A terminal in the session folder23 Yes: Terminals in the working folder (⌘J), in tabs; each is a real shell24
What needs you Yes: One queue for permission requests, connection failures and finished turns, kept across restarts2334 Yes: Each conversation has a live status dot; a badge counts to-dos that await input, need review or failed247
Notifications Yes: Notifies when a background session needs permission or finishes a turn; can be turned off3536 Yes: OS notifications for six event types, each with its own switch and on by default; chat channels and webhooks can relay agent events3738
Review and shipping
Review changes Yes: Latest response, failed tools and every changed file as a diff, with a box to send feedback23 Yes: Read-only diffs of each reply’s edits, a built-in git client, and a review stage where to-dos are merged, reworked or abandoned24307
Files and diffs Partly: File tree, git changes and diff tabs; files open read-only, with no editor2339 Yes: Files open in an editor that saves automatically; diffs stay read-only, apart from a three-pane merge-conflict editor2430
Create pull requests No: Shows the PR for a session’s branch and starts worktrees from PR heads; does not create PRs2340 Yes: Tasks from issues can push their branch and open a PR; tasks from PRs push back to that PR’s branch41
GitHub Yes: Issues, pull requests and Actions runs across repositories, through the gh CLI2340 Yes: A per-folder Repository panel for issues and PRs, with CI checks, comments, close, reopen and merge; items become to-dos41
Issue trackers Partly: GitHub (github.com), through the gh CLI; no Linear or Jira2340 Partly: GitHub, GitLab, Gitea and Forgejo, self-hosted instances included; Linear and Jira aren’t documented41
Where it runs
Platforms macOS 14+ (Apple silicon and Intel), Windows 11 x64, Ubuntu 24.04 x6442 macOS (Apple silicon, Intel), Windows 10/11 x64 and Arm64, Linux x64 and arm64; server builds and a multi-arch Docker image943
Mobile app No: No mobile app; builds cover macOS, Windows, Ubuntu and a headless server42 Partly: iOS/iPadOS 26+ and Android 12+ clients, still in testing, that connect to your own Codeg host916
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 Yes: No hosted cloud; use it in a browser through the desktop Web Service or a self-hosted codeg-server, with a token334443
Auto-update No: Download new versions from GitHub Releases; the app does not update itself4245 Yes: The desktop app updates itself; codeg-server does too, except on Windows, where you rerun the installer1443
History and search
Existing agent history Yes: Browse, preview and import conversations agents list over ACP, including ones started outside Splash2334 Yes: Imports sessions the 15 built-in agents saved on disk, including ones begun outside Codeg, and resumes them with that agent46
Search Across saved conversations Yes: Search titles, folders and saved transcript text, archived sessions included23 Yes: ⌘K searches conversations from every agent, imported ones included, and files; matching on message text isn’t documented4624
Fork a conversation Partly: Experimental: fork the current conversation when the agent supports it, not from an earlier message2334 Partly: Forks from a completed reply and lets you steer a running turn, where the agent supports it5

Where they differ

Who runs file edits and commands

Codeg serves an agent’s ACP file and terminal requests in its own process, unless a per-agent switch hands them back, and gives most agents its codeg-mcp companion, which carries delegation and other Codeg tools. Splash offers agents no file-system or terminal capabilities: each agent changes files on its own, and Splash reads the results from git and a folder watcher.47142917

To-dos and sessions

Codeg gives each to-do a worktree and branch, an optional init command, a review step and an agent that does the merge, under a per-folder concurrency limit; its conversations run in your working tree or in a worktree you create. A Splash session is one agent in its project folder or its own worktree on a splash/… branch, and archiving it deletes the worktree but keeps the branch.730123

Where each one runs

Codeg ships desktop builds for macOS and for Windows and Linux on x64 and Arm, plus a server binary, a multi-arch Docker image, iOS and Android clients still in testing, and Telegram, Lark and WeChat channels. Splash ships desktop builds for macOS, Windows 11 x64 and Ubuntu 24.04 x64, plus a single-user server that listens on loopback for an SSH tunnel.94338428

Setting up agents

Codeg installs and pins versions of its built-in agents, most of them npm packages it starts with npx, and writes MCP servers into the configs of the agents you choose. Splash installs no agents: you install and sign in to each CLI, npx fetches adapters on first run, and Splash lists the MCP servers in the Claude Code, Codex, Pi, Pool and Glue config files, read-only.626202325

Which one fits

Splash may suit you if

  • You want each agent session in its project folder or its own worktree, with permission requests, failures and finished turns in one queue.
  • You want to find conversations agents expose over ACP, import them, and search their saved transcript text.
  • You triage GitHub issues, pull requests and Actions runs across many repositories next to your sessions.
  • You run agents on a remote machine and use them from a browser over an SSH tunnel.

Codeg may suit you if

  • You want to queue tasks that each get a worktree, an optional setup command and a review step before an agent merges them.
  • You want a lead agent to pass parts of a job to other kinds of agents within one conversation.
  • You want to follow sessions from iOS, Android, Telegram, Lark or WeChat, or run the server in Docker.
  • You work with GitLab, Gitea or Forgejo as well as GitHub and want tasks to open pull requests.

Sources

Facts about Codeg come from its public website, documentation and repositories as they read on 9 October 2026; we haven't confirmed each one by running Codeg. 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.

  1. 1 Splash README Splash on GitHub · github.com · checked 2026-10-09
  2. 2 Agent Client Protocol agentclientprotocol.com · agentclientprotocol.com · checked 2026-10-09
  3. 3 Open source SpaceRing · spacering.net · checked 2026-10-09
  4. 4 codeg v0.34.0 spacering-net/codeg on GitHub · github.com · checked 2026-10-09
  5. 5 Codeg README spacering-net/codeg on GitHub · github.com · checked 2026-10-09
  6. 6 Supported Agents Codeg · docs.codeg.app · checked 2026-10-09
  7. 7 To-dos Codeg · docs.codeg.app · checked 2026-10-09
  8. 8 Splash README: Run as a web app over SSH Splash on GitHub · github.com · checked 2026-10-09
  9. 9 Download and install Codeg · docs.codeg.app · checked 2026-10-09
  10. 10 Splash releases Splash on GitHub · github.com · checked 2026-10-09
  11. 11 LICENSE Splash on GitHub · github.com · checked 2026-10-09
  12. 12 LICENSE spacering-net/codeg on GitHub · github.com · checked 2026-10-09
  13. 13 About Codeg · docs.codeg.app · checked 2026-10-09
  14. 14 Architecture Codeg · docs.codeg.app · checked 2026-10-09
  15. 15 Download Splash splash.computer · splash.computer · checked 2026-10-09
  16. 16 Codeg Client Apple App Store · apps.apple.com · checked 2026-10-09
  17. 17 Splash README: How it works Splash on GitHub · github.com · checked 2026-10-09
  18. 18 src-tauri/Cargo.toml spacering-net/codeg on GitHub · github.com · checked 2026-10-09
  19. 19 src/agents/registry.rs Splash on GitHub · github.com · checked 2026-10-09
  20. 20 Splash README: Agents Splash on GitHub · github.com · checked 2026-10-09
  21. 21 src-tauri/src/acp/registry.rs spacering-net/codeg on GitHub · github.com · checked 2026-10-09
  22. 22 Authentication & Models Codeg · docs.codeg.app · checked 2026-10-09
  23. 23 Splash README: Features Splash on GitHub · github.com · checked 2026-10-09
  24. 24 The Workspace Codeg · docs.codeg.app · checked 2026-10-09
  25. 25 src/agents/customize.rs Splash on GitHub · github.com · checked 2026-10-09
  26. 26 MCP Servers Codeg · docs.codeg.app · checked 2026-10-09
  27. 27 Introduction Codeg · docs.codeg.app · checked 2026-10-09
  28. 28 Collaboration Codeg · docs.codeg.app · checked 2026-10-09
  29. 29 Multi-Agent Collaboration Codeg · docs.codeg.app · checked 2026-10-09
  30. 30 Git & Worktrees Codeg · docs.codeg.app · checked 2026-10-09
  31. 31 Automations Codeg · docs.codeg.app · checked 2026-10-09
  32. 32 src/worktree.rs Splash on GitHub · github.com · checked 2026-10-09
  33. 33 Privacy & Security Codeg · docs.codeg.app · checked 2026-10-09
  34. 34 Splash README: Existing sessions and review Splash on GitHub · github.com · checked 2026-10-09
  35. 35 app/src/components/settings/General.svelte Splash on GitHub · github.com · checked 2026-10-09
  36. 36 app/src/lib/system.ts Splash on GitHub · github.com · checked 2026-10-09
  37. 37 General Codeg · docs.codeg.app · checked 2026-10-09
  38. 38 Chat Channels Codeg · docs.codeg.app · checked 2026-10-09
  39. 39 app/src/components/FileTab.svelte Splash on GitHub · github.com · checked 2026-10-09
  40. 40 Splash README: GitHub view Splash on GitHub · github.com · checked 2026-10-09
  41. 41 Repository Panel Codeg · docs.codeg.app · checked 2026-10-09
  42. 42 Splash README: Download the app Splash on GitHub · github.com · checked 2026-10-09
  43. 43 Deployment Codeg · docs.codeg.app · checked 2026-10-09
  44. 44 Web Service Codeg · docs.codeg.app · checked 2026-10-09
  45. 45 app/src/components/settings/About.svelte Splash on GitHub · github.com · checked 2026-10-09
  46. 46 Conversation Aggregation Codeg · docs.codeg.app · checked 2026-10-09
  47. 47 Working with Agents Codeg · docs.codeg.app · checked 2026-10-09