Ever watched an AI agent lose the plot halfway through a task? In the first Dev Mode episode of NerdOut@Spotify, JD, shows how he splits the work across a bunch of agent sessions in Xirp by @Spotify instead. Live demo, our own repos, no slides. Check out the episode: hubs.li/Q04B2D310

Portal, Xirp, @SpotifyConf, and Spotify for Backstage are now part of something bigger. Meet Spotify Technology: the tools behind @Spotify, together as one system. Proven at Spotify. Now yours. hubs.li/Q04zBzt80

"Just start over with another agent." No. Xirp transfers full session context when you switch. @claudeai to @OpenAI Codex, mid-task, nothing lost. Try now hubs.ly/Q04y2K3N0

💫 A little end of week wrap up with some Xirp updates (v0.32–v0.35): → @Pidotdev coding agent support → Worktree search + linked shell terminals from the CLI → Repo insight on first task — starter goals from your codebase → Restore from backup when the database breaks → Pinnable toolbar actions → CJK input fixes, better session recovery, and notification preferences Changelog: hubs.li/Q04xTcgV0

How much did your AI agents cost you yesterday? Or the day before? With Xirp, you’ll see costs broken down by agent, model, and day.  Cost insights live in Xirp. 👀 Try now hubs.li/Q04xKGQ20

You asked for more model choice. Here it is. ✨ Xirp by @Spotify now supports @Pidotdev, an open-source coding agent with access to a broad range of models, right inside the workflow you already know. Give it a try: hubs.li/Q04xx2rY0

Every AI agent session starts from scratch scanning, guessing, relearning things your org already knows. You're paying for that orientation loop every single time. We measured the hidden tax at Spotify and then we fixed it. Here's how hubs.li/Q04x2SLp0

One prompt. The agent pulls Portal context before it touches the codebase 🎯 🔗 Service ownership. Dependencies. Architecture. All there before the first response. No exploring. No guessing. The context came to the agent. 🚀 Portal workspace → Xirp session → grounded immediately. hubs.li/Q04wYYnf0 Try it → hubs.li/Q04wYYmX0

A Claude Code plugin + two declarative agents on Portal by Spotify. Bulk reads and boilerplate route to a cheaper model. Frontier model stays on real problems. 90% token savings, zero infra changes. hubs.li/Q04wGXl40

@cursor_ai in Xirp. Full project context. Isolated worktrees. Session history that persists across your workflow. Same session management you'd get with any agent in Xirp. Now with Cursor in the mix. Your projects. Your context. Your favourite agent. Try it for yourself - hubs.li/Q04w3XZl0

@cursor_ai just joined the lineup. Xirp now supports four harnesses. Switch between them mid-project without losing context. hubs.li/Q04tQ8RX0 @spacexai

Xirp 🤝 Discord Join the Xirp beta and share feedback, bugs, and ideas with us in Discord: hubs.li/Q04tbFLm0 Not part of the Xirp beta yet? Give it a try: hubs.li/Q04tbtV30

The Xirp requests are rolling in and our teams are on it. Shout out to our beta users for sharing your feedback! 🧡  Here are some of the updates we’ve made over the last few days: → Split terminal panes → New Doctor page that checks your agents, tmux, and hooks, offers fixes → Fixed: session deletion could remove your main repo checkout Plus proxy/cert sign-in fixes and quieter Codex notifications. We’re shipping changes regularly; track the full changelog here: hubs.li/Q04t2Kr20 Try Xirp for yourself: hubs.li/Q04t2SKS0

We just launched Xirp, a vendor-neutral agentic development environment. One place to manage agent sessions across @ClaudeDevs, @GeminiApp CLI, and @OpenAI Codex. 1,300+ @Spotify engineers already use it. Now it's available for you to try. Learn more at xirp.spotify.com.

Read about Xirp from Tyson Singer, SVP of Platform at Spotify: portal.spotify.com/blog/intr…

Fleetshift is now GA in Spotify Portal. You describe the change once and Fleetshift rolls it out across your fleet: targeting, creating PRs, and tracking them. Deterministic recipes for the predictable stuff. Honk, our AI coding agent, for everything that isn't. We built this because a Java runtime migration once took 8 months and about 2,000 pull requests. Now a framework release reaches 70% adoption in under a week. When Log4j hit, 80% of production services were patched within 9 hours. → hubs.li/Q04qhY400