splay

agent
Security Audit
Pass
Health Pass
  • License — License: MIT
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Community trust — 110 GitHub stars
Code Pass
  • Code scan — Scanned 7 files during light audit, no dangerous patterns found
Permissions Pass
  • Permissions — No dangerous permissions requested
Purpose
This tool is a workspace manager designed to orchestrate parallel development. It registers git repositories, creates isolated worktrees, and runs persistent terminal sessions for multiple coding agents via a CLI or a native GTK desktop app.

Security Assessment
Overall risk: Low.
Based on the light code audit, no dangerous patterns, hardcoded secrets, or excessive permissions were detected. The application natively interacts with git and executes shell commands to manage terminal sessions, but this is its intended and explicitly stated function. While managing agents inherently involves executing code and scripts within those isolated workspaces, the tool itself does not appear to make suspicious outbound network requests or access unauthorized sensitive data.

Quality Assessment
The project is actively maintained, with its most recent push occurring today. It is properly licensed under the standard MIT license. While the community trust footprint is currently small (16 GitHub stars), this is not unusual for an early-stage or niche open-source utility. The provided documentation is clear, and the codebase is transparent regarding its core functions.

Verdict
Safe to use, though users should inherently trust the external coding agents they choose to run within the managed workspaces.
SUMMARY

Fan out your agents. A Linux workspace manager for running coding agents in parallel, one workspace per task.

README.md

Splay

Splay

Fan out your agents.

Splay is a workspace manager for parallel coding agent development, similar to cmux, Superset, and Conductor. Register git repositories, spin up isolated worktrees, and run persistent terminal sessions inside them from a native GTK desktop app or the CLI.

Splay was previously called Swarm. Read the announcement blog post for more background.

Features

  • Works with any coding agent — run Claude Code, Codex, OpenCode, or any other CLI tool inside a session. Sessions are just terminals, so anything that runs in a shell runs under Splay.
  • Workspace per feature using git worktrees — every workspace is an isolated git worktree, so parallel agents never share a checkout or step on each other's branches.
  • Fast workspace cloning — branch off an existing workspace into a new worktree and branch in one command.
  • Multi-repository management — register any number of GitHub repositories and manage their workspaces and sessions from one place.
  • Ghostty-backed persistent terminals — sessions are backed by libghostty-vt and survive disconnects; detach and reattach from the GUI or CLI without killing the process.

Installation

Splay runs on Linux. Install the latest prebuilt release with:

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/splay-sh/splay/releases/latest/download/splay-installer.sh | sh

Then start the GUI with:

splay

Or drive Splay from the command line with splayctl:

splayctl --help

For more information, check out the documentation section.

Motivation

Coding agents are most effective when you can run many of them in parallel — one per feature, one per bug fix. But in practice, this quickly turns into chaos. Each agent needs its own copy of the source code so they don't step on each other's changes, and each one runs in its own terminal. Before long, you're drowning in terminal tabs, losing track of which agent is working on what, and manually juggling git branches and directories.

Splay exists to tame that. It gives you a single place to manage all your repositories, workspaces, and agent sessions — so you can scale up the number of parallel agents without the overhead of keeping it all organized yourself.

How it works

Splay organizes work into repositories, workspaces, and sessions. A repository is the git repository that holds your project's source code. A workspace is an isolated copy of that source code, backed by a git worktree, where work happens independently without interfering with other workspaces. A session is a persistent terminal environment running inside a workspace — it could be a coding agent, a shell, or any long-running command.

For example, a typical workspace-per-feature workflow looks like this: create a workspace for every feature or bug fix, let a coding agent work on it in a session, submit a pull request, address review comments and iterate — all within the same workspace. When the work is merged to mainline, remove the workspace.

FAQ

How is Splay different from X?

Superset is a macOS desktop app for running multiple CLI coding agents in parallel across git worktrees. Unlike Splay, it ships with a built-in diff viewer, editor, and terminal, supports one-click handoff to external editors, and requires an account. Splay is Linux-only, fully local, and focuses on terminal sessions and worktree management.

cmux is a macOS terminal multiplexer for running coding agents in parallel, with split panes, per-tab notifications, an in-app scriptable browser, and SSH workspaces. Unlike Splay, it doesn't create or manage git worktrees — you supply the checkout layout yourself. Splay runs on Linux as a GTK 4 app, creates worktrees automatically, and has an opinionated, but minimal feature set.

Conductor is a closed-source macOS app for running Claude Code and Codex agents in parallel across git worktrees, with a built-in UI for inspecting activity and reviewing/merging changes. Unlike Splay, it has no CLI and bundles its own review workflow. Splay is MIT-licensed, Linux-only, and leaves review to whatever tools you'd run in a terminal.

I used Swarm. What happens to my workspaces?

Nothing you need to do by hand. The first time Splay starts, it moves ~/.local/share/swarm to ~/.local/share/splay, updates the stored paths, and repairs the git worktrees. Stop any sessions still running under Swarm first. See Migrating from Swarm for details.

Building from source

The GTK desktop app depends on GTK 4 development headers and a Zig toolchain for the vendored libghostty-vt build. Splay currently requires zig 0.15.2.

On Ubuntu/Debian, install the same system packages used by the release build:

sudo apt install gcc g++ libcairo2-dev libglib2.0-dev libgtk-4-dev libpango1.0-dev pkg-config

Then install Zig 0.15.2 and make sure zig is on your PATH.

Install the program with:

cargo install --path .

Documentation

See MANUAL.md for the full reference.

License

Splay is available under the MIT license.

Reviews (0)

No results found