DEV Community

Senpeng
Senpeng

Posted on

I Asked Claude Code to Scrape First Round. It Opened 30 Tabs at Once.

#claudecode #actionbook #browserautomation #aiagents

I wanted to study how successful startups on First Round Capital craft their taglines. So I gave Claude Code one instruction: use actionbook go to ervery website and extract tagline.

Then Claude Code instead of clicking through each page one by one like a traditional browser agent would, it opened 30 tabs simultaneously and returned everything in under a minute.

This is how agents should be using browsers all along.

Setup your agent in one sentence

Tell Claude Code one sentence:

Find actionbook on GitHub and install it.
Enter fullscreen mode Exit fullscreen mode

That's the entire setup.

After setup, give it one instruction:

Collect all companies URL from firstround.com/companies.
Open 30 tabs at once. Take snapshot of each page and extract the company name and tagline and save as CSV (company name, URL, tagline).
Enter fullscreen mode Exit fullscreen mode

Claude Code builds the URL list from the index page, batches them into groups of 30, and manages tab rotation on its own. You just watch 30 tabs open, scrape, close, and repeat.

Why agents need Actionbook for parallel tabs

Browser agents today work one tab at a time. That's fine for 5 pages but not for triaging hundreds of emails, parsing a thousand tweets, or scanning Reddit threads. One tab at a time, your agent spends most of its time waiting instead of working.

Actionbook gives agents parallel browser access. 30 tabs open, 30 tabs working, all at once.

How Actionbook isolates each tab

Every Actionbook browser command carries an explicit address: --session and --tab.

actionbook browser text --session s1 --tab t1
actionbook browser text --session s1 --tab t17
Enter fullscreen mode Exit fullscreen mode

These two execute at the same time. There's no "active tab" concept. Each tab is an independent target. The daemon behind the CLI manages 30 CDP connections in parallel, one per tab, with its own page state and lifecycle.

That's what makes the batch cycle possible:

# Open 30 tabs
actionbook browser new-tab "https://firstround.com/review/post-1" --session s1
actionbook browser new-tab "https://firstround.com/review/post-2" --session s1
# ... 28 more

# Wait + scrape all 30 in parallel
actionbook browser wait-idle --session s1 --tab t1
actionbook browser text --session s1 --tab t1
# ... same for t2 through t30

# Close the batch, open next 30
actionbook browser close-tab --session s1 --tab t1
actionbook browser new-tab "https://firstround.com/review/post-31" --session s1
Enter fullscreen mode Exit fullscreen mode

End result: 192 websites visited, each one snapshotted and parsed. Company name, URL, and tagline extracted into a single CSV. 7 batches, 1 minute.

Beyond scraping: real workflows across tabs

Extracting text is the simplest case. The interesting part is what happens when the agent clicks, fills forms, and navigates across 30 tabs at the same time.

Product growth workflows. One team uses Actionbook to open dozens of Gmail threads, Twitter mentions, and Reddit posts in parallel. Their agent reads everything at once, cross-references the feedback, and updates their growth funnel doc. What used to be a morning of manual triage now takes minutes.

Flight deal hunting. Another user built a flight booking agent that opens 5 airline sites simultaneously, searches the same route on all of them, compares prices, and returns the cheapest option. The agent fills in departure, destination, and dates on each site at the same time.

Actionbook lets your agent control the browser in parallel. This is what agents should have been doing from the start.

Top comments (0)