Lesson 07 · Activity 03

Engine Selector & Pre-Flight Check

Two questions sit between you and a useful delegation: which agentic browser fits this task, and should you hand it over at all. Part one suggests an engine from what you have and what you're doing. Part two is the pre-flight checklist every delegation should clear before the browser is allowed to act. None of this replaces your judgment — it structures it.

Part 1 — Which engine fits?

Part 2 — Pre-flight checklist

Every box should be checked before you let any agent act. Progress is saved on this device.

0 of 6 cleared

Bounded goal: one task, a clear finish line, written down.
No sensitive data: nothing touching student records (FERPA) or other personal data is exposed to the agent.
Lowest privilege: running logged-out or in a low-access session wherever the task allows.
Stop-points named: buy, send, submit, log in, and accept-terms all require my approval.
Active supervision: I'll watch it run and can interrupt — I'm not walking away mid-task.
Verify, don't trust: I'll check the result against the real pages, not just the agent's summary.

Reflection

Think of one task you'd genuinely delegate this week. Which checklist item is hardest to satisfy for it — and does that change whether you'd hand it over?

Saved automatically on this device.

The honest default: If a task can't clear the checklist — especially the sensitive-data and supervision boxes — the right move isn't a different engine, it's to do it yourself. Agentic browsers earn their keep on bounded, low-stakes, public-web work. Keep the high-stakes, student-facing work in your own hands.