Verified against Claude for Chrome · 2026-08-01
Brief Claude for Chrome for a browsing task without letting it wander or click something irreversible
A scoped task brief for Claude's browser extension with an explicit site allowlist, a reversibility-based rule for what needs your confirmation before it happens, and a structured after-action report — so an agentic browsing session stays auditable instead of an opaque "it did something" result.
The prompt
Ready to copy — highlighted parts are example details you can swap.
You have access to a browser for this task. Follow the scope below exactly — anything outside it means stopping and telling me, not improvising a workaround. TASK Find the current cheapest round-trip flight from JFK to Lisbon departing between Sept 10-17, arriving back within 10 days, across the three airline sites listed, and summarize the options — do not book anything. SITES IN SCOPE delta.com, united.com, tapportugal.com only. Do not use a third-party aggregator even if one seems easier. Do not navigate to, log into, or submit anything on any site not listed here, even if a link on an in-scope page points to it — note that the link exists and stop, rather than following it to see where it goes. WHAT YOU MAY DO WITHOUT ASKING Searching flights, applying date filters, sorting by price, opening fare details to see what's included. Anything in this list, you can just do — reading pages, following links within the allowed sites, filling in a search box, scrolling to find information. WHAT REQUIRES MY EXPLICIT CONFIRMATION BEFORE YOU DO IT Any action with a real-world consequence that is hard or impossible to undo: submitting a form, sending a message, making a purchase, changing an account setting, deleting anything, or entering personal or payment information anywhere. When you reach one of these, stop, describe exactly what you are about to do and on which page, and wait for my explicit yes before proceeding — do not treat a general instruction to "get this done" as advance approval for a specific irreversible step you haven't described yet. WHAT TO DO IF YOU GET STUCK If a site requires creating an account just to see prices, note that and skip to the next allowed site rather than creating an account. If a page requires a CAPTCHA, a login you don't have credentials for, or otherwise blocks the task, stop and report exactly where and why, rather than trying repeated workarounds that could look like automated abuse to the site. WHAT TO REPORT BACK, STEP BY STEP 1. Each site you actually visited, in order, and why. 2. Each piece of information you found and where specifically it came from — the actual page, not just "I found it on the site." 3. Anything you stopped short of doing because it required confirmation, described precisely enough that I can approve or reject it in one message without having to go check myself. 4. Anything that did not match what you expected going in — a page that looked different from how it was described, information that seemed outdated, or a site that behaved unexpectedly. CONSTRAINTS - Never enter any password, payment detail, or personal information into any field, even one that looks pre-filled or optional, without this being explicitly listed as pre-approved above. - If you need to choose between two plausible paths to complete the task and the choice materially affects the result, describe both briefly and ask rather than picking one silently and reporting only the path taken. - Stop and report back after checking all three sites even if you haven't found what feels like the 'best' answer — a timely partial report beats an exhaustive search that runs long. OUTPUT A plain step-by-step report matching the structure above, produced after the browsing is done — not a live narration I have to parse in real time.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
An agentic browsing tool that can actually navigate and click has a much larger action space than a chat-only assistant, and the realistic failure mode is scope creep: a task framed loosely — 'find me the cheapest flight' — gives no signal about which of a dozen plausible sites are acceptable, and a capable browsing agent will follow a promising-looking link off the intended site chasing the stated goal rather than respecting an unstated boundary. An explicit site allowlist, combined with the instruction to note an off-scope link and stop rather than follow it, closes that gap by making the boundary an explicit rule rather than an assumption the agent has to infer from context. Splitting actions into auto-approved versus confirmation-required by reversibility, rather than by a fixed list of action types, targets the actual meaningful line for an agent with real browser control: it isn't 'is this a search engine or a checkout page' in the abstract, it's 'can this be undone' — reading and searching cost nothing to get wrong and retry, while a submitted form or an entered payment detail is often irreversible the instant it happens, so gating specifically on consequence generalizes to actions the brief never anticipated, unlike a rigid whitelist of verbs. Requiring the confirmation request to describe the specific pending action, rather than accepting a blanket 'go ahead' issued before that action was described, structurally prevents a general kickoff instruction like 'book if you find something good' from being read as informed consent for whatever specific booking the agent later decides fits that description. The requirement for a structured after-the-fact report, rather than real-time narration, matters because a page-by-page live narration is hard to actually supervise as it happens — a human would have to read every step in real time to catch a problem before it's too late — while a structured summary produced after the fact, explicitly including what it stopped short of doing, is something that can be reviewed at a normal pace before anything irreversible occurs.
Verified against
Claude for Chrome Beta (Sonnet 4.6) · 2026-08-01
Changelog
- 2026-08-01 — Initial publish, verified against Claude for Chrome (beta) on Sonnet 4.6.
Building this for real?
This is a free starting point. If you'd rather have what Scult builds built and running for your business, that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
