The 'Agent Harness' You Didn't Know Existed
Spotify's internal AI dev tool, Xirp, aims to streamline the chaotic landscape of AI coding agents. Designed for its over 1,300 engineers, Xirp provides a unified platform to manage the proliferation of tools like Claude, Codex, and Gemini, helping them tame the sprawl of active sessions and ongoing projects. It promises a more organized, less overwhelming approach to AI-assisted development.
Crucially, Xirp isn't a new AI model itself; Don't't confuse it with a fresh competitor. Instead, it functions as a GUI-based agentic development environment—think of it as a polished, user-friendly wrapper for existing tools. It orchestrates and manages diverse agent sessions, much like a sophisticated version of command-line mainstays such as tmux, Conductor, or open-source solutions like T3 Code, rather than replacing the underlying AI capabilities.
However, before you imagine installing this on your machine, there's a significant catch. Accessing Xirp requires a separate Spotify Technology account, distinct from your regular Spotify music account. This immediate friction, combined with the application's closed-source nature, positions it starkly against community-driven, open-source alternatives like T3 Code, which offer broader accessibility without corporate gatekeeping.
Multi-Agent Mayhem, Tamed
Xirp’s strength truly emerges in its session management. Forget clicking between tabs; a grid layout lets developers monitor and interact with multiple AI agents side-by-side. It’s like a graphical tmux for your Claude, Codex, and Gemini sessions, offering intuitive drag-and-drop resizing and the ability to integrate standard terminal windows alongside agents.
Power users will appreciate two standout features. Session forking clones an entire agent interaction, preserving all context and history. This allows engineers to explore alternative solutions or test new directions without abanDon'ting their original thread. Even more impressive, you can swap agents mid-task – switch from Claude to Codex, for instance – and Xirp seamlessly migrates the full chat history and context.
Another unique capability, "dependent sessions," streamlines complex workflows. This feature allows one agent's task to automatically trigger another upon completion, creating chained operations. Imagine an agent writing code, then handing off its output to a second agent for immediate review or testing, all within a predefined sequence.
A GUI With an Identity Crisis
While Xirp excels at agent management, its built-in peripheral features often fall short. The Git diff viewer, for instance, presents changes clearly but forces a full-screen view. Many developers prefer quick overviews in a sidebar or dedicated tools like GitHub PRs for comprehensive reviews.
Similarly, Xirp includes a basic file editor and an internal browser. These additions are functional, yet they can't match the power or familiarity of external, specialized tools like VS Code. Most engineers already have a finely tuned setup, making these integrated options feel redundant.
Delving into the project overview and skills tabs reveals further limitations. The main prompt box, while central, lacks crucial context-awareness. It doesn't intelligently pull information from active sessions or the project state, making it less efficient than expected for complex tasks.
During testing, the skills section proved buggy and offered limited practical utility. These features feel like afterthoughts, failing to integrate seamlessly with the core agent management experience. Spotify's own engineers likely bypass them for more robust external solutions.
Xirp's user interface is undeniably well-crafted, but its ambition to be an all-in-one environment introduces unnecessary clutter. Developers often favor a focused, minimalist workflow, leveraging a suite of best-in-class individual tools. This integrated approach, though well-intentioned, can hinder rather than help.
Ultimately, the core session management is Xirp's strength. The peripheral features, however, dilute its focus, making it a decent jack-of-all-trades but master of few outside its primary purpose. For more insights into Spotify's broader AI strategy, read What we've learned scaling AI coding agents at Spotify.
Enjoying this? Get one like it in your inbox each morning.
one email a day · unsubscribe in two clicks · no third-party tracking
The Verdict: A Spotify Tool for Spotify's Problems
Ultimately, Xirp is a fascinating look into how a tech giant like Spotify tackles its unique challenges. But for the average developer or small team, Don't't expect to be using it. Its true value lies in solving the coordination nightmare of over 1,300 engineers simultaneously wrangling multiple AI agents like Claude, Codex, and Gemini. That's a problem most of us simply Don't't have.
Spotify built Xirp as an internal solution, deeply integrated into its existing developer ecosystem. Specifically, it pulls crucial context from Spotify's 'Portal' product, which acts as a centralized knowledge base for their sprawling codebase. Without that deep integration, Xirp loses much of its power, becoming just another agent management UI.
While the session management — especially the grid layout for monitoring multiple agents — is genuinely impressive, the peripheral tools like the built-in Git diff viewer or file editor remain inferior to dedicated, preferred developer tools. It’s a classic case of a company building for its specific, large-scale needs rather than general utility.
For solo developers or open-source contributors, polished alternatives already exist that offer similar agent orchestration without the overhead or the need for a proprietary enterprise platform. Xirp is an engineering marvel, but it’s a highly specialized tool designed for Spotify's problems, not yours.
Frequently Asked Questions
What is Spotify Xirp?
Xirp is an agentic development environment created by Spotify. It's a desktop application that provides a unified graphical interface (GUI) to manage sessions with various AI coding agents like Claude, Codex, and Gemini.
Does Xirp replace AI models like Claude or Gemini?
No, Xirp does not replace the underlying AI models. It acts as a 'harness' or a management layer, allowing developers to run, monitor, and interact with multiple agent sessions from different providers in one place.
What are the standout features of Xirp?
Key features include a grid view for managing multiple agents side-by-side, the ability to 'fork' a session to explore different paths while preserving context, and the unique capability to switch AI models (e.g., from Claude to Codex) mid-session.
Is Spotify Xirp free to use?
Yes, but it requires signing up for a Spotify Technology account, which is separate from a Spotify music account. This requirement and its closed-source nature are notable barriers to entry for some users.
Who is the ideal user for Xirp?
Xirp was built to solve Spotify's internal challenges of scaling AI agent usage across over a thousand engineers. It is best suited for large engineering organizations, especially those using Spotify's Backstage and Portal ecosystem, rather than solo developers.

