Welcome to Max Agency, a podcast about how the best AI agents are actually being built. Hosted by Harrison Chase, CEO of LangChain, each episode goes deep with the builders designing, deploying, and learning from real agent systems in the wild. From architecture decisions to evals, tooling, and failure modes, Max Agency is for people who want to understand what it really takes to build useful agents.
Site
RSS
Apple
Classements récents
Dernières positions dans les classements Apple Podcasts et Spotify.
Liens partagés entre épisodes et podcasts
Liens présents dans les descriptions d'épisodes et autres podcasts les utilisant également.
The best AI agents cost less than you think | Eno Reyes, Factory
jeudi 16 juillet 2026 • Durée 01:17:32
Eno Reyes is the co-founder and CTO at Factory, a $1.5 billion company turning signal into deployed code inside some of the world's biggest engineering orgs. Before founding Factory in 2023, he was an engineer at Microsoft and then Hugging Face. In this conversation, Eno unpacks why the harness matters more than the model running underneath it, how to build your own 24/7 software factory, and why he's "bullish on humans in the loop for a very long time.”
–
We also discuss:
Why product management isn't going away
The engineer who lint-checks Factory's own agents
Why coding agents might become the best general agents
The platonic representation hypothesis
Why Factory might hide when "memory" is happening
Building Factory's universal meta harness
Tokenomics, and how routing cuts the bill
–
Timestamps:
(00:00) Introduction
(01:19) What a 24/7 autonomous software factory actually means
(03:16) Why product management isn't going away
(06:56) Alvin, the engineer who lint-checks Factory's own agents
(10:16) "It makes me very bullish on humans in the loop for a very long time"
(11:37) The Disney Epcot analogy for rolling out AI
(16:47) Why coding agents might become the best general agents
(20:54) The case against a model-independent harness, and Eno's counter
(25:44) The platonic representation hypothesis explained
(32:42) Why model quirks are like being left or right-handed
(39:28) Why you could technically decompile Factory's entire harness
(44:20) Why memory might be AI's most overused word
(46:47) Inside AutoWiki and its Lore feature
(55:32) Agent readiness: the deterministic feedback agents need
(57:12) Missions: Factory's universal meta harness
(1:01:12) "It's kind of turtles all the way down": validating the validators
(1:04:37) Tokenomics: what missions cost, and how routing cuts the bill
(1:11:08) Why Eno is bullish on open models
(1:14:30) BenchBench, and why code review benchmarks might be broken
The best AI agents are simpler than you think | Ben Tannyhill, LangChain
jeudi 2 juillet 2026 • Durée 50:13
Ben Tannyhill is a product manager at LangChain, where he's building LangSmith Engine—an agent that finds and fixes your agent's failures. Engine continuously analyzes your production traces, clusters them into actionable issues, and opens pull requests to fix them. Engine's architecture is a lot like an org chart: a main model delegating to a team of cheaper, faster sub-agents. It launched in public beta at Interrupt 2026, and in this conversation, Ben unpacks why it uses a sandbox as a tool, how the team turned it into a self-improving agent that learns from its own traces, and the hard problem of testing a fix before it ships.
–
We also discuss:
Why Engine is "the agent for agent engineers"
Making LangSmith agent-native with condensed trace views
Why the team keeps handing more control to the agent
Inside Engine's four sub-agents: the screener, verifier, and more
Giving Engine memory with an agent overview document
How to keep an always-on agent from blowing the inference budget
Where Insights, Polly, and Engine are converging
–
Timestamps:
(00:00) Introduction (01:25) LangSmith 101 (02:22) Why Engine is "the agent for agent engineers" (03:49) Under the hood: Engine is a deep agent (06:08) Clustering millions of traces with condensed views (10:10) Why the team keeps handing more control to the agent (13:21) Why Engine uses a sandbox as a tool (14:11) Engine's four sub-agents and the org-chart analogy (16:51) Evals for Engine: IssueBench, Harbor, and synthetic environments (23:05) How Engine evolved: from noisy PRs to an issue inbox (25:56) Inside Engine's memory: the agent overview document (29:25) How to keep an always-on agent from blowing the inference budget (30:52) What models Engine uses (31:30) How Engine was rolled out: from Forge to public beta at Interrupt (34:18) Inside the two teams building Engine (35:53) Where Insights, Polly, and Engine are converging(40:06) The missing piece: testing a fix before it ships(42:22) Running a branched agent, and the write-access eval problem(46:35) Using Engine as long-term memory(47:39) Pointing Engine at coding-agent traces(48:49) Running Engine on Engine: the meta self-improvement loop
The best AI agents are simpler than you think | Zack Reneau-Wedeen, Sierra
jeudi 18 juin 2026 • Durée 01:27:25
Zack Reneau-Wedeen is the Head of Product at Sierra, the conversational AI platform behind customer-facing agents for most of the Fortune 20. Before Sierra, he spent seven years at Google as the founding PM for Google Lens and Google Podcasts, then led product at Robinhood and CoinTracker. Sierra is mostly known for customer support, but Zack reveals how and why the company is building agents that span the entire customer lifecycle, from browsing and booking to sales and loyalty. In this conversation, he argues agentic commerce will be bigger than e-commerce, explains why he's a "monolith loyalist", and unpacks why, when a model looks dumb, the problem is usually you.
–
We also discuss:
How Sierra's no-code layer compiles down to agent code, and back again
Why most multi-agent systems just ship your org chart
Inside Sierra's modular voice architecture: thinking, listening, and talking in parallel
Why Sierra built a PCI-certified stack for voice payments
How outcome-based pricing aligns incentives
Why there's no breakout memory company
–
Timestamps:
(00:00) Introduction
(03:39) Analyze, build, release: how you build on Sierra
(07:54) Inside Ghostwriter
(11:04) Meeting models on their turf “80% of the time
(17:47) The one constraint Claude Code doesn't have
(19:35) Agent-to-agent: when an API call still beats MCP
(21:02) Why agentic commerce will be bigger than e-commerce
(27:31) Running models in parallel and ensembling transcription
(32:22) Inside the Agent Data Platform
(40:00) Context engineering: everything it needs, nothing more
(41:38) "Whenever you think the model's too dumb, the model's actually too smart"
The tool design tricks behind Benchling's AI agents | Nick Larus-Stone
jeudi 4 juin 2026 • Durée 50:32
Nick Larus-Stone is the Head of AI at Benchling, the R&D data platform that life science companies use to store and manage their experiments, samples, instruments, and analysis. Benchling has been around for since 2012. In October 2025, it launched Benchling AI, an intelligence layer with a chat interface, backed by an agent, that helps scientists find data, design experiments, and write reports. Nick came to Benchling through its acquisition of Sphinx Bio, the analysis startup he founded. In this conversation, Nick walks through what it takes to build agents for scientific work, and where the playbook from coding agents holds up and where it breaks down.
–
We also discuss:
Why Benchling invests so heavily in getting clean data upfront
How they cross-check answers between models to get more out of each one
Why and how Benchling leans on production traces
Where AI actually helps science today, and where it still gets stuck
Why understanding LLMs is closer to biology than software engineering
–
Timestamps:
(00:00) Intro
(01:22) What Benchling AI is, and the 14-year data platform underneath it
(04:36) Why a decade of structured data is a core advantage
(05:57) The architecture under the hood
(08:28) Similarities and differences compared to a coding harness
(11:14) Benchling’s multi-agent architectures
(14:36) Dealing with verifiable vs non-verifiable tasks
(16:19) Doing evals when clean benchmarks aren’t possible
(18:13) Context engineering: SQL vs. file-based harnesses
(22:11) Memory: agents that create and update their own skills
(25:30) What user education for scientists looks like
How Cogent builds AI agents that have to be right every single time | Geng Sng (Co-founder & CTO - Cogent)
vendredi 22 mai 2026 • Durée 01:14:57
Geng Sng is co-founder and CTO of Cogent, which builds autonomous agents that remediate vulnerabilities for enterprise security teams. Today, Cogent's agents process billions of security events per day, maintaining a live context graph of every asset and vulnerability across customer environments. In this conversation, Geng walks through Cogent's hot vs cold context split, the sub-agents that handle side quests, and the two graphs they run in parallel.
–
We also discuss:
Why defensive security is harder for AI than offensive
Under the hood of Cogent's three agents
Inside Cogent's “read only” by-default sandboxes
Why graph databases don't scale for security data
Cogent Research and the move into formal verification
Why interactive agents need a deeper planning phase to one-shot
How Ramp built an AI agent that can think outside of tokens | Alex Shevchenko
jeudi 7 mai 2026 • Durée 44:06
Alexander Shevchenko is the head of applied research at Ramp, where he leads Ramp Labs – the team behind Ramp Sheets and a steady stream of public AI engineering experiments. Ramp Sheets started as an internal process mining tool that turned Loom videos of accountants into Markov diagrams, before evolving into the agentic spreadsheet editor that shipped in November. In this conversation, Alex walks through the architecture under the hood, why Ramp biases the agent toward Excel formulas over Python code gen, and two recent Labs experiments: Latent Briefing and a user-steerable revival of Golden Gate Claude.
We also discuss:
Under the hood of Ramp Sheets
Inspect, Ramp's internal coding agent, and the self-improving monitor loop it powers
Why finance professionals rejected code gen as too "black box"
Why Anthropic models tend to excel at agentic spreadsheet manipulation
The case for putting the agent outside the sandbox, not inside it
The Loom-to-Markov-diagram process mining pipeline
RLMs and how subagents can share memory in latent space
Latent Briefing and KV-cache communication between subagents
Reviving Golden Gate Claude with steering vectors on Gemma
How Listen is building a system of AI Agents & subagents for specialized tasks | Florian Juengermann, CTO
jeudi 23 avril 2026 • Durée 47:37
Florian Juengermann is the co-founder and CTO of Listen, an AI startup that turns qualitative research across hundreds of interviews, surveys, and focus groups into structured, traceable insights. Listen's agents analyze responses at scale, and Florian has rearchitected the system multiple times to get there. In this conversation, he walks through the virtual table architecture at the core of their Research Agent, how small models run map-reduce classification across thousands of open-ended responses, and the self-reviewing feedback subagent that catches errors during long async runs.
We also discuss:
The three agents inside Listen's platform
How Listen rearchitected from a simple RAG bot to a multi-agent system multiple times
Why the PowerPoint subagent was completely rebuilt using Claude's code SDK
Contextual prompt engineering as an alternative to skills
How Listen keeps report numbers live as new interview responses come in
When to trigger the long-running agent vs. showing early results
What Florian looks for when hiring agent engineers
How Hex builds AI agents that reason like human data analysts | Izzy Miller, AI Engineer
jeudi 9 avril 2026 • Durée 01:08:20
Izzy Miller is an AI engineer at Hex, an AI analytics platform that was one of the first companies to ship data agents to real paying users. Today, Hex runs a multi-agent system with nearly 100K tokens of tools, and Izzy is building a 90-day simulation to evaluate whether those agents actually get smarter over time. In this conversation, he walks through the harness decisions that shaped their architecture, the failure modes Hex is seeing at scale, and what it takes to build an eval that no current model can pass.
We also discuss:
Why data agents are harder to verify than coding agents
Welcome to Max Agency, the podcast that goes deep into how the best agents are being built by builders like you. I'm Harrison Chase, CEO of LangChain, the agent engineering company, and I'll be your host.
Send feedback or questions to maxagency@langchain.dev
Timestamps:
(01:35) Where Hex's notebook agent started
(03:46) The moment Hex knew it was time for agents
(07:36) Why data agents are harder to verify than coding agents
(09:30) How Hex is unifying separate agents
(13:28) Under the hood of the notebook agent
(15:41) The harness features that are now holding the agent back
(17:41) Why Hex built their own orchestrator
(18:59) Managing nearly 100K tokens of tools
(20:49) Ephemeral queries and agent behavior trade-offs
(24:46) The UX problem with showing agents' thinking
(27:28) Why verification is harder than transparency for data agents
(31:00) Memory, context conflicts, and collapse modes
(34:38) How Hex built their internal eval system
(39:29) Why most eval sets are bad
(44:30) The 900% quota eval that every model fails
(46:55) Model upgrades and the "in distribution" debate
(51:34) How Izzy went from marketer to AI engineer
(59:59) The 90-day simulation for long-horizon evals
Apple Podcasts
🇫🇷 France - technology
22/07/2026
#93
🇫🇷 France - technology
23/04/2026
#76
🇩🇪 Allemagne - technology
22/04/2026
#95
🇫🇷 France - technology
22/04/2026
#100
🇫🇷 France - technology
19/04/2026
#90
🇬🇧 Grande Bretagne - technology
18/04/2026
#89
🇩🇪 Allemagne - technology
18/04/2026
#94
🇨🇦 Canada - technology
17/04/2026
#78
🇬🇧 Grande Bretagne - technology
17/04/2026
#49
🇩🇪 Allemagne - technology
17/04/2026
#63
Spotify
Aucun classement récent disponible
Podcasts Similaires Basées sur le Contenu
Découvrez des podcasts liées à Max Agency. Explorez des podcasts avec des thèmes, sujets, et formats similaires. Ces similarités sont calculées grâce à des données tangibles, pas d'extrapolations !
