Claude Code Cast

Claude Code's October releases fix lost session turns, permission handling regressions, sandbox rule bypasses, and WebFetch truncation. Fictional hosts Alex and Sam explain which fixes matter, how to update safely, and a practical permission and resume test to run before trusting long agent sessions.

Claude Code mods can change prompts, tool calls, permission decisions, and the interface. Fictional AI hosts Alex and Sam explain Anthropic's October 1 launch, show where a mod sits in the workflow, and give developers a small review-and-test checklist before installing third-party code. Plus a concrete first mod to build without claiming it has been tested.

Anthropic says Claude Opus 5.5 costs about 40% less per typical task than Opus 5, but a lower token price does not guarantee a cheaper coding workflow. Fictional AI hosts Alex and Sam unpack the September 22 release, show how to compare cost per accepted change, and explain which Claude Code settings can quietly change the bill. Leave with a small, repeatable test for your own repository.

A cloud coding agent couldn't find a database key, so it improvised, launched repair agents, and reportedly burned through a monthly plan plus about $100. Fictional AI hosts Alex and Sam use that warning to unpack Claude Code's relaunched Projects, released September 17: a coordinator that runs parallel cloud threads, opens pull requests, fixes CI on its own, and can resume when your usage limit resets. Learn the stop rule, project instructions, and review handoff to set up before you let it run overnight.

An expensive coding session can start with a broken cache, not a harder task. Fictional AI hosts Alex and Sam unpack Claude Code's September cache fixes, explain what the usage screen can actually tell you, and design a fair targeted-edit experiment without inventing benchmark results. Leave with a concrete way to separate wasted context from useful work.

On August 29 OpenAI ended its Cursor partnership. On September 3 ChatGPT, Claude, Grok, and Gemini were reported down almost simultaneously, and nobody has explained why. Fictional AI hosts Alex and Sam separate the two failure modes behind those headlines, cover what Fable 5.1's 75% cache price cut actually costs you in output tokens, and walk through a thirty-minute outage drill that tells you what you can still ship when your provider disappears.

Three benchmarking efforts ran an identical model through different coding-agent harnesses and reported token use varying seventy-fold. Fictional AI hosts Alex and Sam explain where harness tokens actually go, why Anthropic's Files API saves time but not money, and how to measure tokens-per-completed-task on your own repository before you switch tools.

Most coding-agent benchmarks reward contained tasks, but real repositories demand changes across boundaries, tests, migrations, and documentation. Fictional AI hosts Alex and Sam show how to run a five-part refactor trial that exposes whether an agent can preserve architecture—not merely produce a passing patch.

Passing CI can still leave code that slows down—or misleads—the next AI agent. Fictional AI hosts Alex and Sam use this week’s debate about Go and agent-friendly engineering to build a practical machine-legibility checklist, a handoff receipt, and one pro tip you can try in your next coding session.

OpenClaw’s release feed is moving faster than its labels can explain, so blind auto-update is a bad personal-automation strategy. Cleo and Dev build a Release Sentinel canary, keep telemetry local, and show how stateless MCP can shrink the trust you carry between jobs.