2 min lesson
The browser + artifacts loop, concretely
Use "The built-in browser is a full browser inside the editor" to describe the practical rule.
Step 1 of 3
The built-in browser is a full browser inside the editor: open any URL, render your running app, and say something like "increase the heading padding on the overview page" - then watch it render while only the necessary files change. Three sub-agents back this: explore, bash and browser.
Artifacts are the proof layer: a cloud agent navigates its own virtual desktop, tests the change, records a video and screenshots, and on completion returns the walk-through plus type-checks and test results - uploadable directly to the PR. The routing rule: if the output is reviewable via an artifact, push it async; if it's fuzzier, stay foreground.
Learn more
Full explanation
Why the Mermaid move lands
It answers the legacy buyer's unspoken question - "can this thing even understand our mess?" - with a diagram drawn from their actual repo, not a slide.
Pair it with the codebase-as-docs habit: scan, diagram, then ask the codebase pointed questions live. That sequence reads as mastery, not a rehearsed script.
Tie the spine back to the role: the demo isn't proving Cursor types fast. It's proving the workflow you'll coach - plan, interrogate, verify, prove - which is exactly the trust-but-verify discipline that makes a rollout safe.