← Back to library

Many parallel searches turn a question into a dataset

lukasthoms, joking about yet another branded AI assistant name, had many Claude agents in parallel run 4,654 searches cataloging what companies call their bots. Their results: assistants given human names lean heavily female, the split varies by industry, and naming launches dropped in 2026 compared with 2025. One favorite was a hockey team's support bot.

  • OutcomeSplit a fun research question into thousands of searches across parallel agents, collect the results into a table and look for trends.
  • SetupAn afternoon+
  • LevelIntermediate
  • Creditlukasthoms on Hacker News
View original
Works with
Claude

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

When should you use it?

  • You have a question that needs many searches
  • You want a table, not an essay
  • You can check samples by hand

Not for: Questions answered by one source; Research needing paywalled data

What do you need, and what do you get?

You need

  • Clear question and fields to collect
  • Search tool for agents
  • Budget

You get

  • Dataset table
  • Trend notes
  • Sample checks

How does it work, step by step?

  1. Define fieldsDecide exactly what each row should record.
  2. Split the searchesDivide the space, such as by industry or year.
  3. Run in parallelHave agents search and fill rows with a source link each.
  4. DeduplicateMerge duplicates and drop rows without a source.
  5. Check a sampleVerify some rows yourself before trusting trends.

The prompt

Our own prompt, inspired by lukasthoms on Hacker News and written to work in Claude. Values in lime are placeholders.

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

Prompt3 variables
I want a dataset answering: {question}. Fields per row: {fields}, plus a source URL.
Split the search space into {n} parts, search each, and return rows only when a source supports them. Merge duplicates, then summarize trends and list ten random rows for me to check.

Inspired by lukasthoms on Hacker News: Comment in Every AI Name. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Thousands of searches cost money; set a cap.
  • Agents can invent rows; require a link for each.
  • Trends from search results reflect what is easy to find.

Our take

lukasthoms built this for fun, but the pattern behind it is genuinely useful: break a broad question into thousands of narrow searches, run them in parallel, and assemble the results into a table you can analyze. The quality depends on a few unglamorous rules. Decide the fields before launching, such as company, bot name, industry, launch year and source link, so agents return comparable rows. Require a link for every row, merge duplicates, and check a random sample by hand before believing any trend; a single agent that misreads a page can skew a small category. Be careful about what conclusions mean. Searches find what is publicized and indexed, so a drop in launches could partly reflect fewer press releases rather than fewer bots, and the author rightly avoids over-interpreting. Set a budget before starting, since thousands of searches add up, and save raw results so you can rerun the analysis later. The same approach works for competitor pricing, local service listings or tracking how a term spreads.

Where the time goes back: A curiosity question turns into a real dataset in an afternoon.

FAQ

How many searches?
4,654, per the developer.
What did it find?
Most human-named bots have feminine names, varying by industry, and fewer launches in 2026.

Source and credit

Inspired by lukasthoms on Hacker News. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Comment in Every AI Name
Creator
lukasthoms on Hacker News
Published on
Hacker News
Original date
Oct 11, 2026
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, 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 23, 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 Career & Learning

All 37 Career & Learning playbooks →

Related playbooks

Career & LearningWorkflow✓ AI dry run

Check an AI-edited paper for dropped or invented citations

After any AI rewrite of academic text, compare citations before and after, confirm each source exists and check that claims still match their sources.

Credit: u/ringringpssy on r/ChatGPT

Under an hour
Career & LearningPrompt✓ AI dry run

Clip bookmarks into a personal ask-me store

Save articles and bookmarks into a folder your agent indexes, then ask questions answered only from what you saved, with links back to the clips.

Credit: Miles Deutscher (@milesdeutscher)

Minutes
Career & LearningPrompt✓ AI dry run

Compare your project plan with its fastest possible timeline

Have an AI interview you task by task about a project you keep postponing, estimate how long each task would take with no waiting at all, set that beside your real schedule, name the three largest gaps and whether each comes from waiting, approvals, hesitation or genuine effort, and give you a one-page plan to close the largest gap this week.

Credit: AI Guides (@free_ai_guides)

Minutes
Career & LearningWorkflow✓ AI dry run

Run a job-application agent with a cap and no cold DMs

Let an agent search and apply to matching jobs from a written profile, with a daily limit, a tracking sheet and approval before any direct message.

Credit: u/Sanshuba on r/openclaw

Under an hour