The Real Reason You Keep Hitting Claude Limits (And How to Fix It)

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

Source video:
- Title: The Real Reason You Keep Hitting Claude Limits (And How to Fix It)
- URL: https://www.youtube.com/watch?v=r_CLYDdBdmM
- Topic: Codex + Claude Workflows
- My current learning frame: Run a real coding task in Claude Code while applying the five habits (manual /compact at 50%, /clear between unrelated tasks, a 60% session handoff, killing extended thinking by default, and offloading file-heavy work to a Haiku sub-agent) and use /cost plus /context to measure the difference.
- Why this matters: Limit management is really workflow design.

Transcript anchors from this exact video:
- 0:24 / Evidence 1: "context rot. Once you actually see how it works, I promise you will not use Claude the same way again. Now, I run Claude across three different businesses. I've been hitting limits. My team and I, we've been..."
- 2:14 / Evidence 2: "burning more tokens than your first 15 combined. Okay. So, now we know that context is working memory and it reloads at every single message. That right there, that is half the problem. So, here's the other half."
- 4:00 / Evidence 3: "features that you guys are using, the models that you pick, the length of your sessions, they're telling you it's right up front, you have to manage this actively. And most people just aren't. And then they complain..."
- 5:33 / Evidence 4: "sessions that you thought were probably cheap, they may not be cheap whatsoever. And the models that you thought you weren't using, you actually are. So, it's effectively the closest thing to an X-ray for your context. And..."
- 7:17 / Evidence 5: "file for a different feature. Now, Claude, it was just hauling three jobs worth of context around the whole time. Now, the second that I actually switch jobs, switch tasks, I just do {slash}clear. And people always panic..."
- 9:16 / Evidence 6: "for everything else, Claude, it's plenty smart without the thinking tax. So, you can literally cut your burn on simple tasks by a third just from this one simple change. Habit number five, sub-agents. So, anytime that I'm..."
- 11:01 / Evidence 7: "go ahead and read it if you guys are interested in. If you guys only take one thing from this video, take this. Stop treating Claude as a infinite chat window. You need to treat it as a..."

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 "The Real Reason You Keep Hitting Claude Limits (And How to Fix It)", 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.