Raising An Agent

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.