Spotify put Xirp into public beta on August 10. Tyson Singer, writing on the Spotify Portal blog that day, said thousands of Spotify engineers had adopted the app across more than 36,000 sessions (Singer, 2026). One coding tool in one terminal is a workflow. Dozens of tools across repositories is an operations problem, and that is the problem Spotify chose to productize.

Xirp is a Mac desktop app. It detects the coding-tool command lines you have installed and runs them in persistent terminals you can leave and return to. Current documentation lists Claude Code from Anthropic, Codex from OpenAI, Gemini CLI from Google, plus Pi and Cursor (Spotify for Backstage, 2026). Each tool keeps its own login and model settings. Xirp organizes those sessions on one desk.

Each Task Gets Its Own Working Folder

The useful mechanism is isolation. Xirp can give each task its own Git worktree, a separate working folder attached to the same repository. Two tools can edit the same project and leave each other's files alone. Singer wrote that the design is meant to make fifty or more parallel sessions tenable. Sessions persist when you close the window. You can switch the tool on a task and keep the working state.

That is the product an engineering company ships after it has watched people open five terminals, lose track of which branch belongs to which job, and spend tokens rediscovering a decision another session had already made. Singer described the cost as rising pull requests, rework, and wasted model spend. Xirp is Spotify's answer to the crowded laptop.

Xirp Runs on Your Mac Before You Connect Portal

Local projects, worktrees, files, rules, and a grid of sessions work on their own. Portal is the commercial product Spotify built on Backstage, the internal developer catalog it later opened to other companies. When Xirp is connected, a session launched from a catalog entity or a Workspace can pull ownership, dependencies, wiki pages, and prior session notes through Model Context Protocol. You can upload a finished session so the next person or tool starts from that record.

Singer's case for the pairing is that tools guess less when they can see who owns the upstream service and why the system was built that way. That claim is Spotify's. What you can verify today is narrower. The beta is Mac only. Sign-in uses a Spotify Technology account, separate from a personal music login. Personal inboxes such as Gmail are rejected. The coding tools still require their own paid accounts. Features and screens can change during the preview (Spotify for Backstage FAQ, 2026).

Spotify Is Right to Ship What the Engineering Floor Learned

A company that employs thousands of engineers accumulates operating knowledge about services, owners, and now coding tools on laptops. Backstage came from too many services and unclear owners. Portal packaged that map for other firms. Confidence packaged experimentation. Xirp packages the next pile of work: many artificial intelligence coding tools running at once on the same machine.

Expect more of this from other platforms. A retailer that built warehouse software for itself will sell the warehouse software. A bank that built fraud models for its own ledger will sell the model operations layer. The core business funds the laboratory. The laboratory becomes a second product line once the internal users have paid the tuition.

Outside Spotify the test is practical. Companies have to install a Mac app, accept a Technology account, and decide whether their catalog is complete enough to feed an agent. The wider pattern is already visible: take a hard internal year and put a product around it.

About Shashi Bellamkonda

Loading bio…

LinkedIn Profile

Get new posts by email:

Subscribe

Powered by