R&D represents a diverse group of engineers, designers, product managers, and researchers working together to build the tools, services, and open source products that people across the globe use every day.
External link for Spotify R&D
Spotify R&D reposted this
Great suggestion, everyone. 👏 And here it is! Your week of AI coding, in a nutshell. Xirp Weekly Rewind ⏪ turns your week into a clear picture: every session, every merged PR, every line changed, and what it all cost. Use it to show your work in standups and reviews, spot when you do your best work with the activity heatmap, and keep AI spend in check before it surprises anyone. Every Friday, zero setup. Give it a try: https://hubs.li/Q04yBjBc0
Spotify R&D reposted this
Proud to see another feature my team has worked on getting out! Being Warehouse Native, onboarding Confidence meant having access to a warehouse. Some teams are not there yet and we are accounting for them by launching Confidence Cloud! Using the Confidence Onboarding wizard you can get started with Confidence in a matter of minutes. Try it out!
Your first experiment shouldn’t have to start with a data warehouse integration project. You have an idea to test. But your team doesn’t have a warehouse, or getting access to one means waiting for help from another team. We're now introducing Confidence Cloud: start experimenting without first setting up or connecting a data warehouse of your own. Confidence creates and manages the warehouse for you. Connect your application, send events, and create metrics to measure whether your product changes make a difference. Already have an established data warehouse? Well, the warehouse-native Confidence capabilities isn’t going anywhere. You can continue using your existing business data and custom SQL, with the flexibility and control of your own infrastructure. Same Confidence platform. Just two ways to get started. We’ve introduced several new capabilities in beta over the past few weeks, and we have more to come! Confidence Cloud adds an easier starting point, so more teams can spend less time on setup and more time building, measuring, and learning. https://lnkd.in/dKnZ8t64
Spotify R&D reposted this
Import a project. Run a session. Switch agents mid-task with full context carried over. Xirp lets you start a session in Claude Code then swap to OpenAI's Codex without losing a thing. The conversation history, the findings, the context. It all transfers. Different agent, same session. Try now https://hubs.ly/Q04y2GYV0
Spotify R&D reposted this
How much did your AI agents cost you yesterday? What about the day before? With Xirp, you can now see costs by agent, by model, and by day, broken down across your coding agents and every model you're running. Hover over any day and see exactly where your tokens went. The first step to managing AI tooling spend is knowing what you're spending. Xirp gives you that knowledge. Try now https://hubs.li/Q04xKymQ0
Spotify R&D reposted this
One of the most common requests from Xirp users: more choice in coding agents and models. Today we're taking a step in that direction. Xirp by Spotify now supports Pi, an open-source coding agent with access to a broad range of models. Same workflow, dozens of concurrent sessions, way more choice. Try it out: https://hubs.li/Q04xx1LS0
Spotify R&D reposted this
Your AI agents are running up a tab you're not tracking. Every session starts from zero, scanning, guessing, orienting, before a single useful line ships. Multiply that across your team and it becomes one of your biggest AI tooling line items. We measured the hidden tax at Spotify. Then we fixed it. Here's how https://hubs.li/Q04x2RtF0
Spotify R&D reposted this
One prompt. Zero exploring. 🎯 We started a OpenAI Codex session from a Portal by Spotify workspace. The agent's first move? Pull service ownership, dependencies, and architecture automatically. No "what repo is this?" No five minutes of codebase spelunking. The context came to the agent, not the other way around. Portal workspace → Xirp session → grounded from the first response. Your context. Your codebase. Your agent already knows what it's looking at. Try it → https://hubs.li/Q04wYHns0
Spotify R&D reposted this
A Claude Code plugin called shunt and two declarative agents running on Portal by Spotify. That's all it took to stop burning frontier model tokens on file reads and boilerplate generation. The grunt work routes to a cheaper worker model. The frontier model only handles problems worth its price. 90% token reduction on bulk reads. No new infra. The agents are public and the plugin is open source. https://hubs.li/Q04wGXlY0
Spotify R&D reposted this
A Claude Code plugin called shunt and two declarative agents running on Portal by Spotify. That's all it took to stop burning frontier model tokens on file reads and boilerplate generation. The grunt work routes to a cheaper worker model. The frontier model only handles problems worth its price. 90% token reduction on bulk reads. No new infra. The agents are public and the plugin is open source. https://hubs.li/Q04wGXlY0
Spotify R&D reposted this
One thing we learned building developer platforms at @Spotify: The real test starts when engineers begin using and relying on them. We released @Xirp publicly last month, and since then, the feedback has started flowing. The team has shipped eight beta releases, and you’ve been telling us what works well and where the gaps remain. A lot of the work has focused on reliability: better sign-in and session recovery, more accurate session states and notifications, clearer startup failures, and fixes for the edge cases that show up once engineers start relying on a tool in even more diverse workflows. For me, that reliability work is crucial because every engineer should be able to trust Xirp every day as we do at Spotify. Backstage grew inside Spotify because our developers were also its customers. They used it every day, told us where it got in their way, and helped make it better. Xirp is going through that same process now, only at an even faster pace. Engineers and technical leads outside Spotify are now using Xirp in their own workflows, giving us a much broader range of experience to learn from. We value all of the feedback you’re sharing with us. Keep it coming. See everything that’s changed: https://lnkd.in/dbhKeSAS