Arugula

Keep track of your agents without checking every session. See which agents need input and what your teammates are working on. Leave unfinished work open, come back later, or join a teammate's session to help.

Arugula is a terminal multiplexer whose sessions outlive the window, the daemon and the reboot. A daemon owns your terminals; the browser (desktop or phone) draws tabs and splits you drive with the mouse.

• The swarm. Every pane on every machine you and your team can see, in one live view, clustered by project, machine, kind or person. Whatever needs someone (an agent asking, a build failing) lifts out to a rail of cards, where anyone on the team who may answer allows, answers or sends the agent its next instruction, and everyone sees who did.
• Agents as blocks. Claude Code, Codex or any ACP agent as a UI beside your terminals: tool calls with their output, approvals and questions as cards big enough for a thumb.
• Mouse first. Click, drag and right-click for tabs and splits. No chords to learn, no prefix key.
• Durable. Close the window, lose the connection, restart the daemon or reboot: the layout, working directories and scrollback come back, and each pane does what you told it to (a shell where it was, re-run its command, claude --resume). A daemon restart doesn't even touch running programs.
• Anywhere on your tailnet. The same live layout on every window and your phone, over Tailscale. Push notifications when a pane rings, a long command finishes, or an agent needs you.
• VS Code and dev servers beside your terminals (opt-in). Open in editor (or arugula edit src/main.rs:42) opens VS Code on the pane's machine, in its directory, as a block, back with its file after a restart; Open a port… shows a dev server beside its terminal. Both are off until the daemon gets a listener for them (one flag for this computer's browser; a domain of yours for the phone): see Blocks.
• What did the agent change? Changes on a pane (or arugula diff) lists the files changed in its repository, on its machine, with +/−; tap a file for its hunks and a line to see the file there, both updating while the agent works. Phone first, and a failed build is a Rerun tap away.
• Your editor in the swarm. VS Code, Cursor or nvim (over Remote-SSH too) shows up beside your panes once you ask it to. Follow its cursor from your phone; a debugger stopping, or Claude Code wanting to edit a file, is a card you answer from anywhere. The extension is arugula.arugula-editor on the Visual Studio Marketplace and Open VSX (code --install-extension arugula.arugula-editor), or arugula editors install puts in the daemon's own copy.
• Scriptable. arugula, a CLI for scripts and agents: run, send, wait for a command or a match, tail, search every pane's history.

Linux (x86_64, arm64), macOS (Apple silicon and Intel) and Windows 10 and 11 (x86_64). Share a session with someone, or a whole machine with a team, with roles and presence (teams, sharing). Remote access is over your tailnet, or through Arugula control for devices without one: end to end encrypted, so what the service relays it can't read, and it can't add a reader to your machines. You do trust it for the web client it serves (what holds).

Install

The desktop app (macOS, Linux, Windows) is at arugula.io. On a server, or a machine without a screen:

curl -fsSL https://arugula.io/install.sh | sh

On Windows, in PowerShell: irm https://arugula.io/install.ps1 | iex. With Homebrew: brew tap arugula-salad/tap && brew trust arugula-salad/tap && brew install arugula && arugulad install.

Install has the details, and the quickstart goes from the browser to your phone, scripts, agents and MCP.

Claude Code plugin

Instead of claude mcp add arugula -- arugula mcp and arugula hooks install, one plugin brings Arugula's MCP tools, its hooks (questions, permission prompts and follow-ups as cards) and a short skill. It calls the arugula you installed, so that has to be on your PATH. In Claude Code:

/plugin marketplace add arugula-salad/arugula
/plugin install arugula@arugula

Already set up the hooks by hand? Each still runs once: the plugin's copy stands aside. plugins/claude-code has the details.

Docs

docs.arugula.io has the docs for using Arugula: panes, blocks, agents, control, teams, the CLI and MCP. They're built from arugula-salad/site.

For working on Arugula itself:

• docs/development.md: building from source, testing, releasing, and the code's layout.
• docs/testing.md: the test suites.
• docs/control-e2e.md: how control's end-to-end encryption keeps it out of your terminals.
• DECISIONS.md: the decisions that still hold, an index of the records in docs/decisions/.
• docs/managoat.md: Managoat, the first backend for Cloud workspaces, and what became of it (removed, on control's side and the daemon's).
• docs/platform-features.md: which agent platform features (ACP, MCP, A2A, skills, scheduled tasks) Arugula brings in, which are planned, and the gaps.
• docs/secrets-inventory.md: every secret store and key across the org, by name and owner only, and where each goes as the org converges on the platform.
• docs/plan-archive.md: the original plan and every milestone.

License

MIT OR Apache-2.0, at your option. Terminal emulation by libghostty; see THIRD_PARTY.md.