When should you use it?
- You build the same report from two or three web apps every week
- Writing click-by-click instructions feels like more work than doing the task
- A teammate needs the same steps written down anyway
Not for: Tasks that change money, records or customer data; keep the agent to read-and-report jobs
What do you need, and what do you get?
You need
- A short screen recording with your voice explaining what you click and why
- An AI that can watch video or read a transcript plus screenshots
- A browsing agent your company allows on these apps
You get
- Numbered instructions with a goal, the data to collect and a stop rule
- The finished report from the agent's run
How does it work, step by step?
- Record one clean runDo the task once while talking: which report, which filters, which numbers matter and why.
- Turn it into instructionsGive the recording to an AI with our prompt; ask for steps, checks and the point where it must stop and ask you.
- Hand it to the agentPaste the instructions into the agent and sign in yourself when it reaches a login screen.
- Compare and refineCheck the first report against your own; fix the instructions, not the output, so the next run improves.
The prompt
Our own prompt, inspired by u/mojorisn45 on r/ChatGPT and written to work in ChatGPT agent, Claude and Gemini. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Below is a transcript (and screenshots if available) of me doing a recurring task in {apps} while explaining my choices. Turn it into instructions an AI browsing agent can follow. Transcript: {transcript} Write: 1. Goal: one sentence on what the finished output is ({output_format}). 2. Numbered steps, one action each, naming the exact report, view, filter or field. 3. What to capture at each step and why it matters. 4. Checks: what the agent should do if a screen, report or field doesn't match the description (stop and tell me, never guess). 5. Hand-offs: stop at every sign-in or MFA screen for me to take over. 6. Read-only rule: do not edit, send, delete or submit anything. Keep it short enough to paste into the agent.
Inspired by u/mojorisn45 on r/ChatGPT: My first "wow" moment with Agent. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Commenters' main worry was access. Use only connectors and agents your company has approved, and enter passwords and MFA yourself.
- Recorded steps break when an app changes its layout; tell the agent to stop and report if a screen doesn't match.
Our take
The clever part of this post isn't the agent, it's how the instructions were made. Most people give up on browser agents because writing down every click, filter and judgment call is tedious. Talking through one real run on camera captures all of it, including the reasons, and an AI is good at turning that into a clean procedure. The same document also doubles as an SOP for a new hire. The thread's top replies were about security rather than capability, and they have a point: an agent working inside Salesforce with a manager's access can cause real damage if it misreads a screen. The poster's company had approved the connectors and he signed in himself, which is the right baseline. Keep these jobs read-only, and have the instructions name the exact report and a stop rule. In our dry run we gave a written transcript of a narrated walkthrough, building a weekly renewal report from a CRM and a call-recording tool, to our prompt. It produced eleven numbered steps with a stated goal, the four fields to capture, two checks (stop if the saved report is missing; flag accounts with no calls in 7 days rather than guessing) and a hand-off at login.
Where the time goes back: A report you rebuild by hand every week becomes a set of instructions you write once and reuse.
FAQ
Does the agent need my password?
Why narrate instead of just recording clicks?
Source and credit
Inspired by u/mojorisn45 on r/ChatGPT. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- My first "wow" moment with Agent
- Creator
- u/mojorisn45 on r/ChatGPT
- Published on
- Original date
- Jul 25, 2025
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- ChatGPT agent
- AI dry run
- Oct 20, 2026: passed. Dry-run tested by our AI test agent on sample input. Captured the reasons from the narration as checks; included hand-offs at sign-in and a read-only rule.
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.