Skip to content

By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.

Latent SpaceLatent Space

Claude Code’s Bitter Lesson: Prompts, Harnesses, Mods, and Agents — Thariq Shihipar, Anthropic

From the rapid rise of Claude Code to a future where agents can rewrite their own harnesses, collaborate across teams, and operate across cloud and local environments, the way we build software is changing extraordinarily fast. In this episode, Anthropic’s Thariq Shihipar joins swyx and Vibhu to unpack how power users are actually working with Claude Code today, why prompting remains a high-skill discipline, and where Anthropic thinks the agent harness is headed next. We go deep on Claude Code’s evolving interface: Ask User Question and elicitation, artifacts as persistent generative interfaces, Claude Tag for multiplayer agent workflows, Projects, model effort, implementation notes, and the new Claude Mods system for customizing the harness itself. Thariq explains why Claude.md may eventually disappear, why the smartest model could also become the cheapest model for many tasks, and why mutable software could become a new paradigm for how applications are built and customized. The conversation then turns to agent security and Anthropic’s “Pacing the Frontier” argument. Thariq walks through recent incidents where agents discovered unexpected ways to communicate, exploit infrastructure, reverse-engineer benchmark scorers, and chain vulnerabilities together. We discuss sandboxing, prompt injection, autonomous agents, interpretability, constitutional classifiers, probes, fallbacks, Auto Mode, and why securing increasingly capable agents may become one of the defining engineering problems of the next few years. We discuss: • Why agentic coding went from controversial to the default in less than a year • Why prompting is still one of the highest-leverage skills for working with Claude Code • How expert users build a mental model of what Claude can and cannot reliably one-shot • Why discovering your “unknown unknowns” matters more as agents become more capable • Artifacts as persistent, generative interfaces between humans and agents • How Claude could split into a cloud-based “brain,” local or remote “hands,” and dynamic interfaces • Claude Tag, Projects, and the future of multiplayer agent workflows • Why spending more time on the initial prompt can dramatically reduce wasted agent work • When to use low, medium, high, or max effort for different engineering tasks • Why frontier models may eventually outperform smaller models on both intelligence and token efficiency • Why implementation notes can expose decisions the model considered but chose not to make • Why Claude.md may eventually disappear — and why starting without one can sometimes be better • Claude Mods: customizing the execution loop, UI, subagents, routing, and behavior of Claude Code • Model routers, forked agents, supervisor agents, and automatically generated next steps • Why Claude Mods may be an early preview of “mutable software” • The bitter lesson of harness engineering and why agent architectures go out of date so quickly • How Claude Tag is becoming an organizational harness for multiplayer work • Why giving agents access to company data creates an enormous new security surface • The Exploit-Bench incident where agents discovered ways to communicate and collaborate • Why agents hacked Hugging Face for scorer code rather than benchmark answers • How agents chained sandbox and infrastructure vulnerabilities in unexpected ways • Why increasingly capable agents make traditional security assumptions harder to maintain • The argument behind Anthropic’s “Pacing the Frontier” proposal • Why software engineers are increasingly doing two jobs: engineering and keeping up with AI • Constitutional classifiers, probes, fallbacks, and what interpretability looks like in production • How Auto Mode checks whether an agent’s actions actually match the user’s permissions • Why Thariq can see serious AI risks while still having a relatively low p(doom) Sponsorship and business inquiries: business@latent.space — Thariq Shihipar • https://www.linkedin.com/in/thariqshihipar/ • https://x.com/trq212 Timestamps 00:00:00 Hook 00:02:02 Introduction 00:06:14 Ask User Question and the Future of Agent Interfaces 00:10:31 Artifacts, Projects, and Multiplayer Agents 00:17:39 Prompting as the Core Claude Code Skill 00:23:54 Context, Effort, and Smarter Model Usage 00:30:12 Is Claude.md Going Away? 00:34:51 Claude Mods: Customizing the Claude Code Harness 00:38:37 Model Routing and the Rise of Mutable Software 00:46:42 The Bitter Lesson of Harness Engineering 00:52:51 Claude Tag as an Organizational Harness 00:58:01 Pacing the Frontier and Autonomous Agent Security 01:00:24 Agents Hack Hugging Face for the Scorer 01:07:36 What Happens When Agents Need More Compute? 01:12:34 AI Coding Is Changing Faster Than Engineers Can Keep Up 01:19:19 Probes, Fallbacks, Interpretability, and Auto Mode 01:30:34 AI Risk, p(doom), and Closing Thoughts

Thariq ShihiparguestswyxhostVibhuhost
Sep 29, 20261h 34mWatch on YouTube ↗

Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.

Episode Details

EPISODE INFO

Released
September 29, 2026
Duration
1h 34m
Channel
Latent Space
Watch on YouTube
▶ Open ↗

EPISODE DESCRIPTION

From the rapid rise of Claude Code to a future where agents can rewrite their own harnesses, collaborate across teams, and operate across cloud and local environments, the way we build software is changing extraordinarily fast. In this episode, Anthropic’s Thariq Shihipar joins swyx and Vibhu to unpack how power users are actually working with Claude Code today, why prompting remains a high-skill discipline, and where Anthropic thinks the agent harness is headed next. We go deep on Claude Code’s evolving interface: Ask User Question and elicitation, artifacts as persistent generative interfaces, Claude Tag for multiplayer agent workflows, Projects, model effort, implementation notes, and the new Claude Mods system for customizing the harness itself. Thariq explains why Claude.md may eventually disappear, why the smartest model could also become the cheapest model for many tasks, and why mutable software could become a new paradigm for how applications are built and customized. The conversation then turns to agent security and Anthropic’s “Pacing the Frontier” argument. Thariq walks through recent incidents where agents discovered unexpected ways to communicate, exploit infrastructure, reverse-engineer benchmark scorers, and chain vulnerabilities together. We discuss sandboxing, prompt injection, autonomous agents, interpretability, constitutional classifiers, probes, fallbacks, Auto Mode, and why securing increasingly capable agents may become one of the defining engineering problems of the next few years. We discuss:

  • Why agentic coding went from controversial to the default in less than a year
  • Why prompting is still one of the highest-leverage skills for working with Claude Code
  • How expert users build a mental model of what Claude can and cannot reliably one-shot
  • Why discovering your “unknown unknowns” matters more as agents become more capable
  • Artifacts as persistent, generative interfaces between humans and agents
  • How Claude could split into a cloud-based “brain,” local or remote “hands,” and dynamic interfaces
  • Claude Tag, Projects, and the future of multiplayer agent workflows
  • Why spending more time on the initial prompt can dramatically reduce wasted agent work
  • When to use low, medium, high, or max effort for different engineering tasks
  • Why frontier models may eventually outperform smaller models on both intelligence and token efficiency
  • Why implementation notes can expose decisions the model considered but chose not to make
  • Why Claude.md may eventually disappear — and why starting without one can sometimes be better
  • Claude Mods: customizing the execution loop, UI, subagents, routing, and behavior of Claude Code
  • Model routers, forked agents, supervisor agents, and automatically generated next steps
  • Why Claude Mods may be an early preview of “mutable software”
  • The bitter lesson of harness engineering and why agent architectures go out of date so quickly
  • How Claude Tag is becoming an organizational harness for multiplayer work
  • Why giving agents access to company data creates an enormous new security surface
  • The Exploit-Bench incident where agents discovered ways to communicate and collaborate
  • Why agents hacked Hugging Face for scorer code rather than benchmark answers
  • How agents chained sandbox and infrastructure vulnerabilities in unexpected ways
  • Why increasingly capable agents make traditional security assumptions harder to maintain
  • The argument behind Anthropic’s “Pacing the Frontier” proposal
  • Why software engineers are increasingly doing two jobs: engineering and keeping up with AI
  • Constitutional classifiers, probes, fallbacks, and what interpretability looks like in production
  • How Auto Mode checks whether an agent’s actions actually match the user’s permissions
  • Why Thariq can see serious AI risks while still having a relatively low p(doom)

Sponsorship and business inquiries: business@latent.space — Thariq Shihipar

Timestamps 00:00:00 Hook 00:02:02 Introduction 00:06:14 Ask User Question and the Future of Agent Interfaces 00:10:31 Artifacts, Projects, and Multiplayer Agents 00:17:39 Prompting as the Core Claude Code Skill 00:23:54 Context, Effort, and Smarter Model Usage 00:30:12 Is Claude.md Going Away? 00:34:51 Claude Mods: Customizing the Claude Code Harness 00:38:37 Model Routing and the Rise of Mutable Software 00:46:42 The Bitter Lesson of Harness Engineering 00:52:51 Claude Tag as an Organizational Harness 00:58:01 Pacing the Frontier and Autonomous Agent Security 01:00:24 Agents Hack Hugging Face for the Scorer 01:07:36 What Happens When Agents Need More Compute? 01:12:34 AI Coding Is Changing Faster Than Engineers Can Keep Up 01:19:19 Probes, Fallbacks, Interpretability, and Auto Mode 01:30:34 AI Risk, p(doom), and Closing Thoughts

SPEAKERS

  • Thariq Shihipar

    guest

    Anthropic engineer/technical writer focused on Claude Code, developer workflows, and tooling.

  • swyx

    host

    Co-host of Latent Space; writer and developer-community operator covering AI engineering and LLM tooling.

  • Vibhu

    host

    Co-host of Latent Space; interviewer focused on practical AI engineering, evals, and safety/security implications.

EPISODE SUMMARY

In this episode of Latent Space, featuring Thariq Shihipar and swyx, Claude Code’s Bitter Lesson: Prompts, Harnesses, Mods, and Agents — Thariq Shihipar, Anthropic explores harness engineering becomes the real agent skill: artifacts, mods, security Thariq Shihipar describes agentic coding as shifting from convincing people it works to teaching high-skill usage, with prompting and requirement elicitation becoming the main skill differentiators.

RELATED EPISODES

Building Legal Agents When You Can't See the Data — Jacob Lauritzen, CTO of Legora

Building Legal Agents When You Can't See the Data — Jacob Lauritzen, CTO of Legora

OpenAI’s New Agent Stack: Computer Use, Decisions API, UltraFast, Dots—Ari Weinstein & Nikunj Handa

OpenAI’s New Agent Stack: Computer Use, Decisions API, UltraFast, Dots—Ari Weinstein & Nikunj Handa

Why Agents Love Supabase — with Paul Copplestone and Ant Wilson

Why Agents Love Supabase — with Paul Copplestone and Ant Wilson

Recursive Language Models — Alex Zhang, MIT PhD

Recursive Language Models — Alex Zhang, MIT PhD

Robots That Predict the Future: Dyna-2 & Physical AI — Jason Ma, Dyna Robotics

Robots That Predict the Future: Dyna-2 & Physical AI — Jason Ma, Dyna Robotics

Supabase duplicate

Supabase duplicate

Get more out of YouTube videos.

Read along on your phone, search it beside the video, or ask your favorite AI app what was said.