Theo Criticizes Fable 5 Access and Benchmark Restrictions

Theo points to restricted access, fallback models and refusals in one coding benchmark as reasons for concern about Anthropic's Fable release.

ThTheo연사
채널
Theo - t3․gg
게시일
2026년 6월 16일
영상
0:37
읽기
1분
슬라이드
2
원문
영어
YouTube에서 열기
스크롤하면 영상이 오른쪽 아래로 작아져 계속 재생됩니다. 자막은 읽기 언어를 따릅니다.
읽기 언어2개 언어로 읽을 수 있음
이 글은 아직 한국어 번역이 없어 영어 원문으로 표시합니다.
요약

30초 요약

In this June 2026 video, Theo argues that restrictions around Anthropic's Fable model limit who can use it and complicate evaluation. He cites benchmark results that use an Opus fallback and a report of refusals on ProgramBench, and criticizes the precedent he believes the restrictions set.

  1. 1A powerful model with access limitsTheo praises Fable's capabilities but criticizes how Anthropic implemented access restrictions.
  2. 2Benchmark fallback mattersHe notes that strong reported results can include an Opus 4.8 fallback rather than Fable alone.
  3. 3ProgramBench refusalsHe cites a reported run in which Fable refused all 200 tasks, and argues that restrictions affect evaluation.

핵심 정리

  1. Theo says some people could not access Fable at the time of the video.
  2. Some benchmark results for Fable included an Opus 4.8 fallback.
  3. Theo cites a report that Fable refused all 200 tasks in a ProgramBench run.
  4. He argues that the restrictions set a troubling precedent for future models.
전문

챕터별로 다듬은 전문 읽기

원본 자막만 보기
01

Access and benchmark restrictions

Theo criticizes the limits on who can use Fable. He also examines benchmark results and the role of a fallback model.

Fable, Anthropic's new Mythos-class model, is powerful, but at the time of this video some people cannot use it at all. I think the way Anthropic implemented these restrictions is unacceptable.

Benchmark result with an Opus fallback
슬라이드 1 / 2Benchmark result with an Opus fallbackThe displayed result labels Fable 5 with an Opus 4.8 fallback.

The model has benchmarked very well, but some results come with a qualification: an Opus 4.8 fallback. In another example, a reported ProgramBench run says Fable refused all 200 tasks. I find the restrictions absurd, and I worry about the precedent they set.

02

Refusals and precedent

He cites reported refusals on ProgramBench. He worries about the precedent set by such restrictions.

Reported ProgramBench refusals
슬라이드 2 / 2Reported ProgramBench refusalsThe displayed post reports that Fable refused all 200 tasks in the run.

같은 채널의 다른 글

슬라이드 5장38:47EN
Theo - t3․gg· 2026년 10월 28일Theo’s Long-Running Agent Experiments: Verification, Compute and CostTheo Browne · Ping LabsA skateboard game and two compiler projects show how repeated checks and flexible compute can sustain agent work—and how expensive those loops can become.코딩 에이전트에이전트 엔지니어링AI cost & performance+2
슬라이드 5장36:07EN
Theo - t3․gg· 2026년 10월 27일Theo on Token Costs, Coding Agents, and the Price of AI CapabilityTheo Browne · Ping LabsA viral estimate of Lauren's AI spending prompts a closer look at cache pricing, benchmarks, and the changing work of coding agents.AI cost & performance코딩 에이전트Inference+1
슬라이드 5장30:37EN
Theo - t3․gg· 2026년 10월 26일Theo’s Three Skills for Reviewing and Shipping with Coding AgentsTheo Browne · Ping LabsHow sol-loop, full-send and full-stop encode review, verification and different levels of merge authority.Agent skills코딩 에이전트Code review & verification+2
슬라이드 2장0:43EN
Theo - t3․gg· 2026년 10월 23일Theo Distinguishes Security Vulnerabilities from Active AttacksTheo Browne · Ping LabsA short explanation of why disclosed software flaws and reported attacks are different kinds of security news.CybersecuritySoftware engineering
슬라이드 6장29:22EN
Theo - t3․gg· 2026년 10월 22일Theo on Security Vulnerabilities, Stolen API Keys and AITheo Browne · Ping LabsA look at the gap between vulnerability disclosure and patching, and a speculative account of why stolen inference keys may be valuable.CybersecurityAI securitySoftware engineering+1
슬라이드 4장31:13EN
Theo - t3․gg· 2026년 10월 20일Theo on Why Smarter Models Help More Than DevelopersTheo Browne · Ping LabsFrom game modifications to compiler experiments, Theo revisits his assumptions about who benefits from more capable AI.코딩 에이전트Developer productivityHuman-AI Collaboration+1