Xirp by Spotify

Xirp by Spotify is a developer tool. Spotify's agentic development environment that grounds coding sessions in your services, ownership, docs and architecture decisions. Workspace and automatic documentation keep context from disappearing, and Claude, Gemini and Codex can be swapped without losing it.

Xirp is an agentic development environment built by Spotify that aims to fix a problem most coding tools ignore. Generation is no longer the bottleneck: code ships faster and more services get built. What breaks is context. New engineers take months to ramp up, and AI agents make decisions that are technically correct yet operationally wrong because they do not know the system they are working inside. The knowledge exists, but it sits in Slack threads and in the heads of the few people who built a service years ago. Xirp treats that as a retrieval problem rather than a documentation problem. The product centers on three connected pieces. The agent is grounded in your services, ownership, dependencies and architectural decisions, so each session begins with the system rather than a single file. Workspace, a Spotify Portal plugin, keeps work items, sessions and docs in one shared place, so context survives when an engineer wraps up and the next person or agent picks the work up. Documentation is generated automatically from coding sessions and fed back into future ones, which keeps it current without asking engineers to stop and write. Xirp is a harness rather than a single model. Teams switch between Claude, Gemini and Codex without losing context, and sessions run locally or remotely. That vendor independence matters for organizations that do not want their institutional memory tied to one provider. The obvious audience is platform and infrastructure teams at companies large enough to have real service ownership maps and architecture decisions worth preserving. A single small project gains little from a context layer built on Portal. The beta is invitation based, with access requested through the join beta page, and a Portal instance is included with beta participation. Weekly Portal Office Hours and a Discord community carry much of the onboarding. Xirp is not a replacement for a general chat assistant or a lightweight editor plugin; it is closer to infrastructure for engineering organizations that already feel the cost of lost context.