Como Usar o FreeBuff, o Agente de IA pra Programar 100% DE GRAÇA #freebuff #ia #iagratis #claudecode

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

Source video:
- Title: Como Usar o FreeBuff, o Agente de IA pra Programar 100% DE GRAÇA #freebuff #ia #iagratis #claudecode
- URL: https://www.youtube.com/watch?v=cV8he4-ewoI
- Topic: Codex + Claude Workflows
- My current learning frame: Write one detailed, unambiguous landing-page prompt and run it through both FreeBuff modes — web builder and terminal CLI — comparing the results, noting your region's model and quota limits, and confirming you kept all sensitive data out of the tool.
- Why this matters: New playlist item from Kauã Miguel - Dev; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:21 / Evidence 1: "free coding agent that works differently from open code, Mimo, or Cloud Code, for example. And why is he different? For example, with cloud code or memode, when you use their free version, you depend on using an..."
- 2:16 / Evidence 2: "here we have a problem. The free buff has more models in other regions of the world. So, for example, Canada, the United States, the UK, some regions of Europe, they have access to these complete models for..."
- 4:32 / Evidence 3: "act as, for example, a copilot, where we can see your complete repository. We have a community with people here, there are remnants of Discord, and there are several cool projects here as well. This one isn't quite..."
- 6:59 / Evidence 4: "cool. I can come here, for example, and accept this. And one more point, unlike what I said before regarding the web, where you have a message limit, here your limit is based on time. So you can..."

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 "Como Usar o FreeBuff, o Agente de IA pra Programar 100% DE GRAÇA #freebuff #ia #iagratis #claudecode", 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.