Stop a browser agent clicking the wrong thing after the page changes under it
by PaperChaseWebb
A team building a shared human and agent browser tags every agent action with who is driving the tab and the page revision the plan was based on. If either changed, the action fails as stale and the agent re-reads instead of clicking whatever is now at that spot.
- Price
- Free
- Difficulty
- Advanced
- Setup
- 1 hr
- Format
- .md file
stop-a-browser-agent-clicking-the-wrong-thing-after-the-page-changes-under-it.md · 2 KB · direct download, no signup
What you end up with
The price is more round trips and treating 'stale' as a normal result.
What you get
- A plain-language summary of the workflow
- A fill-in prompt template
- What to watch out for
- A link to the original source
Who it is for
Builders who already use AI agents and want a proven workflow they can copy into their own project.
Works with
Dashed chip: Plain Markdown, so it also pastes into other agents such as Grok Bot, Hermes, OpenClaw or Muse. We list those as compatible by format only, not as tested.
Tools needed
Cost to run: Free with the agent plan you already use.
Time to result: One working session
How it works
Record the page revision or a snapshot when the agent plans an action
Record the page revision or a snapshot when the agent plans an action.
Expected: Done before you move to the next step.
Just before acting, check the target still matches and the person has
Just before acting, check the target still matches and the person has not taken over.
Expected: Done before you move to the next step.
If anything changed, fail as stale and re-read the page
If anything changed, fail as stale and re-read the page.
Expected: Done before you move to the next step.
Keep committing steps (submit, pay, close) with the person
Keep committing steps (submit, pay, close) with the person.
Expected: Done before you move to the next step.
Log stale results so you can see how often the page moved
Log stale results so you can see how often the page moved.
Expected: Done before you move to the next step.
Sample prompt from the pack
Apply this workflow to [your project]: 1. Record the page revision or a snapshot when the agent plans an action. 2. Just before acting, check the target still matches and the person has not taken over. 3. If anything changed, fail as stale and re-read the page. 4. Keep committing steps (submit, pay, close) with the person. 5. Log stale results so you can see how often the page moved. Stop and ask me before anything irreversible: deploys, payments, sends or deletes.
Adapted by PaperChaseWebb. Not the original author's prompt.
Free preview of the file
# Stop a browser agent clicking the wrong thing after the page changes under it PaperChase agent use case (free feed entry), version 1.0. Source: [u/OyaAI](https://www.reddit.com/r/AI_Agents/comments/1xhx5bl/how_do_you_stop_a_browser_agent_from_acting_on_a/), 2026-10-28. ## What they did The failure they designed against is the silent wrong click: the agent picks an element, a modal opens or the person takes over, and the click lands on something else. Each call now carries the current controller and the revision the plan was computed from; a mismatch returns a stale target error. Opening, picking and closing tabs is human only, so the agent can prepare but the person commits. ## Worth knowing The price is more round trips and treating 'stale' as a normal result. For Playwright or CDP setups, a cheap version is to snapshot before acting and compare the target's text and position just before the click.
Worth knowing
- The price is more round trips and treating 'stale' as a normal result. For Playwright or CDP setups, a cheap version is to snapshot before acting and compare the target's text and position just before the click.
- Figures are as reported by the original author and were not re-measured by us.
Questions
Where does this come from?
A public post credited to u/OyaAI. Source: https://www.reddit.com/r/AI_Agents/comments/1xhx5bl/how_do_you_stop_a_browser_agent_from_acting_on_a/
Is it free?
Yes. Feed entries are free to read and download.
Details
Version 1.0 · Updated Oct 29, 2026 · Markdown version of this page
License: Personal and commercial use. Credit the original source when you share the workflow. Download terms
Related
AGENTS.md, CLAUDE.md and Cursor rules starter files
Six fill-in instruction files for coding agents (base, Next.js plus Supabase, FastAPI, browser game, CLAUDE.md pointer, scoped Cursor rules), an Approvals section that makes the agent stop and wait for your yes, a table of what Grok Bot, Claude Code, Codex, Hermes and Cursor each read, a read-only checker for your rule files and 9 prompts to write, trim and test your own.
Ask-first rules for AI agents: hard nos, approval cards and a test set
Paste-in rules that make an agent ask before it sends, spends, posts or deletes, define what a real yes is, and stop retries after a no, plus 12 test scenarios to check it.