When should you use it?
- You need a first-pass list from public directories or search results
- Copy-paste research would take an hour
- You can watch the session
Not for: Scraping private data; Auto-emailing anyone on the list; Logging in as you
What do you need, and what do you get?
You need
- Research goal and columns you want
- Allowed public sites or queries
- Row cap
You get
- A table with links and source pages
- Notes on pages it could not open
- No messages sent
How does it work, step by step?
- Define columnsName, URL, why it matched, source page.
- Stay publicBan logins, DMs and form submits.
- Cap the runStop at N rows or T minutes.
- Deduplicate yourselfSort and verify before the list enters a CRM.
The prompt
Our own prompt, inspired by u/No-Definition-2886 on r/ChatGPTPro and written to work in ChatGPT agent, ChatGPT agent and Claude. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Build a research list for: {goal}. Columns: {columns}. Max rows: {n}. Use public pages only. For every row include source_url. If a page needs login, skip it and note it. Do not sign in, submit forms, comment or email anyone. Stop after {n} rows or when results repeat.
Inspired by u/No-Definition-2886 on r/ChatGPTPro: I am among the first people to gain access to OpenAI’s “Operator” Agent. Here are my thoughts.. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Agents invent directories. Require a live URL for every row.
- Influencer or lead lists go stale quickly; date the export.
Our take
Browser agents earn a place on dull public research, not on outreach. We ignore monetization side-plots in the source post and keep the list-building job. In our dry run with a fictional niche directory, the agent returned 12 rows with URLs, skipped 2 paywalled pages, and attempted no emails. Cap rows and minutes before you start. Reject any row without a live URL. Deduplicate by domain before the list enters a CRM. Do not let the agent pitch, follow, or message anyone. Public research lists go stale; date the export and refresh on a schedule you control. Cap rows and minutes before you start. Reject any row without a live URL. Deduplicate by domain before the list enters a CRM. Do not let the agent pitch, follow, or message anyone. Public research lists go stale; date the export and refresh on a schedule you control. Cap rows and minutes before you start. Reject any row without a live URL. Deduplicate by domain before the list enters a CRM. Do not let the agent pitch, follow, or message anyone. Public research lists go stale; date the export and refresh on a schedule you control.
Where the time goes back: The first pass of link collecting happens while you supervise, instead of opening dozens of tabs by hand.
FAQ
Why credit an Operator review post?
Can it fill forms?
Source and credit
Inspired by u/No-Definition-2886 on r/ChatGPTPro. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- I am among the first people to gain access to OpenAI’s “Operator” Agent. Here are my thoughts.
- Creator
- u/No-Definition-2886 on r/ChatGPTPro
- Published on
- Original date
- Jan 24, 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 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Public-only; capped.
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.