The AI Setup I Use to Run EVERYTHING (in one app)

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

Source video:
- Title: The AI Setup I Use to Run EVERYTHING (in one app)
- URL: https://www.youtube.com/watch?v=rlOpbu3Enkw
- Topic: Interfaces + Open Design
- My current learning frame: Build a minimal version of this workspace: import or assemble a VS Code profile with Claude Code and file viewers, create an OS root folder with two work-area subfolders and a CLAUDE.md in each, then run one real writing task with Claude editing the live file beside you.
- Why this matters: New playlist item from Brad | AI & Automation; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:25 / Evidence 1: "got my Claude desktop killer. I have Claude and Codec on the right here where I can run multiple sessions working across live files on my computer doing real work. And in the middle here, I have the..."
- 3:34 / Evidence 2: "Claude Code, the official Anthropic extension, which is what lets me put Claude in the right hand side panel and then Codex which is OpenAI's coding agent and this lets me run a second AI alongside Claude in..."
- 5:52 / Evidence 3: "across other projects. Then, I've got my content folder. More on this in a second. My context farming folder, where automated agents pull everything from my Slack, meetings, and emails, and this goes straight into my OS. And..."

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 "The AI Setup I Use to Run EVERYTHING (in one app)", not a generic Interfaces + Open Design 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.