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..."

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 UI critique sheet for judging whether an AI interface improves control.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Intent -> Canvas -> Artifact -> Preview -> Feedback -> Iteration
   - 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 AI Setup I Use to Run EVERYTHING (in one app)", not a generic Interfaces + Open Design 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.