Anthropic Just Fixed Claude Code’s Biggest Problem

You are helping me turn one specific YouTube video into real, durable learning.

Source video:
- Title: Anthropic Just Fixed Claude Code’s Biggest Problem
- URL: https://www.youtube.com/watch?v=sJrz5Qokbbo
- Topic: Codex + Claude Workflows
- My current learning frame: Take one real repo and wire the harness end to end: split the bloated root CLAUDE.md into layered per-folder notes, add a passive self-improving stop hook, and connect one MCP server for a tool your team uses daily.
- Why this matters: New playlist item from Nick Puru | AI Automation; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 1:01 / Evidence 1: "just a quick mental model first, Claude Code, it does not pre-index near repo. So, there's no embedding step, there's no vector database, there's no rag layer that's running in the background. The way that it actually works,..."
- 3:28 / Evidence 2: "is just going to be connecting Claude to all of your internal tools. And then, sub-agents, these are effectively just split expiration from editing. Also, a quick heads-up, LSP, I'm pretty sure 90% of you have never heard..."
- 7:37 / Evidence 3: "model that we use for which job, how we keep track of our prompts in here, the test command that only works in this folder, and none of this actually matters when Claude is over in the dashboard."
- 11:34 / Evidence 4: "finishes responding and it's just once per turn. And Anthropic's recommendation, and this is actually word for word from their article, a stop hook can reflect on what happened during the session and propose Claude.md updates while the..."
- 14:54 / Evidence 5: "going to be there. And when somebody is working in marketing, the skill is going to be gone. And the mental model that's actually helped me is Claude's and MG, it's effectively just rules and things Claude must..."
- 19:44 / Evidence 6: "connects to internal tools, data sources, and APIs that it cannot otherwise reach. So in practice that means your Jira, your Confluence, Sentry, your internal database, your GitHub, each one has its own MCP server. So you can..."
- 22:15 / Evidence 7: "and then the main agent, it edits with the full picture. So, what the hell does that mean? Three sub agents fanning out, each one running its own context window, each one returns a clean summary. The main..."

Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable claims from the video. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A routing matrix for when to use Codex, Claude, browser checks, or manual review.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Inspect -> Plan -> Edit -> Verify -> Review -> Route
   - 3 concrete examples that apply the video idea to real agentic work
   - 2 failure modes the video helps prevent
   - a checklist I can use the next time I run Codex or Claude
   - one practical exercise with a clear done signal
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.

Quality bar:
- Make this specific to "Anthropic Just Fixed Claude Code’s Biggest Problem", not a generic Codex + Claude Workflows essay.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- If evidence is weak, say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.