Chain of Thought | AI Agents, Infrastructure & Engineering

Conor Bronsdon

AI is reshaping infrastructure, strategy, and entire industries. Chain of Thought is the podcast where builders reason through what's changing. Host Conor Bronsdon sits down with the engineers and founders shipping AI in production to get past the hype into what's working and what isn't. Episodes cover model infrastructure, inference, agent frameworks, evaluation, and developer tools. Guests have come from NVIDIA, Google DeepMind, AMD, Databricks, Vercel, and more. Every episode carries a full transcript and show notes at chainofthought.show. New episodes weekly. Conor Bronsdon is an independent consultant and angel investor in AI infrastructure and developer tools. He led technical ecosystem at Modular, acquired by Qualcomm in 2026; led developer awareness at Galileo, acquired by Cisco; and ran developer marketing at LinearB, where he was GM of the Dev Interrupted podcast and community. Views expressed by the host and guests are their own.

  1. 4d ago

    Agents Are Overtaking Humans in Search: Why Search Must Be Rebuilt

    Saahil Jain joined You.com as a founding engineer in 2020, when it was a consumer search engine competing with Google. Now its CTO, he builds search for AI agents, and he argues that however smart models get, they will still need tools to find out what is happening in the world. His analogy: we built the self-driving cars before the roads. He walks through which work he expects to move inside the model, why better models made harnesses matter less, and why cheaper open models and routing are giving harnesses a new job. He says he changed his mind on that last point in the past few months. Then we get into how agents search differently than people do: thousands of queries at once, recall over ranking, and a much wider range of latency needs. Saahil traces a query from fan-out to the index to re-ranking, and explains why You.com judges search by whether the agent answered the question, and why he trusts customer evals and benchmarks that change over time more than static public ones. We cover: - Core intelligence versus augmented intelligence, and the self-driving cars that arrived before the roads- Which tasks Saahil expects models to absorb, and where unverifiable rewards slow them down- Why frontier labs keep going vertical while open-model labs give weights away- How stronger models shrank the gap between good and bad harnesses, and how routing across open models can revive them- How You.com post-trains models with its search tool while trying not to overfit to any one model- How agent search differs from human search: query volume, context, ranking and latency- The life of a query: subqueries, lexical and semantic indexes, re-ranking and enrichment- Why static benchmarks can be memorized, and what dynamic benchmarks and customer evals measure instead Mentioned in this episode:- I Paid an AI Agent $8 to Write About its ‘Life’: https://newsletter.chainofthought.show/p/i-paid-an-ai-agent-8-to-write-about- MotionBench: https://motionbench.sh Connect with Saahil Jain: - LinkedIn: https://www.linkedin.com/in/saahiljain/- Twitter/X: https://x.com/saahil9jain- You.com: https://you.com- You.com API docs: https://you.com/docs/quickstart Connect with Chain of Thought host Conor Bronsdon:Newsletter: https://newsletter.chainofthought.show/Twitter/X: https://x.com/ConorBronsdonLinkedIn: https://www.linkedin.com/in/conorbronsdon/YouTube: https://www.youtube.com/@ConorBronsdon More episodes: https://chainofthought.show Chapters:(0:00) Agents run a thousand searches at once(0:25) What survives as AI models get smarter(1:47) Is this the singularity?(4:26) Core intelligence versus augmented intelligence(6:33) Self-driving cars before the roads(7:27) What belongs inside the model(11:00) Where verifiable rewards run out(12:16) Can agents form relationships?(16:58) What model labs own, and what independents can build(20:21) What a harness is(22:39) The model is eating the harness(23:14) Open models and routing revive the harness(25:32) Open versus closed: what the labs keep(31:30) OpenAI, Baseten and the enterprise model budget(33:53) Co-evolving a search tool with the model labs(37:41) How agent search differs from human search(42:42) Life of a query, from fan-out to index(47:22) Measuring retrieval by whether the agent answered(50:21) Static benchmarks, freshness and customer evals(54:19) Why he changed his mind on harnesses Thanks to Walrus, presenting sponsor of season four of Chain of Thought. Walrus Memory gives AI agents portable, verifiable memory that carries context across apps, sessions, and other agents. Get started at https://walrus.xyz/cot Thanks to CoralBricks for sponsoring this episode. CoralBricks serves open models through one API, fast and at low cost: DeepSeek V4.1 Flash streams at over 300 tokens a second. Get $5 in credits on signup, plus another $5 on your first purchase: https://www.coralbricks.ai/r/Z6V2RE Thanks to Inngest, presenting sponsor of season four of Chain of Thought. Agents in production run long: they call models and wait on APIs and people. But the longer agents run, the more they break. Inngest handles that with durable execution. You build your agent as steps in TypeScript, Python, or Go. When a step fails, Inngest retries it with exponential backoff, and completed steps are saved and skipped. Try it out: https://inngest.link/cot-pod Thanks to WisdomAI for sponsoring this episode. In WisdomAI's latest benchmark, Claude Code alone topped out at 73% accuracy; WisdomAI closed the gap, delivering accurate answers 3x faster at about a third of the cost. Get "The Blueprint for Trusted AI Analytics": https://wisdom.ai/benchmark

    Agents Are Overtaking Humans in Search: Why Search Must Be Rebuilt
  2. Oct 29

    How Cisco Secures Personal AI Assistants for 90,000 Employees | DJ Sampath

    Cisco is giving each of its 90,000 employees a personal AI agent. Some of those same employees are already connecting agents from outside the security boundary without asking IT. DJ Sampath, SVP and GM of AI Software and Platform at Cisco, walks through what had to be in place before the rollout: scanning every prompt, sandboxing each agent, keeping agents multi-tenant, scanning the skills and tools people bring in, and settling which identities an agent may act as. New episodes, the ideas behind them and Conor's essays land in the Chain of Thought newsletter first. Subscribe: https://newsletter.chainofthought.show/ We recorded at Cisco's San Francisco office, a block or two from OpenAI, where Cisco was an early Codex design partner. DJ explains how engineers rework their skills files with each model generation, how per-engineer PR bots review agent-written code, and why defenders now have to move at agent speed when an exploit can show up within minutes of a CVE going public. We cover: What Cisco's IT team required before rolling out MyAgent to 90,000+ employeesPrompt injection by email, and why the first integration everyone makes is the riskiestCisco's AI security taxonomy, DefenseClaw, and Project Quarry, a new open source language for describing agent behavior and policyHow the agents are actually used: daily briefs, meeting actions, live dashboards, 2 trillion tokens in a single weekWhy skills files need refactoring every model generationDiscovering and governing shadow agents with zero trust accessMulti-model code review, spec drift, and evals built from pull request tracesHow Cisco Cloud Control was built in about eight months with agentic codingChapters:(0:00) Guardrails tested inside Fortune 100 companies(0:21) Securing 90,000 employee AI agents(8:04) Cisco's open source agent security stack(12:01) Project Quarry: a policy language for agents(17:07) Personal agent use cases at Cisco(19:08) Early design partner on Codex(23:15) Reassessing workflows each model generation(27:27) Shadow agents and zero trust access(30:29) Security as an adoption accelerator(31:39) Multi-model code review for dependability(36:09) Defenders moving at agent speed(41:04) How Cisco Cloud Control was built Connect with DJ Sampath: X: https://x.com/djsampathLinkedIn: https://www.linkedin.com/in/djsampath/DJ on Cisco Blogs: https://blogs.cisco.com/author/djsamProject Quarry: https://blogs.cisco.com/ai/project-quarry-agent-security-detectionsCisco: https://www.cisco.com/Related episode: Cisco President and CPO Jeetu Patel, "Parenting Your AI Agents for Best Results": https://share.transistor.fm/s/43e97aa6 Connect with Chain of Thought host Conor Bronsdon: Newsletter: https://newsletter.chainofthought.show/Twitter/X: https://x.com/ConorBronsdonLinkedIn: https://www.linkedin.com/in/conorbronsdon/YouTube: https://www.youtube.com/@ConorBronsdonMore episodes: https://chainofthought.show Thanks to Inngest, presenting sponsor of season four of Chain of Thought. Agents in production run long: they call models and wait on APIs and people. But the longer agents run, the more they break. Inngest handles that with durable execution. You build your agent as steps in TypeScript, Python, or Go. When a step fails, Inngest retries it with exponential backoff, and completed steps are saved and skipped. Try it out: https://inngest.link/cot-pod Thanks to Walrus, presenting sponsor of season four of Chain of Thought. Walrus Memory gives AI agents portable, verifiable memory that carries context across apps, sessions, and other agents. Get started at https://walrus.xyz/cot Thanks to WisdomAI for sponsoring this episode. In WisdomAI's latest benchmark, Claude Code alone topped out at 73% accuracy; WisdomAI closed the gap, delivering accurate answers 3x faster at about a third of the cost. Get "The Blueprint for Trusted AI Analytics": https://wisdom.ai/benchmark Thanks to Svix, presenting sponsor of season four of Chain of Thought. Svix delivers billions of reliable webhooks for startups and the Fortune 500. Get started at https://link.svix.com/cot. Qualified startups get $12,000 in credits, and YC companies get $50,000.

    How Cisco Secures Personal AI Assistants for 90,000 Employees | DJ Sampath
  3. Oct 25

    For AI Agent Fleets, the Model Is Rarely the Bottleneck | Theory Ventures' Andy Triedman

    Andy Triedman is a partner at Theory Ventures, and he is building his own software factory, while assessing how startups are leveraging theirs. His read after running agent fleets: the models are frankly good enough for most of the work. The vast majority of things you'd ask an agent to do are not intelligence limited. They are context limited. We have infrastructure work to do - but we can be more ambitious! Full transcript and chapters: https://chainofthought.show/podcast/79-for-ai-agent-fleets-the-model-is-rarely-the-bottleneck-theory-ventures-andy-triedman/ So the hard part moves upstream. Deciding what the agents should build, what they need to know, and when they should stop and ask a person is now most of the job. We cover: Moving from solving one problem at a time to building systems that solve whole classes of problems, like generating and testing integrationsWhich tasks still need human approval, and which can be fully handed offWhy a short feature spec leaves too much unsaid, and how better questions up front cut review interruptionsKeeping shared context and company decisions current, because an agent takes everything it reads as trueInference ROI, and when well-scoped tasks can go to cheaper modelsSandboxes and simulated customer environments for agentsFirst steps for teams: shared skills, cloud agents and approval gatesProtecting customer data, and organizing agent memory from session traces to company prioritiesNew episodes, the ideas behind them and Conor's essays land in the Chain of Thought newsletter first. Subscribe: https://newsletter.chainofthought.show/ Chapters:(0:00) Agents are context limited, not intelligence limited(0:34) From coding agents to software factories(5:53) What still needs human approval(10:16) Agent loops that improve the product on their own(14:52) Where agent automation breaks down(17:59) The bitter lesson and engineering as experimentation(20:08) From writing code to directing agent fleets(24:18) Shared context and stale decisions(27:25) Inference ROI and cheaper models(30:23) Moving human time from code to customer intent(34:42) Sandboxes and simulated customer environments(37:26) First steps: shared skills and cloud agents(40:14) Protecting customer data and isolating agents(42:32) Context limits and hierarchical agent memory(47:05) What Theory Ventures looks for in founders Connect with Andy Triedman: LinkedIn: https://www.linkedin.com/in/andy-triedman/Andy at Theory Ventures: https://theoryvc.com/team-members/andy-triedmanTheory Ventures: https://theoryvc.com/Connect with Chain of Thought host Conor Bronsdon: Newsletter: https://newsletter.chainofthought.show/Twitter/X: https://x.com/ConorBronsdonLinkedIn: https://www.linkedin.com/in/conorbronsdon/YouTube: https://www.youtube.com/@ConorBronsdonMore episodes: https://chainofthought.show Thanks to Svix, presenting sponsor of season four of Chain of Thought. Svix delivers billions of reliable webhooks for startups and the Fortune 500. Get started at https://link.svix.com/cot. Qualified startups get $12,000 in credits, and YC companies get $50,000. Thanks to Walrus, presenting sponsor of season four of Chain of Thought. Walrus Memory gives AI agents portable, verifiable memory that carries context across apps, sessions, and other agents. Get started at https://walrus.xyz/cot Thanks to Inngest, presenting sponsor of season four of Chain of Thought. Agents in production run long - they call models and wait on APIs and people. But the longer agents run, the more they break. Inngest handles that with durable execution. You build your agent as steps in TypeScript, Python, or Go. When a step fails, Inngest retries it with exponential backoff, and completed steps are saved and skipped. Try it out: https://inngest.link/cot-pod Thanks to G2i for sponsoring this episode - for over a decade, they vetted and placed engineers at other companies, from startups to FAANG. Two years ago, they turned that same judgment inward, building their own bench to review RL environments, evals, and training data that models are trained on. Get access: https://fandf.co/3SFxVm6

    For AI Agent Fleets, the Model Is Rarely the Bottleneck | Theory Ventures' Andy Triedman
  4. Oct 14

    What Breaks When Agents Become the Customer | Svix CEO Tom Hacohen

    What breaks when agents become the customer? Most of the integration layer, APIs, SDKs and webhooks alike, was built for human developers and for servers that are always listening. Agents are neither. Full transcript and chapters: https://chainofthought.show/podcast/78-what-breaks-when-agents-become-the-customer-svix-ceo-tom-hacohen/ When an agent runs on a laptop, closing the lid takes down the tunnel its webhooks come through. When the lid opens, it gets a storm of retries from 12 hours earlier. Svix founder and CEO Tom Hacohen's answer is to let the agent poll for what it missed. Svix delivers webhooks for companies like Clerk and Resend, and it created Standard Webhooks, the spec OpenAI, Anthropic and Google Gemini have adopted. In this episode of Chain of Thought, Tom joins Conor Bronsdon to talk through designing APIs for agents that adapt, whether agents still need SDKs, and why he wants less code even when agents write it. He also introduces Poke, Svix's new spec for making event-driven APIs work for agents. This episode is sponsored by Svix. We cover: Why events are harder for agents than API calls: the sender controls them, and they arrive outside the agent's sessionHow polling endpoints and Svix's plugins for Hermes and OpenClaw let an agent pick up where it left offWhy Tom calls JSON an abomination and webhooks duct tape, and why worse is better anywayWhy Svix created Standard Webhooks when everyone implemented webhooks differently, and how the spec let Kong and ngrok add webhook verificationWhether agents still need SDKs, and why Svix's skills work like a solutions engineer while its docs stay written for humansWhy Tom wants less code even when agents write it, and what piling patches on patches costsPoke, Svix's early spec for letting agents subscribe to and trigger events across services, released so feedback can shape it while it's still malleableChapters:(0:00) Duct tape, retry storms and the case for simplicity(1:19) Why integrations got easier and harder at once(2:59) How EteSync's webhook requests led to Svix(5:22) Worse is better: why webhooks persist(7:15) What changes when an agent receives the event(9:07) What happens when the laptop closes(11:08) Hermes, OpenClaw and agents that poll(13:03) Letting agents choose their own subscriptions(14:42) The long tail of the web without APIs(18:38) Why Svix created Standard Webhooks(24:17) How Standard Webhooks is governed(26:16) Following real usage, including MCP(28:17) Designing APIs for agents that adapt(30:38) Do agents still need SDKs?(31:25) Skills as documentation for agents(34:52) Less code, even when agents write it(36:19) Agentic development and the offshoring analogy(37:34) Software factories and the plumbing underneath(40:57) Keeping up while the standards change(44:18) What Svix is launching with Poke(46:39) Why Svix released the Poke spec early(47:58) Building for your customers' customers(49:38) Clerk, Resend and webhooks in the background(52:22) Where to follow Tom Links from the episode: Svix: https://link.svix.com/cotPoke: https://www.svix.com/poke/Standard Webhooks: https://www.standardwebhooks.comStandard Webhooks on GitHub: https://github.com/standard-webhooks/standard-webhooksEteSync: https://www.etesync.comssot-check: https://github.com/conorbronsdon/ssot-checkMost of the Web Will Never Get APIs for AI Agents | Dhruv Batra: https://chainofthought.show/podcast/63-most-of-the-web-will-never-get-apis-for-ai-agents-dhruv-batra/Connect with Tom Hacohen: LinkedIn: https://www.linkedin.com/in/tomhacohen/X: https://x.com/TomHacohenSvix: https://link.svix.com/cotConnect with Chain of Thought host Conor Bronsdon: Newsletter: https://newsletter.chainofthought.show/Twitter/X: https://x.com/ConorBronsdonLinkedIn: https://www.linkedin.com/in/conorbronsdon/YouTube: https://www.youtube.com/@ConorBronsdonMore episodes: https://chainofthought.show Thanks to Svix, presenting sponsor of season four of Chain of Thought. Svix delivers billions of reliable webhooks for startups and the Fortune 500. Get started at https://link.svix.com/cot. Qualified startups will get $12,000 in credits, $50,000 for YC companies.

    What Breaks When Agents Become the Customer | Svix CEO Tom Hacohen
  5. Oct 7

    Switching Models Shouldn't Mean Starting Over | Walrus Protocol's Kimberly Logan

    If your agent's memory lives inside one model provider, switching models or harnesses means starting over. You need portable memory - yet when switching agent memory between models, you can swing accuracy by thirteen points or more, depending on which model reads them back. Full transcript and chapters: https://chainofthought.show/podcast/77-switching-models-shouldnt-mean-starting-over-walrus-protocols-kimberly-logan/ Kimberly Logan, Head of Product at the Walrus Foundation, where she builds Walrus Memory, joins Chain of Thought to discuss how to build portable and verifiable memory for AI agents - and why Walrus's decentralized storage network has proved an apt primitive. She and host Conor Bronsdon get into why model lock-in is a memory problem, what people use agent memory for beyond coding, how you prove what happened to your data, and why Walrus doesn't publish memory quality benchmarks, plus more. This episode is sponsored by Walrus. We cover: Why longer context windows don't help once you switch models or harnesses, and why an import function only fixes one point in timeWhy Kimberly doesn't benchmark Walrus Memory against memory startups, and why she sees the opportunity as bigger than memory aloneWhat people build with Walrus Memory besides coding agents, which Walrus puts at maybe 30% of usage: long-running study aids, trading agents, and security teams comparing production snapshots with code changesWalrus's figure that almost 85% of the memories written are read back more than 30 days laterHow attestations on the blockchain and a delegate key you control let you show what happened to your data, and why unchanged data still isn't proof that it's accurateWhy Kimberly treats recall quality and latency as table stakes, and how a knowledge graph keeps recall on the freshest memoriesWhy she left almost 20 years in traditional software, including seven at Google, for a blockchain company, and where shared memory across companies and trust boundaries goes nextWalrus Console, announced this week: one place to manage agent memories and files through an interface or an MCP connection, without knowing how the storage underneath is configuredConnect with Kimberly Logan: LinkedIn: https://www.linkedin.com/in/krlgn/Twitter/X: https://x.com/kimblgnWalrus: https://walrus.xyz/cotConnect with Chain of Thought host Conor Bronsdon: Newsletter: https://newsletter.chainofthought.show/Twitter/X: https://x.com/ConorBronsdonLinkedIn: https://www.linkedin.com/in/conorbronsdon/YouTube: https://www.youtube.com/@ConorBronsdon🔗 More episodes: https://chainofthought.show Chapters:(0:00) Why agent memory has to move with you(1:25) Context windows don't follow you to a new model(4:41) Why an import function doesn't fix lock-in(6:38) Why Walrus isn't competing head-on with memory startups(8:39) Where Walrus Memory goes next(10:38) Trading agents and security snapshots on Walrus Memory(14:44) Verifiability: answering what happened to your data(17:21) Fresh recall, and why Walrus doesn't publish memory benchmarks(20:22) From traditional software to a blockchain company(24:40) A record other companies and regulators can check(25:42) What Walrus Console is for(29:09) Use agent memory beyond coding agents(30:52) Plugging in your own agent stack(31:41) Memory across companies and trust boundaries(35:48) Closing thoughts Thanks to Walrus, presenting sponsor of season four of Chain of Thought. Walrus Memory gives AI agents portable, verifiable memory that carries context across apps, sessions, and other agents. Get started at https://walrus.xyz/cot #AI #AIAgents #AgentMemory #SoftwareEngineering #DevTools

    Switching Models Shouldn't Mean Starting Over | Walrus Protocol's Kimberly Logan
  6. Oct 5

    Your Best AI Engineer Might Have the Worst Metrics | Sonar CTO Andrea Malagodi

    Andrea Malagodi is CTO at Sonar, which builds AI code verification and governance tools. When finance asked about the size of his team's AI bills, he calculated cost per PR. At one extreme was an engineer with more than 500 PRs in a short period and a low cost per PR. At the other was an engineer with very high spend and very few PRs. Full transcript and chapters: https://chainofthought.show/podcast/76-your-best-ai-engineer-might-have-the-worst-metrics-sonar-cto-andrea-malagodi/ Judged on cost alone, the first engineer wins and the second looks like a problem. Malagodi looked closer. The first had built a personal agent factory, with specification, design review, documentation records, coding, verification and functional testing, and about two-thirds of the output was tests and validations. The second was working on a hard problem that needed the AI to reason through long, multi-turn sessions and didn't reduce to a line count. Numbers alone tell you something, but not which engineer was doing the more valuable work. We cover: Why cost per PR is becoming the industry's standard AI spend metric, and how Malagodi's 500-PR engineer and high-spend engineer broke itThe history of bad proxies, from lines of code to story points to token leaderboards, and why Malagodi says the people who removed code were often the most importantSonar's guide, verify, solve loop: Vortex for codebase context, algorithmic plus LLM-based PR analysis, a remediation agent for legacy debt, and the Hunter agent for security vulnerabilitiesWhy Malagodi breaks agent work into small pieces, and why a five-day session that produces 400,000 lines of code leaves you with no idea what is in your codebaseSetting up disagreement between agents with an orchestrator and personas for engineering, product management and quality, plus Conor Bronsdon's cross-model-family review setupRolling AI tools out at enterprise scale: one cost view for finance, up to 30% savings from cutting repeated context reads, and why budgets as small as $50 a week are hard to work withRotating a triage duty to protect deep work, including how Sonar's teams built skills to sort through hundreds of reported CVEs, a number of them likely false positivesNew episodes, the ideas behind them and Conor's essays land in the Chain of Thought newsletter first. Subscribe: https://newsletter.chainofthought.show/ Chapters:(0:00) Human reviewers rubber-stamp big AI changes(2:43) Learning the craft alongside AI tools(9:09) From lines of code to PR counts(12:17) Spreading top engineers' setups org-wide(16:50) The guide, verify, solve agent loop(22:51) Specialized agent lanes and multitasking limits(26:51) Clear asks and guardrails for agent coordination(30:29) Building disagreement between agents(34:59) Mixing models instead of picking one(39:46) Rolling out AI tooling at enterprise scale(46:19) Defense in depth for AI-written code(50:52) Protecting time for incident investigations(54:08) Personalized software for teams and individuals Links from the episode: Sonar Vortex research: https://www.sonarsource.com/blog/cut-your-coding-agents-cost-with-sonar-semantic-code-navigation/SonarQube Hunter Agent: https://www.sonarsource.com/products/sonarqube/hunter-agent/Connect with Andrea Malagodi: LinkedIn: https://www.linkedin.com/in/malagodia/Sonar: https://www.sonar.com/Connect with Chain of Thought host Conor Bronsdon: Newsletter: https://newsletter.chainofthought.show/Twitter/X: https://x.com/ConorBronsdonLinkedIn: https://www.linkedin.com/in/conorbronsdon/YouTube: https://www.youtube.com/@ConorBronsdonMore episodes: https://chainofthought.show Thanks to Svix, presenting sponsor of season four of Chain of Thought. Svix delivers billions of reliable webhooks for startups and the Fortune 500. Get started at https://link.svix.com/cot. Qualified startups get $12,000 in credits, and YC companies get $50,000. Thanks to Walrus, presenting sponsor of season four of Chain of Thought. Walrus Memory gives AI agents portable, verifiable memory that carries context across apps, sessions, and other agents. Get started at https://walrus.xyz/cot Thanks to Inngest, presenting sponsor of season four of Chain of Thought. Agents in production run long - they call models and wait on APIs and people. But the longer agents run, the more they break. Inngest handles that with durable execution. You build your agent as steps in TypeScript, Python, or Go. When a step fails, Inngest retries it with exponential backoff, and completed steps are saved and skipped. Try it out: https://inngest.link/cot-pod Thanks to G2i for sponsoring this episode - for over a decade, they vetted and placed engineers at other companies, from startups to FAANG. Two years ago, they turned that same judgment inward, building their own bench to review RL environments, evals, and training data that models are trained on. Get access: https://fandf.co/3SFxVm6

    Your Best AI Engineer Might Have the Worst Metrics | Sonar CTO Andrea Malagodi
  7. Sep 24

    Why Context Alone Isn't Enough for Enterprise AI Agents | WisdomAI CPO Kapil Chhabra

    An AI agent answering questions about your business needs to understand how that business works. How do you calculate churn? When does your fiscal year end? Who has the authority to change those definitions? Connecting a model to company data leaves those questions unresolved. Full transcript and chapters: https://chainofthought.show/podcast/75-why-context-alone-isnt-enough-for-enterprise-ai-agents-wisdomai-cpo-kapil-chhabra/ That’s the work of context engineering: giving agents the business definitions, instructions and examples they need to interpret your data. But that context changes as the business evolves, and someone has to keep it accurate. In this episode of Chain of Thought, WisdomAI co-founder and CPO Kapil Chhabra joins Conor Bronsdon to explain how his team approaches that challenge. We explore how companies maintain shared context, why data teams are taking on the role of AI context engineers, and how a specialized harness plans queries, checks results and repairs errors before returning an answer. Recorded at WisdomAI’s San Mateo office, this episode is sponsored by WisdomAI. We cover: Why the context layer is broader than a semantic layer or catalog, and how it differs from memoryHow context drifts, and why a subject-matter expert has to approve changes to shared definitionsWhy Kapil sees an AI context engineer role emerging, and why data teams are moving from providing insights to providing contextHow WisdomAI's harness decomposes a question, federates queries across data sources and repairs errors, including a customer that replaced a $5M-a-year analytics pipelineThe four ingredients of a trustworthy AI answer: accuracy, consistency, governance and explainabilityLive Apps: governed analytics apps built from a single prompt, and what keeps them liveWhy your context is your IP and should stay portableChapters:(0:00) Do your agents have the right context?(1:56) The four ingredients of trust(5:13) The criticality and impact 2x2(8:12) Data, context, harness: the hospital analogy(11:12) What the context layer actually means(11:48) Specialized harnesses: legal, support, analytics(13:17) Why only 7% of data leaders have scaled AI(15:46) What models can't guess: ARR, churn, fiscal years(16:45) The data stack collapses into the context layer(20:55) Memory vs. context(25:26) Are agents the new users of software?(27:19) Where humans should spend their time(28:14) Commissioning an AI agent, and who verifies it(31:28) Context drift and the learning loop(34:04) Context is a multiplayer game(35:12) Decompose, query, verify, repair(38:47) Replacing a $5M analytics pipeline with federation(42:04) The context development life cycle(43:29) The AI context engineer(46:02) Jobs are changing, not disappearing(46:59) Product, people and process(51:20) Who decides? Why FDEs can't own your context(52:22) Data context vs. business context(54:11) The benchmark: specialized harness vs. general agent(56:08) Meeting users in ChatGPT, Claude and Slack(58:48) Static vs. runtime context(1:00:08) Harness engineering as models change(1:01:44) Right-sizing AI and Live Apps(1:04:42) The boring parts: governance, security, caching(1:06:18) 1,000 dashboards, 50 human-years(1:08:08) What "live" means(1:09:19) Are dashboards going away?(1:12:08) A pipeline app built on a weekend walk(1:15:53) Who owns the apps?(1:17:27) Data teams now provide context, not insights(1:18:56) Building with the WisdomAI MCP(1:19:43) Your context is your IP(1:20:48) Closing thoughts: none of that work goes to waste Links from the episode:Meet the Modern Data Team (WisdomAI CDO report)AI Context Engineer (ACE) certificationLive AppsWisdomAI in ChatGPT WorkAvoid AI Writingssot-checkI Paid an AI Agent $8 to Write About its 'Life'Slack Wants to Be the Context Harness for Code | CPO Jaime DeLangheThe AI Framework Era Is Over: Why Context Is the Moat | Jerry Liu Connect with Kapil Chhabra:LinkedInWisdomAIWisdomAI on X Connect with Chain of Thought host Conor Bronsdon:NewsletterTwitter/XLinkedInYouTube More episodes: https://chainofthought.show Thanks to WisdomAI for sponsoring this episode. WisdomAI is the agentic analytics platform for trusted enterprise intelligence: governed context, an analytics harness that makes every answer consistent and verifiable, and Live Apps built from a single prompt. Try Live Apps: https://wisdom.ai/liveapps

    Why Context Alone Isn't Enough for Enterprise AI Agents | WisdomAI CPO Kapil Chhabra
  8. Sep 22

    AI Codes: Product Engineers Decide What to Build | Laurie Voss, Arize

    Laurie Voss co-founded npm - now head of developer relations at Arize, he argues that engineers will increasingly earn their keep as 'product engineers': understanding what users need and directing AI agents to build it. Full transcript and chapters: https://chainofthought.show/podcast/74-ai-codes-product-engineers-decide-what-to-build-laurie-voss/ One example: a bakery owner who knows how to make a croissant but has no interest in building software. Someone still has to turn that owner's needs into requirements. Laurie sees that work becoming central to product engineering, with cheaper code making software for narrower industries more viable. We discuss where he still sees a need for human code review and operational knowledge, what he would look for in a computer science course if he were starting out today (and what he wouldn't do), and why he compares AI today to the web in 1997. He is optimistic about the technology and skeptical of the valuations, while leaving one question unresolved: how do junior engineers learn the judgment this work demands? We cover: Why the "aha moment" of solving a problem survives even when agents type the codeWhere Laurie still sees a need for human code review, operations, and tacit knowledgeWhether a $15,000 coding bootcamp or a theory-heavy CS degree is still worth itWhy AI in 2026 looks like the web in 1997, and what that says about the bubbleHow AI-generated pull requests burden open source maintainers, and why Laurie expects cheaper code to pressure closed-source business modelsWhy the systems analyst returns as the product engineer, and why that means niche software for bakeries and auto partsWhy Laurie predicts open-model competition and diminishing returns could compress frontier-model marginsHow apprenticeships could help junior engineers develop product judgmentChapters: (0:00) The shift in software jobs(0:44) Why Laurie is optimistic about the code generation explosion(3:06) The aha moment moves from typing code to thinking(5:49) Where agents still need human review and operational knowledge(8:51) Is college still worth it?(9:54) Bootcamps versus theory-heavy CS courses(13:04) We are all product engineers now(15:55) AI is the web in 1997(18:19) Exponential growth, the labs' pause, and npm's ten-year curve(20:07) Barring AGI, AI is a normal technology(21:48) Block's layoffs and companies staying smaller(23:14) What the labor data shows: fewer people, more capital(26:29) Open source as the canary: drowning in AI pull requests(28:11) AI reimplementations and the pressure on software moats(30:26) Personal software and the kill-my-SaaS hackathon(32:32) The bakery and the return of the systems analyst(34:09) Niche software for specific industries(35:36) Bootstrapping and the DevTools opportunity(37:13) What this means for the model companies(38:20) Frontier-model margins and open-model competition(39:53) How the bubble pops: scaling laws and diminishing returns(43:24) Staying private and the trough of disappointment(45:51) Get good at a domain, not the technology(50:44) The missing junior ladder is the question of our time(53:32) Closing thoughts: it's 1997, you can retrain Connect with Laurie Voss: Blog: https://seldo.com/LinkedIn: https://www.linkedin.com/in/seldo/Twitter/X: https://x.com/seldoBluesky: https://bsky.app/profile/seldo.comArize: https://arize.com/Connect with Chain of Thought host Conor Bronsdon: Newsletter: https://newsletter.chainofthought.show/Twitter/X: https://x.com/ConorBronsdonLinkedIn: https://www.linkedin.com/in/conorbronsdon/YouTube: https://www.youtube.com/@ConorBronsdonMore episodes: https://chainofthought.show Thanks to Svix, presenting sponsor of season four of Chain of Thought. Svix delivers billions of reliable webhooks for startups and the Fortune 500. Get started at https://link.svix.com/cot. Qualified startups get $12,000 in credits, and YC companies get $50,000. Thanks to Walrus, presenting sponsor of season four of Chain of Thought. Walrus Memory gives AI agents portable, verifiable memory that carries context across apps, sessions, and other agents. Get started at https://walrus.xyz/cot Thanks to G2i for sponsoring this episode - for over a decade, they vetted and placed engineers at other companies, from startups to FAANG. Two years ago, they turned that same judgment inward, building their own bench to review RL environments, evals, and training data that models are trained on. Get access: https://fandf.co/3SFxVm6 Thanks to Inngest, presenting sponsor of season four of Chain of Thought. Agents in production run long - they call models and wait on APIs and people. But the longer agents run, the more they break. Inngest handles that with durable execution. You build your agent as steps in TypeScript, Python, or Go. When a step fails, Inngest retries it with exponential backoff, and completed steps are saved and skipped. Try it out: https://inngest.link/cot-pod 7Mdv8UhrombOD7fnCVai

    AI Codes: Product Engineers Decide What to Build | Laurie Voss, Arize
5
out of 5
41 Ratings

About

AI is reshaping infrastructure, strategy, and entire industries. Chain of Thought is the podcast where builders reason through what's changing. Host Conor Bronsdon sits down with the engineers and founders shipping AI in production to get past the hype into what's working and what isn't. Episodes cover model infrastructure, inference, agent frameworks, evaluation, and developer tools. Guests have come from NVIDIA, Google DeepMind, AMD, Databricks, Vercel, and more. Every episode carries a full transcript and show notes at chainofthought.show. New episodes weekly. Conor Bronsdon is an independent consultant and angel investor in AI infrastructure and developer tools. He led technical ecosystem at Modular, acquired by Qualcomm in 2026; led developer awareness at Galileo, acquired by Cisco; and ran developer marketing at LinearB, where he was GM of the Dev Interrupted podcast and community. Views expressed by the host and guests are their own.

You Might Also Like