Claude Code Just Dropped Workflows (An Actual Game Changer)

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

Source video:
- Title: Claude Code Just Dropped Workflows (An Actual Game Changer)
- URL: https://www.youtube.com/watch?v=ua2YA7TiLEk
- Topic: Codex + Claude Workflows
- My current learning frame: Invoke a deep-research workflow on a specific question you actually care about, inspect the generated workflow.js to set a token budget guard and assign cheaper models (Haiku) to discovery phases, then run it and verify which phase used the most agents.
- Why this matters: New playlist item from Mansel Scheffel; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:59 / Evidence 1: "we're having in this main window. And that's one of the reasons that we would actually have sub agents. So again, if we look at our main claude code session over here, what we can do is we..."
- 3:53 / Evidence 2: "Currently, you can't do this in VS Code with the extension. Three quick things to note on this as well. There is no direct file system or shell access from the script. The agents can do that obviously."
- 6:13 / Evidence 3: "tool and took 17 seconds. We can see in the fetch phase all of the agents that are currently running, how many tokens they're using, what tools they're using, and how long they've been running for. While that..."
- 9:26 / Evidence 4: "line. So, I've just asked Claude to do that exactly right now because you can use different phases inside this script. So, some of them could run in Haiku, maybe for discovery if that's what you wanted to..."
- 11:25 / Evidence 5: "phase. Six haiku agents brainstorm name and tagline candidates. Model haiku. Then we have the critique and we have model sonnet. And for the synthesis, we have model opus. That top part over there was like it said..."
- 13:04 / Evidence 6: "claims times three independent verify agents each. Like I said, this is probably going to be your biggest one most of the time that you're running workflows. So, flipping back to our slides, we now know with a..."
- 15:07 / Evidence 7: "majority of my workflows. Again, in a business, you just want that determinism and that reliability. You want to make sure that Claude is doing the same thing every day, getting leads, replying to people, what whatever it..."

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 Dropped Workflows (An Actual Game Changer)", 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.