Claude Code Just Got WAY More Powerful

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

Source video:
- Title: Claude Code Just Got WAY More Powerful
- URL: https://www.youtube.com/watch?v=efVfydaUIrM
- Topic: Codex + Claude Workflows
- My current learning frame: Pick one recurring task you do manually in Claude Code, then design both a routine (cron or webhook trigger) to run it and a markdown rubric an outcome-based agent could iterate against to finish it.
- Why this matters: New playlist item from How I AI; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:04 / Evidence 1: "Welcome back to How I AI. I'm Claire Vo, product leader and AI obsessive here on a mission to help you build better with these new tools. Today I attended Code with Claude, Anthropic's first developer event, and..."
- 1:52 / Evidence 2: "it daily or no, sorry, I'm going to run it weekly on Mondays at 6:00 a.m. And I think that's all I need to do. Oh, I'm going to select my folder um where my project is and..."
- 3:25 / Evidence 3: "The second one is in Claude manage agents in the API. If you haven't paid attention, opening I released something in Codex called goal. You can do {slash} goal in beta in Codex and it'll basically bang its..."
- 5:41 / Evidence 4: "cool cuz now you're able to define not just individual agents, but teams of agents programmatically through the API. And so, the example I would give for something like Chat PRD is you could have a PRD orchestrator."
- 7:21 / Evidence 5: "to overthink it. But, creating those memories is a little hard. And often a lot of the harnesses right now write memory on a hook. They write that on an event. And so, what they do is like..."
- 8:54 / Evidence 6: "or some regular cadence, you're going to review past sessions, and you're going to explicitly write the right things to disk so they can be referred to moving forward. Side note, I think we think a lot about..."
- 10:30 / Evidence 7: "memory over sessions, over time, and do that on demand. And then finally, we can all use more Claude code, which makes everyone happy. I do not know if these limit increases apply to Claude design. I suspect..."

Video-aware target:
- Prompt lane: Coding-agent workflow
- Mechanism to extract: Find the workflow rule that explains when and how to use Codex, Claude Code, browser control, dashboards, or manual review.
- Artifact to produce: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal.
- Artifact must include: task class; agent/tool choice; context packet; verification step; handoff/recovery rule

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, transcript support, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable mechanism from the video: Find the workflow rule that explains when and how to use Codex, Claude Code, browser control, dashboards, or manual review. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Inspect context -> Route tool -> Plan work -> Edit safely -> Verify behavior -> Report next step
   - answers to these source questions: What workflow pain is being solved? | What exact coordination mechanism is shown? | What evidence proves it changes the work?
   - 3 concrete examples that apply the video idea to real agentic work, such as rate-limit routing; browser verification after a UI edit; long-running /goal session review
   - 2 failure modes the video helps prevent, chosen from the transcript evidence and these likely risks: choosing tools by hype; losing context across agents; letting parallel sessions become invisible
   - a checklist for the next real workflow, focused on: routing decision, context portability, verification, handoff summary
   - one practical exercise with a clear done signal: Route three recent tasks across Codex, Claude, browser checks, and manual review with a reason for each.
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 "Claude Code Just Got WAY More Powerful", not a generic Codex + Claude Workflows essay.
- Each workflow rule must point to a timestamped claim or demo moment, then state what remains unproven.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- Avoid these generic drifts: generic Codex vs Claude comparison; feature lists without task routing; claims that ignore limits or recovery.
- If evidence is weak or missing, stop and say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.