GenAI PM
person33 mentions· Updated Aug 25, 2026

Boris Cherny

An AI practitioner mentioned for discussing cybersecurity refusals and an unspecified system called Fable. He is cited as the source of a safety-related update.

Key Highlights

  • Boris Cherny is a recurring source on Claude Code workflows, AI coding quality, and safety-operational tradeoffs.
  • He has shared practical guidance on prompt injection defenses, usage debugging, adversarial code review, and latency tuning.
  • His comments give AI PMs useful signals on product defaults, enterprise readiness, and where coding agents are strong versus still unreliable.
  • He described Opus 4.8 as the first model that felt better than him at coding, while still stressing persistent bugs and inefficiencies.
  • He also linked Fable to both performance workflows and efforts to reduce cybersecurity refusals.

Boris Cherny

Overview

Boris Cherny is an AI practitioner and public commentator frequently cited in discussions around Claude Code, model-assisted software engineering, safety, and operational best practices for agentic development workflows. Across newsletter mentions, he appears as a hands-on builder close to real-world deployment questions: how coding agents should be evaluated, how usage spikes should be debugged, how prompt injection can be mitigated in practice, and how internal tools such as Fable fit into developer workflows.

For AI Product Managers, Cherny matters because his comments consistently sit at the intersection of model capability, product UX, reliability, safety, and enterprise readiness. His updates provide practical signals on where coding agents are actually strong today, where they still fail, how teams are adapting work patterns around them, and which product decisions—such as defaults, guardrails, verbosity controls, and review flows—materially affect user outcomes.

Key Developments

  • 2026-06-29: Boris Cherny described five archetypes on the Claude Code team—Prototyper, Builder, Sweeper, Grower, and Maintainer—framing AI-native work as a blend of product, engineering, and design responsibilities.
  • 2026-07-09: He rolled out `/checkup` in Claude Code to automate cleanup of unused skills, MCPs, and plugins, while also deduping and splitting CLAUDE-related configuration/context.
  • 2026-07-24: Cherny shared that he uses Fable’s dynamic workflows plus profiling to iteratively tune code until p95 latency drops below 300 ms, signaling a performance-first, measurement-driven approach to agentic systems.
  • 2026-08-08: He said that combining model training, input probes, and an intent-checking classifier can reduce indirect prompt injection to near zero on unseen attacks, and announced that auto mode would become the default in Claude Code the following week.
  • 2026-08-09: Cherny noted that evaluation harnesses can support other models through proxies such as LiteLLM, but that effective harnesses still require significant model-specific tool design, prompting, and tuning. He also raised a product question about whether Claude should automatically resume using Fable after a usage limit reset or wait for explicit user confirmation.
  • 2026-08-10: He shared a prompt-injection benchmark from an independent researcher and said Anthropic had largely solved the threat in practice for Claude models, with red-team testing showing similar results. He framed prompt injection as a common attack vector against agents and users.
  • 2026-08-12: Cherny said unspecified evaluations found `/code-review low` outperformed other models at a fraction of the cost—under $0.01. He also argued that LLM bugs are shifting from simple implementation mistakes toward system design, UI usability, and missing broader context, recommending adversarial review via simulator testing or built-in code review tools.
  • 2026-08-21: He recommended running `/usage` to diagnose spend or activity anomalies, saying the most common causes are extreme parallelism, runaway loops, or inefficient skills/plugins. He also referenced an unnamed enterprise-oriented offering expected in the fall, noting that Mythos-class models require extra safety controls and that customers can own and control their data while Anthropic retains none.
  • 2026-08-24: Cherny said he stopped writing code by hand in November 2025 but still codes daily with agents. He described Opus 4.8 as the first model that felt better than him at coding, while emphasizing that Claude-generated code still contains bugs and inefficiencies. He also described a three-stage progression from coding, to coding-adjacent engineering, to broader computer-based tasks, placing Claude at stage 1, partial stage 2, and early stage 3 in his workflow.
  • 2026-08-25: He said his group uses the same exact Fable and is working to reduce cybersecurity refusals, positioning him as a source for a safety-related update tied to refusal behavior and internal system use.

Relevance to AI PMs

1. Useful signal on product defaults and UX tradeoffs: Cherny’s comments on auto mode, verbosity mitigation, Fable resume behavior, and cleanup commands show how seemingly small workflow decisions can strongly affect trust, cost, and adoption in AI coding products. 2. Practical guidance for evaluation and operations: His emphasis on `/usage`, profiling, adversarial code review, and harness tuning gives PMs concrete ways to instrument AI features, investigate failures, and compare quality-cost tradeoffs across models and settings. 3. Grounded view on safety and enterprise readiness: His remarks on prompt injection, cybersecurity refusals, privacy/compliance controls, and Mythos-class safety measures help PMs think beyond raw capability toward deployment constraints that matter in real customer environments.

Related

  • Anthropic / Claude / Claude Code: Cherny is repeatedly associated with Claude Code workflows, model behavior, and safety/performance tradeoffs.
  • Fable: An internal or unspecified system he references in workflow and safety contexts, including dynamic workflows, latency tuning, and resumed use after limits reset.
  • Prompt injection: A recurring theme in his comments, especially around practical mitigations combining training, probes, and classifiers.
  • `/code-review`, `/usage`, `/checkup`: Operational commands tied to quality review, spend/debug analysis, and workspace hygiene.
  • LiteLLM, Bedrock, Vertex, Azure: Relevant to his comments on cross-model harnessing and the reality that integrations still require model-specific tuning.
  • Opus 4.6 / Sonnet 4.6 / Opus 4.8 / GPT-4 Turbo: Part of the broader model comparison landscape surrounding his observations on coding performance, verbosity, and cost-quality tradeoffs.
  • Mythos preview, enterprise customer demand, UK AISI, Glasswing: Connected to discussions of advanced model safety, enterprise deployment expectations, and governance-oriented product constraints.
  • Prototyper, Builder, Sweeper, Grower, Maintainer: Team archetypes he used to describe how AI-native product development work is evolving.

Newsletter Mentions (33)

2026-08-25
Boris Cherny said his unspecified group uses the same exact Fable and is working to reduce cybersecurity refusals.

GenAI PM Daily August 25, 2026 GenAI PM Daily 🎧 Listen to this brief 3 min listen Today's top 19 insights for PM Builders, ranked by relevance from Blogs, YouTube, and LinkedIn. GPT-5.6 in Kiro advances developer price-performance #1 📝 OpenAI News Advancing price-performance for developers with GPT‑5.6 in Kiro to improve price-performance for developers, enabling more cost-effective and performant model access for applications. #16 𝕏 Boris Cherny said his unspecified group uses the same exact Fable and is working to reduce cybersecurity refusals.

2026-08-24
He stopped writing code by hand in November 2025 but still codes daily with agents, and said Opus 4.8 was the first model that felt better than him at coding, while stressing that Claude’s code still has bugs and inefficiencies.

#7 𝕏 Boris Cherny commented that models are advancing through three stages—coding, coding-adjacent engineering, and most computer-based tasks—and judged Claude to have reached stage 1, part of stage 2, and early signs of stage 3 for his work. He stopped writing code by hand in November 2025 but still codes daily with agents, and said Opus 4.8 was the first model that felt better than him at coding, while stressing that Claude’s code still has bugs and inefficiencies. #10 𝕏 Boris Cherny said Opus excels at long-running work and coding but has quirks, with verbosity a major concern and broader fixes a team priority. As a temporary mitigation, users can run `claude /config outputStyle=concise`.

2026-08-21
Boris Cherny recommended running `/usage` for a detailed breakdown, noting that the issue is most often caused by extreme parallelism, a runaway loop, or a very inefficient skill/plugin.

#14 𝕏 Boris Cherny recommended running `/usage` for a detailed breakdown, noting that the issue is most often caused by extreme parallelism, a runaway loop, or a very inefficient skill/plugin. #16 𝕏 Boris Cherny announced that an unnamed item, which had been worked on with customers for a while, was expected to arrive in the fall. He said Mythos-class models require additional safety measures, enterprises need to meet their own privacy and compliance rules, and customers can own and control their data while Anthropic retains none of it.

2026-08-12
"#11 𝕏 Boris Cherny said unspecified evaluations found that /code-review low produced a better result than other models at a fraction of the cost—less than $0.01."

#11 𝕏 Boris Cherny said unspecified evaluations found that /code-review low produced a better result than other models at a fraction of the cost—less than $0.01. #18 𝕏 Boris Cherny commented that LLM bugs are shifting from off-by-one errors toward system design, UI usability, and missing broader context. He recommends adversarial code review—including a one-line prompt to test every edge case in an iOS simulator or Claude’s built-in /code-review—to catch many of these issues.

2026-08-10
𝕏 Boris Cherny shared a prompt-injection benchmark created by an unnamed independent researcher and said Anthropic has largely solved the threat in practice for Claude models, with red-team testing producing similar results.

𝕏 Boris Cherny shared a prompt-injection benchmark created by an unnamed independent researcher and said Anthropic has largely solved the threat in practice for Claude models, with red-team testing producing similar results. He described prompt injection as the most common way scammers attack people and agents, including by using malicious website text to trick agents into disclosing credentials.

2026-08-09
#2 𝕏 Boris Cherny commented that the referenced harnesses support other models through proxies such as LiteLLM, but building an effective harness requires substantial model-specific tool design, prompting, and tuning.

GenAI PM Daily August 09, 2026 GenAI PM Daily 🎧 Listen to this brief 3 min listen Today's top 10 insights for PM Builders. Claude Code sessions can now message each other #1 𝕏 Madhu Guru commented on Claude Code session-to-session messaging, using a figurative heist analogy to describe sessions communicating and operating without individual oversight. #2 𝕏 Boris Cherny commented that the referenced harnesses support other models through proxies such as LiteLLM, but building an effective harness requires substantial model-specific tool design, prompting, and tuning. #10 𝕏 Boris Cherny asked whether Claude should automatically resume using Fable after a user’s limit resets or pause and let the user decide each time.

2026-08-08
Boris Cherny said stacking model training, input probes, and an intent-checking classifier can bring indirect prompt injection to ~0 on unseen attacks—a result he did not expect a year ago. He also announced that auto mode would become the default in Claude Code the following week.

#6 𝕏 Boris Cherny said stacking model training, input probes, and an intent-checking classifier can bring indirect prompt injection to ~0 on unseen attacks—a result he did not expect a year ago. He also announced that auto mode would become the default in Claude Code the following week.

2026-07-24
Boris Cherny uses Fable’s dynamic workflows and a profiler to iteratively tune his code until the p95 latency drops below 300 ms.

#15 𝕏 Boris Cherny uses Fable’s dynamic workflows and a profiler to iteratively tune his code until the p95 latency drops below 300 ms. #16 in Colin Matthews suggests kickstarting AI email writing by first defining a clear “good email” rubric—using an LLM to extract criteria from sample emails—and then iterating on drafts against that rubric rather than endless ad-hoc edits.

2026-07-09
Boris Cherny rolled out `/checkup` in Claude Code to automate cleaning unused skills/MCPs/plugins, deduping and splitting CLAUDE.

𝕏 clem 🤗 – Co-founder & CEO @HuggingFace launched the SkyPilot-HF Storage integration, enabling one-line provisioning of multi-cloud GPU clusters with seamless, cached mounting of Hugging Face datasets and repositories. #15 𝕏 Boris Cherny rolled out `/checkup` in Claude Code to automate cleaning unused skills/MCPs/plugins, deduping and splitting CLAUDE.

2026-06-29
#9 𝕏 Boris Cherny sees five key archetypes—Prototyper, Builder, Sweeper, Grower, and Maintainer—in the Claude Code team.

The newsletter summarizes Boris Cherny's view that roles are blending across product, engineering, and design.

Related

Claude Codetool

An AI coding assistant environment used for running evaluation skills and agentic workflows. In this issue it is mentioned as a runtime for ai-evals-course material and as an agent in an OpenRouter-like system.

Anthropiccompany

An AI company best known for Claude. It is referenced implicitly through Claude’s memory and Cowork features.

Claudetool

Anthropic’s assistant, discussed here for shared memory across chat and Cowork. The feature is relevant to PMs because it enables cross-task context reuse and user-controlled memory.

Opus 4.6tool

A Claude model version praised for personality and writing style. The newsletter contrasts it with Opus 5 as more concise and friend-like.

Opustool

A model used in the newsletter as a reasoning and execution engine for product experimentation. It is described as generating daily A/B test ideas and implementing winners for a mobile game economy.

prompt injectionconcept

A security risk in agentic systems where malicious instructions can manipulate model behavior through retrieved or connected content. The newsletter references it as a design and safety concern for agents.

RAGconcept

RAG is a retrieval-based pattern that injects external context into prompts to improve model responses. The newsletter presents it as often outperforming fine-tuning for practical product work.

Fabletool

An unspecified system or capability referenced by Boris Cherny as being used unchanged by his group. The newsletter provides little detail beyond its use in cybersecurity refusal work.

Sonnet-4.6tool

A Claude model used in the newsletter's example to run Python code and analyze a floor plan. It is discussed as part of an agentic workflow inside Claude Cowork.

Claude Code Reviewtool

An AI-powered code review feature from Claude Code designed to provide deep PR feedback, catch bugs, and improve development workflows. It is presented as a research-preview beta for Team and Enterprise.

Stay updated on Boris Cherny

Get curated AI PM insights delivered daily — covering this and 1,000+ other sources.

Subscribe Free