Rubber Duck Radio

Fable 5 Banned: The Multi-Model Escape Plan

1 h 0 min · 19. Juni 2026
Episode Fable 5 Banned: The Multi-Model Escape Plan Cover

Beschreibung

Anthropic launched Claude Fable 5 with huge expectations, only to see the US government order it pulled globally three days later. Tim and Paul dig into the swirling conspiracy theories: was it retaliation for refusing to arm the Pentagon? Did a competitor exploit a jailbreak report to kneecap a rival? And did Anthropic’s own transparency accidentally hand over the rope? Then the conversation pivots to token anxiety, ballooning API costs, and the open-source models like GLM 5.2 and DeepSeek V4 Pro that now rival proprietary giants at a fraction of the price. The episode’s core insight: a three-stage workflow—planning with a flagship model, implementing with a cheap or local one, and reviewing with a third—lets developers escape single-point-of-failure risks and spiraling bills, and it's already taking shape across the coding community.

Kommentare

0

Sei die erste Person, die kommentiert

Melde dich jetzt an und werde Teil der Rubber Duck Radio-Community!

Loslegen

2 Monate für 1 €

Dann 4,99 € / Monat · Jederzeit kündbar.

  • Podcasts nur bei Podimo
  • 20 Stunden Hörbücher / Monat
  • Alle kostenlosen Podcasts

Alle Folgen

18 Folgen

Episode Fable 5 Banned: The Multi-Model Escape Plan Cover

Fable 5 Banned: The Multi-Model Escape Plan

Anthropic launched Claude Fable 5 with huge expectations, only to see the US government order it pulled globally three days later. Tim and Paul dig into the swirling conspiracy theories: was it retaliation for refusing to arm the Pentagon? Did a competitor exploit a jailbreak report to kneecap a rival? And did Anthropic’s own transparency accidentally hand over the rope? Then the conversation pivots to token anxiety, ballooning API costs, and the open-source models like GLM 5.2 and DeepSeek V4 Pro that now rival proprietary giants at a fraction of the price. The episode’s core insight: a three-stage workflow—planning with a flagship model, implementing with a cheap or local one, and reviewing with a third—lets developers escape single-point-of-failure risks and spiraling bills, and it's already taking shape across the coding community.

19. Juni 20261 h 0 min