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 T3 Code both run several agents at once, each in a project folder or its own git worktree. T3 Code pairs a server that runs agents with desktop, web, iOS and Android apps, and uses each agent’s own interface. Splash is a desktop app, with an optional headless server you open in a browser, that speaks the Agent Client Protocol with every agent.
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.computerT3 Tools
An MIT-licensed control surface for coding agents: a server runs Claude Code, Codex, Cursor and others on your own machines, driven from desktop, web, iOS and Android apps.345
t3.codes| Splash | T3 Code | |
|---|---|---|
| The basics | ||
| What it is | Desktop app, plus a headless server you open in a browser16 | Desktop, web, iOS and Android apps controlling a server that runs the agents; the server also runs alone as the t3 CLI45 |
| Release status | v0.2.1, early development17 | Stable v0.0.45, released 2 October 2026, and nightly builds several times a day; the makers call it alpha and early-stage891011 |
| License | Open source (MIT)12 | Open source (MIT), the T3 Connect relay included; the Terms also cover use of the hosted services131411 |
| Price | Free15 | Free; no paid plans are listed, and the Terms say there is currently no subscription fee311 |
| Platforms | macOS 14+ (Apple silicon and Intel), Windows 11 x64, Ubuntu 24.04 x6416 | macOS (Apple silicon, Intel), Windows 10 and 11 (x64, arm64), Linux x86_64 and arm64 (.deb, AppImage); iOS 18+ and Android178184 |
| Built with | Rust, with a Svelte 5 frontend in a webview, built on the Elyra framework19 | TypeScript: an Electron desktop app, Expo and React Native mobile apps, and a Node.js server built on Effect10820 |
| Agents | ||
| Agents | Ships launch commands for 20 agents, including Claude Code, Codex, Copilot, Gemini, Goose, OpenCode2122 | Stable: Codex, Claude Code, Cursor, Grok Build, OpenCode, Antigravity. Nightly adds Pi, Muse Code (beta) and ACP agents (Registry or local)42324252627 |
| How it runs agents The protocol or interface | Agent Client Protocol over stdio, natively or through a pinned adapter for the vendor’s CLI212 | An adapter per agent: Claude Agent SDK, Codex app-server, an OpenCode server; Grok, Antigravity and (in stable) Cursor over ACP2829303132 |
| Agent sign-in Who pays for the model | You install and sign in to each agent’s CLI yourself; Splash runs it with that login22 | Your existing agent logins and subscriptions; T3 resells no tokens, and each provider instance can hold its own API keys4323 |
| Account required | Splash has no accounts; splash-server asks for a token it keeps in its data folder336 | Not for local use or direct connections; T3 Connect and mobile push notifications need a T3 account341135 |
| 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 attention36 | Yes: Answered in the conversation; four modes per thread, from Supervised to Full access (the initial default for new threads). Options vary by provider37 |
| MCP servers | Partly: Read-only list of MCP servers from Claude Code, Codex, Pi, Pool and Glue config files3638 | Yes: Agents get T3’s own MCP tools and load their own servers; nightly builds let outside agents sign in to T3’s MCP server2839404142 |
| Working in parallel | ||
| Isolation per session | Yes: The project folder, or a git worktree on its own branch per session36 | Yes: Per thread: the current checkout or a new worktree on its own branch. Shift-clicking several models starts one worktree thread each4344 |
| Setup scripts and dev servers | No: A worktree is a plain git checkout; Splash runs no setup scripts or dev servers3645 | Yes: Scripts in a checked-in t3.json run in a T3 terminal, optionally on worktree creation, and can open a preview URL on desktop44 |
| Built-in browser For previewing dev servers | No: No built-in browser; the workbench holds git changes, a file tree, diff and file tabs, and a terminal36 | Yes: An in-app browser preview on desktop; nightly builds run it on the server, where you and agents share tabs from any device444647 |
| Terminal | Yes: A terminal in the session folder36 | Yes: Built-in terminals on desktop, web and mobile, run by the server and keeping up to 5,000 lines of scrollback across reconnects4818 |
| What needs you | Yes: One queue for permission requests, connection failures and finished turns, kept across restarts3649 | Partly: Sidebar sections for pinned, active, snoozed and settled threads; a beta option lifts threads that finish, fail or need you43 |
| Review and shipping | ||
| Review changes | Yes: Latest response, failed tools and every changed file as a diff, with a box to send feedback36 | Yes: Inline diffs to check before pushing; diff comments go to the agent as chips; threads can rewind to an earlier message if the provider supports it340 |
| Create pull requests | No: Shows the PR for a session’s branch and starts worktrees from PR heads; does not create PRs3650 | Yes: Commits, pushes and opens PRs from a thread with generated messages and descriptions; drafts, stacks, amends and auto-merge393 |
| GitHub And other Git hosts | Yes: Issues, pull requests and Actions runs across repositories, through the gh CLI3650 | Yes: GitHub through the gh CLI, plus GitLab, Forgejo, Gitea, Bitbucket and Azure DevOps; a page to review, check out and merge PRs3951 |
| Issue trackers | Partly: GitHub (github.com), through the gh CLI; no Linear or Jira3650 | No: None documented; the Git host integrations cover repositories and pull requests, not issues39 |
| Where it runs | ||
| Mobile app | No: No mobile app; builds cover macOS, Windows, Ubuntu and a headless server16 | Yes: iOS 18+ and Android companion apps for your own machines, with push alerts via T3 Connect; nightly builds need the TestFlight or Play beta app1843523 |
| 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 | Yes: T3 Connect relay (with sign-in), direct LAN or Tailscale pairing, SSH hosts added from the desktop app, and the hosted web app46 |
| Cloud execution | No: Agents run as child processes on your computer, or on your own server with splash-server16 | No: No hosted execution; agents run on machines you control, and an optional load balancer picks one for new threads465 |
| 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 Splash3649 | Partly: First-run setup offers to import Claude Code and Codex conversations active in the last 30 days, without tool activity; nightly also imports from ACP agents that support it522526 |
| Search transcripts | Yes: Search titles, folders and saved transcript text, archived sessions included36 | Yes: Cmd/Ctrl+K searches your messages and agents’ final replies across connected machines, on web and desktop43 |
T3 Code uses each agent’s own interface: the Claude Agent SDK, Codex’s app-server protocol, an OpenCode server, and ACP for Grok and Antigravity. Stable builds run Cursor over ACP too; nightly builds move it to Cursor’s SDK and add ACP Registry agents. Splash speaks the Agent Client Protocol with every agent, natively or through a pinned adapter.2829303132532526212
T3 Code splits into a server, which runs agents, terminals and Git, and desktop, web, iOS and Android clients. The desktop app includes its own server, the t3 CLI runs one alone, and T3 Connect, direct LAN or Tailscale pairing, or SSH links devices. Splash is a desktop app; splash-server runs it on another machine, used in a browser through your own SSH tunnel.544616
T3 Code ships stable releases (v0.0.45, 2 October 2026) and several nightly builds a day. Nightly builds run a new orchestrator, merged about an hour after v0.0.45 shipped, and add the ACP Registry, Pi, Muse Code, PR watching, and scheduled and webhook tasks; the store mobile apps can’t connect to them. The docs on its main branch already describe these features. Splash tags a release when a new version on main passes CI.89262754552325395616
Both are free and MIT-licensed, and both run agents with your own agent logins. T3 Code needs no account for local or direct connections; its T3 Connect relay and mobile push notifications need a T3 account. Splash has no accounts; splash-server asks for a token it keeps in its data folder.131143435121522336
T3 Code adds tooling around the agents’ work: t3.json setup scripts, an in-app browser, a panel streaming an iOS Simulator or Android Emulator, a Usage page, and pull requests across six Git hosts. Splash adds tooling around conversations: a Needs attention queue, a review screen, transcript search, importing sessions agents list over ACP, and a GitHub view with Actions runs.44575839364950
Facts about T3 Code come from its public website, documentation and repositories as they read on 9 October 2026; we haven't confirmed each one by running T3 Code. 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.