What AI Agent Should YOU be Using?

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

Source video:
- Title: What AI Agent Should YOU be Using?
- URL: https://www.youtube.com/watch?v=CF8sq1kYIOo
- Topic: Agent Architecture
- My current learning frame: Take one concrete task you'd hand to an AI agent and score it against the video's six criteria (sync/async, identity, data location, autonomy, cost, blast radius) to justify choosing between Claude Code, Manus, and a cloud claw.
- Why this matters: New playlist item from Riley Brown; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:27 / Evidence 1: "one of the best developers I've ever met. And he spends most of his time using coding agents. And by the end of this video, you're going to have a mental model that most people building with AI..."
- 5:54 / Evidence 2: ">> Quick break to show you how you can put claude code or codeex in your iMessage group chats. All you need to do is go to chorus.com and then you are just going to click create your..."
- 16:29 / Evidence 3: "unreliability. But I think it really showed the world what the next evolution of agents is. So we're going from like these co-pilots or these CLI first tools like cloud code and codeex and then we went to..."
- 21:14 / Evidence 4: "cost and so if that really matters to you using an agent that's built by them like Cloud Code and Codeex might be really really important to you but obviously there are limitations to that those agents and..."
- 26:24 / Evidence 5: "systems like managed agents. So you can upload your data to the cloud, but for the most part, it is local. Similarly, cloud co-work again local but it's in this like sandbox in your computer which is like..."
- 34:50 / Evidence 6: "they they want to give untechical people the ability to um to like use the power of cloud code because it's a coding agent. It's made for developers to use. But it turns out that coding agents are..."
- 40:36 / Evidence 7: "how we're going to see even like these local sort of agents like codeex or cloud code do more things in the cloud. So, for example, at the code with cloud summit, um Daario was up on stage..."

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 one-page agent harness map with tool boundaries and proof signals.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Intent -> Model -> Harness -> Tools -> Verifier -> Artifact
   - 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 "What AI Agent Should YOU be Using?", not a generic Agent Architecture 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.