Splitlane

Splitlane next to its neighbours

Several tools put coding agents side by side, and three of them come up often next to this one. Everything said about them here is taken from each project's own documentation as of October 2026. All three change quickly, so check their docs before relying on it.

One change since then: on 4 November 2026 Conductor announced that it is joining Meta and stopped taking new users.

ToolWhere the agents runHow it learns an agent needs youPlatformsLicense
SplitlaneTerminal panes in a desktop app, one git worktree per agent sessionThe agent's own session records for Claude Code and Codex, hooks for eight more; for the rest, only whether the process is alivemacOS, Linux; Windows from sourceGPL-3.0-or-later
herdrPanes inside the terminal you already useRules matched against what the agent draws on screen; hooks or the agent's own reports for some agentsLinux, macOS, WindowsApache-2.0
cmuxTerminal panes in a native macOS appTerminal notification sequences, a cmux notify command and hooks it installsmacOSGPL-3.0-or-later
ConductorIts own chat interface, one git worktree per workspaceIts documentation does not saymacOS; no new sign-ups since November 2026Closed source

The column it was built around

The third column is the one Splitlane was built around. A permission prompt and an idle prompt can look alike on screen, and an agent's interface changes from one release to the next. Claude Code and Codex each keep a record of their own session, so Splitlane reads that record and the process tree under the pane, and leaves the screen out of it.

Here's the catch: that works for exactly two agents, and each has to be checked again when its record format changes. herdr reports state for more agents than Splitlane does.

Where the neighbours are ahead

  • herdr keeps terminals running in a background server after you close it or lose an SSH connection, and lists several SSH machines together. Splitlane's session host does the first half on macOS and Linux: closing the window leaves the agents working. It is local only, though. There is no SSH, no second machine, and on Windows closing Splitlane still ends what it started.
  • cmux puts a scriptable browser next to the terminal. Splitlane has no browser.
  • Conductor builds the whole workflow on worktrees, with a setup script and a run script for each workspace. Splitlane also gives every agent session a worktree and branch of its own, with one setup command and a range of ports, and asks before closing a session whose branch holds work. It has no run script.

Where Splitlane goes a different way on purpose

  • Agents run in ordinary terminals, the same as outside the app. Conductor puts them in its own chat interface and keeps its terminal mode experimental.
  • herdr and cmux both give agents an API that can send input to another pane. In Splitlane the MCP bridge can only read. An agent types into the sessions it opened itself, and into one you opened only after you allow it; typing into any other pane stays off until you start Splitlane with it switched on.
  • The diff of what the agents changed and the project's file tree are in the same window.

Which one fits

If you work inside a terminal or over SSH, herdr or plain tmux will fit better. If you already use Conductor, it keeps working for now: the local app gets new models and critical fixes until early 2027, and Conductor Cloud goes read-only on 13 November and shuts down on 20 November 2026. New users can no longer download it.

Splitlane is for a few agents in ordinary terminals on your own machine, where the question is which one is waiting.