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

Beskrivelse

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.

Kommentarer

0

Vær den første til å kommentere

Registrer deg nå og bli medlem av Rubber Duck Radio sitt community!

Prøv gratis

Prøv gratis i 14 dager

99 kr / Måned etter prøveperioden. · Avslutt når som helst.

  • Eksklusive podkaster
  • 20 timer lydbøker i måneden
  • Gratis podkaster

Alle episoder

18 Episoder

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