Orbs and Jellyware

Quinn and Thorsten answer the responses to The Company of the Future. Some teams stopped doing pull requests; others said their security team would never allow it, and asked Amp to meet people where they are. They explain why, in 2026, meeting people where they are means falling behind, and how a team of 21 makes big architectural changes without RFCs: self-hosted Orbs, worked out in one Slack thread and a customer visit, and macOS Satellites, which launched an hour before they recorded. They also cover how culture keeps slop off main, adopting customers instead of filing tickets, why they don't hire their way out of priorities, removing features, why Thorsten no longer looks at unit tests, the unseen cost of code review, and why you've got to get the tokens.

Quinn and Thorsten sit down together in San Francisco to answer the question they get asked most: how does the Amp team work? They walk through a week at Amp, from Thorsten's Sunday post and the single Monday meeting to writing down goals in silence. They explain why Amp has no quarterly goals, no departments and no territory, and how feature flags and the work in progress, orb good and orb bad channels keep a team of 21 in sync. They also cover reviewing changes with agents, pushing to main without mandatory code review, and why they think more companies will soon work like this.

Quinn and Thorsten record a late-night Hot Take Thursday. They start with a company that capped each engineer at €50 of tokens a week, then talk about why cheap models end up costing more and why some people will be priced out of frontier models. They explain how agents now ship, monitor and fix production, not just write code, and why code review and other old processes get in the way. They also cover not waiting on your agents, simple evals in Orbs, why Amp has runners, and the hot takes Thorsten left out of his post.

Quinn and Thorsten discuss what they can hand off to agents now, from coordinating work across projects to following up with users after a fix ships. They explain how they test agent behavior and use production data to improve performance, then talk about Amp's recent outages and the work to improve reliability. With more of their work happening in Orbs, they ask what the personal computer is still for, and why changing how you work matters as much as changing models.

Quinn and Thorsten predict that intelligence will get cheap and tokens will be everywhere, then ask what that does to software. They debate build versus buy in the age of agents, why Orbs are worth paying for while Thorsten one-shot a bug tracker, and why developers should do X instead of building software to do X. They also explain the two Amps, why building Amp feels like owning a house instead of renting, and how they plan to bring the Amp way to more teams.

This episode was recorded in person in Munich, where the whole Amp team had gathered for a week of building. Quinn and Thorsten discuss why isolated Orbs make it easier to run agents in parallel, how the team asks agents for exhaustive verification, and how production itself can become a feedback loop. They also introduce jellyware: high-quality software that is designed to change quickly. When agents make software more malleable, teams can fix bugs faster and raise the quality bar instead of lowering it.

In the first episode of season 2, Quinn and Thorsten discuss why the Amp team went heads-down the last few months to rebuild Amp around remote-controllable, parallel agents, running locally or in orbs. They also talk about how this shift changed our development workflows and what that means for the future of local development.

Quinn and Thorsten announce that they will kill the Amp editor extension. It will self-destruct soon, because the time of the sidebar is over. 

Quinn and Thorsten are back! It's been a while since they published a Raising An Agent episode and in this this episode, they discuss how everything seems to have changed again with Gemini 3 and Opus 4.5 and what comes after — the assistant is dead, long live the factory.

In this episode of Raising an Agent, Beyang and Camden dive into how the Amp team evaluates models for agentic coding. They break down why tool calling is the key differentiator, what went wrong with Gemini Pro, and why open models like K2 and Qwen are promising but not ready as main drivers. They share first impressions of GPT-5, explore the idea of alloying models, and explain why qualitative "vibe checks" often matter more than benchmarks. If you want to understand how Amp thinks about model selection, subagents, and the future of coding with agents, this episode has you covered.