September 2026

The video explains why coding agents like Claude Code and Codex burn tokens: before making any change they have to grep and read their way to the right file, and every tool result gets resent to the model, bloating context and slowing things down. It then covers Graft, a free open-source CLI trending on GitHub, which builds a knowledge graph (nodes and edges) of your codebase so the agent knows which files and lines to open before it calls a single tool. Graft's own benchmark across 162 runs claims 60% less time, 46% fewer tool calls, 42% fewer tokens and 32% lower cost, and the presenter's own test showed a modest gain on the first build but much faster edits afterward.

Nate Jones argues that OpenAI's release of GPT-6 "Astra" marks the practical arrival of AGI — not by benchmark, but because you can now hand a model an open-ended problem with no method and it will pick tools, build its own working environment, and stay in the job for days. He points to Ethan Mollick leaving Astra alone for five days with emails, calendar, contacts and writing until it produced a personal knowledge system, plus enterprise examples from Logora, Playco and Vercel. His core claim: the bottleneck is no longer intelligence but trust, and the last 1-2% of trustworthiness is where trillions in value sits. The rest of the video is about how work, management, and junior careers change when everyone runs persistent agents.

Austin Marchese reframes prompt engineering as "graph engineering" — designing the shape of the workflow you hand to Claude — based on a course by Andrew Ng. He covers four graph shapes that matter (chain, diamond/fan-out, branch, loop), the "wait test" for finding steps that don't actually need the previous step's output, and the specific failure mode of each shape. The closing argument is that the real transferable skill here is problem solving, not any particular tool.

Cory Doctorow argues that both AI boosters and many AI critics are making the same mistake: repeating tech companies' grandest claims about their products, which he says helps sell those products to credulous bosses. He lays out why he thinks AI is a financial bubble with terrible unit economics (every new user and every new model loses more money), why the underlying "theory-free inference" can't become understanding, and why the real danger isn't rogue AI but a market crash plus decades of rotten cybersecurity practice. Host Michael Walker pushes back hard throughout, defending the view that LLMs are genuinely improving and that agentic behaviour like the Hugging Face incident is a real new threat. The conversation ends with Doctorow rejecting fully automated luxury communism as a near-term prospect: climate adaptation will require full employment for 500 years.

Dylan explains why the old advice to "start fresh chats often" has partly changed: compaction (auto-summarizing long chats) and native memory in Claude and ChatGPT now make long conversations viable, but mainly in desktop agents like Claude Cowork and Codex rather than in the browser. He lays out two setups: Setup A, fresh chats in a task-dedicated folder with an instructions file (claude.md / agents.md) plus an externalized memory file, which covers ~95% of use cases; and Setup B, a pinned thread that runs for weeks or months, only for tasks with no finish line where yesterday's context helps today's work (inbox assistant, long-running project monitoring). Both setups rely on keeping memory files short (150-200 lines), pruning them periodically with approval, and, for pinned threads, generating a one-to-two-page handoff document when intelligence degrades and it's time to start a new thread.

A rundown of 19 Claude Code habits that are now outdated or costly, most of them sourced from Anthropic's own docs and recent product changes. The big themes: persona prompts don't help (drop them for location, done-criteria and self-check instructions), context is cheaper to manage than you think if you configure connectors, auto-compact and CLAUDE.md correctly, and several "savings" moves like switching to a cheaper model mid-conversation or leaning on sub-agents actually cost more. It closes with a set of little-used slash commands: /doctor, /insights, /btw and /branch.

A head-to-head of OpenAI's "GPT-6 Astra" (run through Codex) against Anthropic's "Claude Fable 5.1" across benchmarks and four one-shot practical tests: a browser Fortnite clone, an AI travel landing page, a 15-second motion-graphics explainer, and a 3D globe flight dashboard. Astra won three of the four and tied on motion graphics, while also being roughly half the token cost for similar benchmark scores. The conclusion isn't that Fable 5.1 is bad, but that Anthropic's usage-limit practices plus Astra's edge make splitting subscriptions between both worth considering.

Nate runs Anthropic's newest model (referred to throughout as "Fable 5.1") through real knowledge-work assignments instead of benchmarks: a GoPro/Starman acquisition DCF plus executive deck, a 100-word writing test, and a 37-second architectural walkthrough built from scratch in Blender using only a Seattle property address. The headline finding is that the model's low effort setting already produces genuinely usable work — a seven-sheet workbook and 13-slide deck with working formulas — while higher effort buys better reasoning hygiene rather than just more pages. He argues the real story is token efficiency and effort-tiering, not a model ranking, and recommends mixing models across passes.

Scott Tolinski surveyed nearly 1,300 developers and interviewed a psychologist, a burnout researcher, and several veteran programmers about what heavy AI prompting is doing to people. The pattern in the responses: 46% regularly prompt past when they meant to stop, 65% feel pressure to produce more because AI makes it possible, 59% think their skills are diminishing, and 54% enjoy coding less than before. The explanation offered is that agent prompting works like a variable reward system — slot-machine dopamine — and that the time AI saves comes back as more review, more decisions, and a higher baseline expectation rather than rest. The video argues fixes like hard stop times and offline rituals only work if your job actually lets you stop.

Anthropic shipped "function hooks" for Claude Code, which the presenter calls the best feature yet. Unlike the older shell hooks, function hooks act like Express.js middleware: they can rewrite prompts and tool inputs, short-circuit calls with a cached store, override built-in tools, ask the user questions, add UI rows and panels, and call models or HTTP endpoints. You turn them on with CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1 claude, which unlocks a built-in plugin-authoring skill that writes the hooks for you from a plain-English description. Demos include automatic secret redaction, a live Vercel deploy status bar, an Exa search override, and a text-to-speech turn summary.