--- title: "Cork vs Xirp: run many agents, or keep many agents from colliding · Cork" description: "Cork vs Xirp: Spotify's Xirp runs parallel coding agent sessions in worktrees on macOS. Cork coordinates those agents so they stop overwriting each other." canonical: "https://corkcli.com/blog/cork-vs-xirp" last_updated: "2026-11-14" published: "2026-10-03" author: "Kevin Vera" --- # Cork vs Xirp: run many agents, or keep many agents from colliding Cork vs Xirp: Spotify's Xirp runs parallel coding agent sessions in worktrees on macOS. Cork coordinates those agents so they stop overwriting each other. By Kevin Vera · October 3, 2026 · [Comparisons](https://corkcli.com/blog/c/comparisons) · 7 min read How is Cork different from Xirp? Xirp, from Spotify, is a macOS app for running and managing many local AI coding sessions at once, each in its own Git worktree, with optional context from Spotify Portal. Cork does not run sessions at all: it is a [coordination layer](https://corkcli.com/blog/coordination-layer-ai-coding-agents) that keeps several AI coding agents, and the people running them, from overwriting each other on one codebase, and hands each agent what the others already learned. Xirp answers "how do I run 20 agents without losing track of them?" Cork answers "what happens when those 20 agents touch the same code?" The two fit together more than they compete. ## Cork vs Xirp at a glance | Topic | Cork | Xirp (as of October 2026) | |---|---|---| | What it is | Coordination layer for [parallel AI coding agents](https://corkcli.com/blog/parallel-ai-coding-agents) and teammates | Agentic development environment (desktop app) for managing many agent sessions | | Where agents run | Wherever they already run, on your machine | In persistent terminal sessions inside the Xirp app, on your Mac | | Agents covered | Claude Code, Codex, Cursor (hooks); any MCP client | Claude Code, Codex, Gemini CLI, Pi, Cursor | | Isolation model | Shared codebase, coordinated live | One Git worktree per task | | What is shared | Signatures, callers, recent changes, notes, live edits between agents | Optional Portal context: Workspace wiki pages, catalog entities, prior sessions | | Conflict handling | Write gate, live change notices, [semantic lint](https://corkcli.com/blog/semantic-lint), rebase-and-test landing | Worktrees keep agents apart while they work | | Platforms | Claude Code, Codex and Cursor on your machine | macOS only | | Install | `curl -fsSL https://corkcli.com/install.sh \| sh` | Desktop download, beta | | Pricing | Free (local, and 10 agent hours a month in the cloud); $20 a month per 100 agent hours, pooled | Desktop app free in beta; Portal Foundations free for 60 days | ## What is Xirp? Xirp is Spotify's "vendor-neutral agentic development environment," announced on the Spotify Portal blog on August 10, 2026. Its docs describe it as a way to "run and manage local AI coding sessions across projects, agents, and [Git worktrees](https://corkcli.com/blog/git-worktrees-parallel-ai-coding-agents)." You can run Claude Code, Codex, Gemini CLI, Pi or Cursor in persistent terminal sessions, create a separate worktree for each task so agents work in parallel, and manage terminals, Git changes, files, rules, skills and session status from one app. Spotify says context is "decoupled from any single agent or harness," so you can switch tools mid-project and keep the working state. Connecting to Spotify Portal (optional) gives agents access to Workspace wiki pages, catalog entities and prior sessions, so a session starts knowing who owns an upstream service and what depends on it. Spotify reports that thousands of its engineers adopted Xirp across more than 36,000 sessions. Xirp is in beta and runs on macOS only. ## What is Cork? Cork (corkcli.com, by Lithometric) keeps several AI coding agents, and the people running them, from overwriting each other on one codebase, and hands each agent what the others already learned. It does not run agents or host machines: Claude Code, Codex and Cursor keep running where they already run, and Cork coordinates them. Hooks in Claude Code, Codex and Cursor do the protocol with no extra model calls, and an MCP server (https://mcp.corkcli.com) works with any MCP client. When an agent starts or gets a prompt, it receives a briefing with the exact signatures, callers and recent changes of the code it is about to touch. When another agent renames something yours depends on, your agent hears about it on its next step. A [write gate](https://corkcli.com/blog/write-gate) holds an edit against code another agent is changing right now until your agent has their version. Semantic lint turns a teammate's rename into a rule your agents are checked against, and landing makes `git push` one step that rebases onto teammates' commits, reruns the tests and pushes. Agents can message each other, and MCP tools like get_symbol, blast_radius, recap and remember/recall are available. ## Where Xirp stands out - **Session management at scale.** Xirp is built to keep dozens of agent sessions visible and organized in one app, with terminals, Git changes and layouts side by side. - **Broad harness support.** Claude Code, Codex, Gemini CLI, Pi and Cursor all run inside it, and Spotify says working state carries over when you switch. - **Organizational context.** With Portal connected, agents can see service ownership, catalog entities and Workspace docs, which is context a codebase alone does not hold. - **Proven internally.** Spotify reports more than 36,000 sessions from its own engineers before the public beta. ## Where Cork wins - **Agents in different worktrees still collide.** Worktrees keep agents apart while they type, but their changes meet at merge time. Cork tells each agent, live, when another one changes code it depends on, so agent merge conflicts surface before they are written. - **Code-level briefings.** Cork hands an agent the exact signatures, callers and recent changes of what it is about to touch, so it searches less. In Cork's benchmark (12 Claude Code agents at once on one repository, hard tasks), agents with Cork used 53% fewer tokens than the same agents without it. - **Teammates, not just your own sessions.** On the paid plan, agents on teammates' machines see each other, so [multiplayer coding agents](https://corkcli.com/blog/multiplayer-coding-agents) across a team stay coordinated. - **Not tied to one OS or app.** Cork works with Claude Code, Codex and Cursor where they already run; Xirp is a macOS app. ## Can you use both? Yes, and it is a natural pairing. Xirp runs and organizes the sessions; Cork coordinates what those sessions do to shared code. Run multiple Claude Code agents in Xirp's worktrees, and Cork's hooks in Claude Code, Codex and Cursor keep those agents aware of each other's renames and signature changes, so the work still fits together when the worktrees merge. Cork does not provide a session manager, terminal UI or Portal-style catalog, so Xirp fills that gap. ## Pricing compared - **Xirp:** the desktop app is free for Mac users during the beta. "Xirp + Portal Foundations" is free for a 60-day trial. A full "Xirp + Portal" plan is listed as coming soon with pricing not announced (as of October 2026). - **Cork:** Cork Free gives unlimited agents and repos on one machine, no account, with all data on the machine. Cloud Free adds an account with 10 agent hours a month (30 bonus hours the first month) and a 30-day history window. Beyond that you pay for agent hours, not seats: $20 a month per unit of 100 hours, pooled across the workspace, graduated to $17 (units 11 to 50) and $15 (51 and up), with 15% off a year. Every member is a player, with teammates' machines, prompts matched to code by meaning, shared knowledge and 90-day history. Enterprise starts from about 100 units. ## Bottom line Xirp is a strong place to run and watch many coding agents on a Mac, especially if your company uses Spotify Portal. It isolates agents in worktrees but does not coordinate the code they change. Cork is that coordination: it keeps parallel AI coding agents from overwriting each other and briefs them on the code they touch. If you run many agents, you likely want something like Xirp to run them and Cork to keep them from colliding. ## Frequently asked questions ### Is Cork an alternative to Xirp? Not directly. Xirp runs and manages agent sessions; Cork does not run agents. Cork is the coordination layer that works alongside a session manager like Xirp. ### Does Xirp stop agents from overwriting each other? Xirp gives each task its own Git worktree, so agents do not overwrite each other while they work. Their changes can still conflict when worktrees are merged. Cork addresses that by telling agents about each other's changes live and gating edits to code another agent is changing. ### Does Xirp work on Windows or Linux? As of October 2026, Xirp's docs and plans page list macOS only. ### Can I use Cork with Claude Code sessions running inside Xirp? Cork works through hooks in Claude Code, Codex and Cursor and an MCP server any MCP client can use, so it coordinates those agents regardless of which app launches them. ### Is Xirp free? The Xirp desktop app is free during its beta. Portal Foundations is a 60-day free trial, and full Portal pricing had not been announced as of October 2026. ## Sources Checked October 2026: - - - - - ## Related reading - [Cork vs Claude Code on the web: where agents run, or how they share one codebase](https://corkcli.com/blog/cork-vs-claude-code-on-the-web): Cork vs Claude Code on the web: one runs Claude Code sessions in Anthropic's cloud, the other keeps parallel agents from colliding on shared code. - [Cork vs Herdr: where agents live vs how they share a codebase](https://corkcli.com/blog/cork-vs-herdr): Cork vs Herdr: Herdr keeps AI coding agents running in persistent terminal panes. Cork keeps those parallel agents from overwriting each other's code. - [Cork vs AQ: a shared cloud workspace, or a coordination layer for the agents you already run](https://corkcli.com/blog/cork-vs-aq): Cork vs AQ: AQ hosts multiplayer cloud workspaces for coding agents. Cork coordinates the agents you already run so they stop overwriting each other. - [Cork vs Mosaic: shared session memory, or live coordination on the code](https://corkcli.com/blog/cork-vs-mosaic): Cork vs Mosaic: Mosaic syncs AI coding sessions into shared team memory; Cork keeps parallel agents from overwriting each other. How they differ and fit. [All articles](https://corkcli.com/blog.md) · [Cork in Markdown](https://corkcli.com/index.md) · [llms.txt](https://corkcli.com/llms.txt) This page in HTML: https://corkcli.com/blog/cork-vs-xirp