When should you use it?
- You are trying a new screen-control agent
- You want a safe first task you can check
- You plan to give it real errands later
Not for: Tasks with payments or messages; Unverified outputs you will act on
What do you need, and what do you get?
You need
- Agent sandbox
- A simple, checkable request
You get
- Saved file with results
- Your notes on where it went wrong
How does it work, step by step?
- Use a sandboxRun the agent in an isolated environment, such as the vendor's container demo.
- Pick a checkable taskAsk for a few facts you can verify in minutes.
- Watch the screenshotsFollow each action and what the agent saw.
- Verify every rowOpen each link and compare with what was saved.
- Note failure modesRecord where it acted before a page loaded or guessed.
The prompt
Our own prompt, inspired by Lovkush Agarwal and written to work in Claude, ChatGPT agent and Grok Bot. Values in lime are placeholders.
Look for a handful of places near [location] with good meat-free options. For each, open its own website and confirm it exists and serves vegetarian dishes. Write each place, its site and a short summary into a notes file. If a page does not load fully, wait and reload before reading it. If you cannot confirm a detail, write unconfirmed instead of filling it in.
Inspired by Lovkush Agarwal: I tried Anthropic's computer-use agent. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Acting on a screenshot taken before the page finished loading led to an invented result.
- A first-time success at setup says nothing about accuracy.
Our take
Short and valuable because it names a concrete failure: acting on a stale screen. Agents have improved since, but the test design still applies to any new tool. Give it a task you can verify by hand. Lovkush's errand was well chosen: five places near Bond Street with opening hours is small enough to check in minutes, yet it exercises searching, reading and saving. Running it inside the vendor's container demo kept the agent away from his real accounts. Watching the screenshots showed the failure clearly; the agent sometimes acted on a page before it had finished loading and produced a result that was not really there. That pattern is worth testing for in any screen-control tool. Open every link and compare it with what was saved, and record where the agent guessed. A smooth setup says nothing about accuracy. Only move to real errands once a tool passes a few checkable tests, and keep payments and messages out of scope until then.
Where the time goes back: A ten-minute test shows you a failure mode cheaply before it costs you on a real task.
FAQ
Was setup hard?
What went wrong?
Source and credit
Inspired by Lovkush Agarwal. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- I tried Anthropic's computer-use agent
- Creator
- Lovkush Agarwal
- Published on
- lovkush.substack.com (Substack)
- Original date
- Jan 14, 2025
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.