• Sources: primary
  • Summary: Spotify says that after an internal all-hands titled AI or die, about nine months ago, engineers moved to running fleets of agents, which trapped context in personal instruction files and made costs hard to attribute. Its Portal product adds workspaces that seed agent sessions with catalog entities, designs and wikis, plus a PR inbox for agent PRs, a catalog of skills and rules, an MCP server, usage and cost insights, and Fleetshift for refactors across thousands of repositories. It also has an internal session tool called Zerp. Spotify reports over 6,200 Portal users and over 121,000 sessions.
  • Why it matters: An existing service catalog can serve as shared agent context and as the place to track agent cost and review queues.