The Xirp Cockpit Paradox

https://preview.redd.it/5wji1dapbaoh1.png?width=3840&format=png&auto=webp&s=f0402b65017fc688df4c4fd3cab233d76abef104

tl;dr: One developer, fifty sessions, no pilot. What happens when the cockpit goes crewless?

https://xirp.spotify.com is Spotify's macOS desktop app for running dozens of concurrent coding-agent sessions across Claude, Gemini and Codex, each in its own git worktree.

Spotify engineers have run over 36,000 sessions(vs 300k run in agent-swarm.dev , it's early). Context is decoupled from the model so you can switch harnesses mid-task.

1. Own your worktree isolation. Xirp gives every session its own git worktree. Timbal and Quartermaster converge on the same pattern: one session's state never contaminates another's. Fifty concurrent sessions need this, and Xirp ships it by default.
2. Treat models as interchangeable. Context lives outside the harness. Start a task in Claude Code, finish it in Gemini CLI without losing state. Xirp lets you swap mid-project and the session follows you.
3. No memory without the pilot. Xirp sessions stop when the developer closes the laptop. LoL!!

→ Wait. Xirp has been used less than https://github.com/desplega-ai/agent-swarm, do you really want to risk it? Spotify is not even using it that much.

If you are going down this local machine rabbithole, use one of the battle tested ones, like https://github.com/stablyai/orca. Don't blame it on us.