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 ccgui, also called CC GUI, are open-source desktop apps for working with several AI coding agents. ccgui, a Tauri app, connects each of its built-in engines, among them Claude Code, Codex, Kimi, Grok and OpenCode, through an adapter written for that engine. Splash drives every agent over the Agent Client Protocol.
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.computerMossX
An open-source Tauri desktop app that runs Claude Code, Codex, Kimi, Grok, OpenCode and other AI coding CLIs in one window. A VS Code extension and a JetBrains plugin share the CC GUI name.34
docs.mossx.ai| Splash | ccgui | |
|---|---|---|
| The basics | ||
| What it is | Desktop app, plus a headless server you open in a browser15 | Desktop app that runs several AI coding CLIs in one window and can serve its UI to browsers on other devices36 |
| Release status | v0.2.1, early development17 | v1.1.2 (8 October 2026), the latest of 122 releases since February 2026, none of them marked as a prerelease8 |
| License | Open source (MIT)9 | The README and docs say MIT, but the repository has no LICENSE file and GitHub detects no license31011 |
| Price | Free12 | No price or paid plan is listed, and the download site says its open-source projects stay free; providers bill model usage1314 |
| Platforms | macOS 14+ (Apple silicon and Intel), Windows 11 x64, Ubuntu 24.04 x6415 | macOS (Apple silicon and Intel), Windows 10 or later x64 with WebView2, and Linux x64 as AppImage or .rpm16173 |
| Built with | Rust, with a Svelte 5 frontend in a webview, built on the Elyra framework18 | Tauri 2, with a Rust backend and a React 18 and TypeScript frontend36 |
| Agents | ||
| Agents | Ships launch commands for 20 agents, including Claude Code, Codex, Copilot, Gemini, Goose, OpenCode1920 | README lists 11 built-in engines, among them Claude Code, Codex, Kimi, Grok and OpenCode; docs cover seven. Users can’t add more3621 |
| How it runs agents | Agent Client Protocol over stdio, natively or through a pinned adapter for the vendor’s CLI192 | An adapter per CLI: stream-json for Claude Code, codex app-server, ACP for Kimi, Grok, Qoder and MiniMax, HTTP for OpenCode32223242526 |
| Agent sign-in Who pays for the model | You install and sign in to each agent’s CLI yourself; Splash runs it with that login20 | Reuses each CLI’s own login, or stores provider API keys with a base URL and model mapping; the provider bills usage1427 |
| Account required | Splash has no accounts; splash-server asks for a token it keeps in its data folder285 | No ccgui account is described; it needs at least one working AI runtime and a project folder2729 |
| Model and mode pickers | Yes: Model, mode and effort pickers when the agent offers them30 | Yes: Engine per session, model and thinking level per tab, and auto, manual, plan or bypass modes where the engine supports them331 |
| 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: Prompts offer allow, always allow or deny, and agent questions open as cards. Grok and Qoder have one mode, bypass; Pi and DeepSeek Harness have auto313 |
| MCP servers | Partly: Read-only list of MCP servers from Claude Code, Codex, Pi, Pool and Glue config files3032 | Partly: Lists configured MCP servers for Claude Code and Codex and turns them on or off; new servers are added in each runtime’s own config33 |
| Working in parallel | ||
| Isolation per session | Yes: The project folder, or a git worktree on its own branch per session30 | Yes: Sessions belong to a workspace; worktree sub-workspaces, from a new or existing branch or a GitHub PR, get their own sessions3435363738 |
| Setup scripts and dev servers | No: A worktree is a plain git checkout; Splash runs no setup scripts or dev servers3039 | Partly: Startup scripts saved per workspace run on demand in a terminal tab; no setup hook for new worktrees and no dev-server handling are documented384041 |
| Terminal | Yes: A terminal in the session folder30 | Yes: A PTY-backed terminal dock (xterm with WebGL) inside the app, one shell per tab334 |
| Built-in browser | No: No built-in browser; the workbench holds git changes, a file tree, diff and file tabs, and a terminal30 | Partly: Browser tabs show web pages in native webviews inside the app; the entry is a beta feature, off by default3842 |
| What needs you | Yes: One queue for permission requests, connection failures and finished turns, kept across restarts3043 | Partly: Permission prompts and question cards appear in each session, with optional system notifications; no queue across sessions is documented314445 |
| Review and shipping | ||
| Review changes | Yes: Latest response, failed tools and every changed file as a diff, with a box to send feedback30 | Yes: Git panel and tool-call diffs, and plans that wait for approval; line comments back to the agent aren’t documented4633147 |
| Files and diffs | Partly: File tree, git changes and diff tabs; files open read-only, with no editor3048 | Yes: A file tree with Git status colors and a CodeMirror editor with Markdown preview; the Git panel shows diffs334 |
| Create pull requests | No: Shows the PR for a session’s branch and starts worktrees from PR heads; does not create PRs3049 | No: The Git panel stages and commits, with AI-written commit messages; creating pull requests isn’t among its documented features3446 |
| GitHub | Yes: Issues, pull requests and Actions runs across repositories, through the gh CLI3049 | Partly: Starts a worktree from a PR number or URL; PR, issue and CI views aren’t documented355034 |
| 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.5 | Yes: Browser access over the LAN with a token, QR code and per-device approval, or beyond it through your own Cloudflare Worker3515253 |
| Mobile app | No: No mobile app; builds cover macOS, Windows, Ubuntu and a headless server15 | No: None published; the mobile client’s docs are still in preparation. Phones can open the desktop UI in a browser5451 |
| Auto-update | No: Download new versions from GitHub Releases; the app does not update itself1555 | Yes: A built-in updater gets new versions from GitHub Releases2756 |
| 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 Splash3043 | Not documented: Not documented; the README says it reads each CLI’s own session files, and the docs separate history by runtime357 |
| Search transcripts | Yes: Search titles, folders and saved transcript text, archived sessions included30 | Yes: One search box covers files, sessions, past messages, skills and commands34 |
| Fork a conversation | Partly: Experimental: fork the current conversation when the agent supports it, not from an earlier message3043 | Partly: Claude Code and Codex fork and roll back where supported; DeepSeek Harness can fork; other engines don’t list it45 |
ccgui wires each built-in engine through its own adapter: stream-json for Claude Code and Antigravity, codex app-server for Codex, ACP for Kimi, Grok, Qoder and MiniMax Code, RPC for Pi and OMP, and local HTTP servers for OpenCode and DeepSeek Harness. Adding an engine takes a new build. Splash speaks the Agent Client Protocol with every agent, natively or through an adapter.3225823242559266021192
Both run agents as local processes. ccgui serves its UI to browsers on your network with a token and per-device approval on the desktop, and since v1.0.0 can relay it through a Cloudflare Worker in your own account. Splash can instead run as splash-server on the machine with your code, reached in a browser over an SSH tunnel.6351525315
ccgui lists no price, and you pay whichever model provider you configure. Its README and docs call it MIT-licensed, but the repository has no LICENSE file, and production builds load Baidu Tongji (百度统计) analytics a few seconds after launch, which the README and user docs don’t mention. Splash is free, MIT-licensed and has no accounts.131431011616212928
ccgui has a Git panel that stages and commits with AI-written messages, a file editor, startup scripts per workspace, split views, bundled skills, a plugin SDK with a marketplace and, as a beta, browser tabs. Splash has a Needs attention queue across sessions, review with a feedback box, importing agent history over ACP, and a GitHub view of issues, PRs and Actions runs.4633840335342304349
Facts about ccgui come from its public website, documentation and repositories as they read on 10 October 2026; we haven't confirmed each one by running ccgui. 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.