← Back to library

Score browser agents on your own task list

u/TheReedemer69 ran six browser agents through everyday tasks such as job forms, logging in to fetch data, posting and troubleshooting. Ratings put ChatGPT agent worst, Manus capable but costly with bot-detection trouble, Perplexity Computer strong but pricey, Comet the best balance, and two local-model setups in the mix.

  • OutcomeBefore committing to a browser agent, run the same handful of real tasks through several and score speed, blocks, capability and cost.
  • SetupAn afternoon+
  • LevelIntermediate
  • Creditu/TheReedemer69 on r/AI_Agents
View original
Works with
Custom agentChatGPT agentManus

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 24, 2026

When should you use it?

  • You are choosing a browser agent
  • Vendor demos do not match your tasks
  • Cost per task matters

Not for: One-off tasks you could do by hand faster; Tasks on sites that forbid automation

What do you need, and what do you get?

You need

  • Five to eight real tasks
  • Test accounts
  • Scoring sheet

You get

  • Score table per agent
  • Notes on where each was blocked
  • Cost per task

How does it work, step by step?

  1. Pick real tasksChoose tasks you actually do weekly, from simple to tricky.
  2. Use test accountsRun on throwaway or low-risk accounts where you can.
  3. Run each agentGive every agent the same instructions and time limit.
  4. Score consistentlyRecord success, time, how often it was blocked, and cost.
  5. Retest quarterlyAgents change fast; rerun the same set every few months.

The prompt

Our own prompt, inspired by u/TheReedemer69 on r/AI_Agents and written to work in Custom agent, ChatGPT agent and Manus. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt5 variables
I am comparing browser agents. Task {n}: {task_description}. Success means: {success_criteria}. Time limit {minutes} minutes.
After the attempt, report: completed yes or no, steps taken, where you were blocked and why, and anything you needed from me.
Use only the test account {test_account}.

Inspired by u/TheReedemer69 on r/AI_Agents: Tested 6 browser use agents for real-world tasks — here's an honest breakdown + looking for recommendations. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Agents that run in a cloud browser get blocked more often than ones in your own browser, per the poster.
  • Cheap local models may fail even simple steps.

Our take

Vendor leaderboards age fast; a personal task list does not. Build a short suite of jobs you actually care about, run every candidate through the same suite, and score pass, fail, cost and friction. Include a login-gated task, a form task and a long wait task. Publish your rubric for your team so buying decisions are comparable. Use throwaway or low-risk accounts where possible, and give each agent the same instructions and time limit. Record success, time taken, how often it was blocked and the cost per task. The poster found agents running in a cloud browser were blocked more often than ones running in his own browser, which is worth testing for yourself. Cheap local models may fail simple steps. Rerun the same set every few months, because these tools change quickly. Skip sites that forbid automation. Write the scores down in one sheet, so a buying decision rests on your own tasks rather than vendor demos.

Where the time goes back: A small fair test saves months of paying for the wrong tool.

FAQ

Which one won?
For this poster, Comet was the best balance, mainly because it runs in the user's own browser; your tasks may differ.
Is a local setup worth it?
Not yet for this poster; it failed easy tasks on their hardware.

Source and credit

Inspired by u/TheReedemer69 on r/AI_Agents. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Tested 6 browser use agents for real-world tasks — here's an honest breakdown + looking for recommendations
Creator
u/TheReedemer69 on r/AI_Agents
Published on
Reddit
Original date
Apr 14, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Custom agent
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, bookings 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.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminPrompt✓ AI dry run

Audit how you manage your agent team, not only the agents

Have your chief-of-staff agent review the last 30 days of how you delegated, clarified, interrupted, corrected, assigned, approved and followed up across your agent team, score eight management areas with evidence, list your three biggest weaknesses, and draft a seven-day improvement plan, without changing any bot, routine or instructions until you approve.

Credit: Michael Fenech (@Michael_Fenech_)

Under an hour
Operations & AdminPrompt✓ AI dry run

Audit how your agents pick tools before buying more usage

Have your lead agent review the recurring jobs it can see, note which apps, scripts, browser sessions or full computer control each one relies on, flag jobs that take a heavier route than needed or rely on remembered facts, check permissions and fallbacks, and then propose three side-by-side experiments before anything is changed.

Credit: Michael Fenech (@Michael_Fenech_)

Under an hour
Operations & AdminPrompt✓ AI dry run

Brief an agent with nine fields, not a how-to

Before you hand a job to an agent, fill in nine short fields that name the result, the sources it may use, the deadline, what it may do alone, what needs your say-so, what it must never do, how to prove the work is finished, what to do when it gets stuck, and where to put the deliverable, then add a line that tells it to pick the simplest reliable method.

Credit: Michael Fenech (@Michael_Fenech_)

Minutes
Operations & AdminWorkflow✓ AI dry run

Build and launch a hobby web app with a hosted coding agent

Go from a feature list to a live web app with storage, analytics, sign-up email integration and a landing page, without writing the code yourself.

Credit: Günter Richter

An afternoon+