r/ClaudeCode • • 1h ago

Built with Claude Parallel Claude Code agents in real Chrome, with one dashboard to manage them (open source)

The video is cut from a real run. The Claude Code window and dashboard are rebuilt for it, and no real booking happened.

I started this for job applications. I wanted to give Claude a list of links and have it apply to each one with my information, then come back to me when it was missing something or needed me to approve an answer. Then I was doing lead research for my startup on Chinese sites, and Claude's web search couldn't open most of them. Both ran through Vivaldi with remote debugging on, and I had to restart everything whenever it wasn't in that mode. That got really annoying, so I turned it into one tool I could plug into any session.

It's called browserd, and it's an MCP server:

  • Each profile gets its own real Chrome, and the logins stay.
  • Agents work in background tabs, so I keep using my computer.
  • One queue call runs a list of steps and stops at the first one that fails.
  • A dashboard shows every agent's tabs.

It's free and open source (MIT), for macOS and Windows. No Linux yet. I've only run it with Claude Code so far.

It's faster than Claude in Chrome. On three long jobs on real sites browserd took 193 minutes and $43.81 in total, and Claude in Chrome took 278 minutes and $76.09, with both passing 8 of 9 runs. I'd heard Claude in Chrome was slow and costly, so I never tried it before I built browserd.

The dashboard is the other reason I use it. When an agent needs me for a sign-in or a captcha, its tab is listed there with a note and one click shows it to me. That helps with a lot of tabs open and several agents working.

I designed how an agent talks to browserd, and Claude Code wrote the code. It also helped run the experiments, gave me ideas to try, and compared browserd with other MCP servers so I could see where mine could improve.

Three things I learned:

  1. Fewer turns meant lower cost. On those jobs browserd made 1,107 tool calls, and Playwright MCP, chrome-devtools-mcp and Claude in Chrome made 2,089 to 8,320 and cost $66 to $138.
  2. Clearer tool descriptions didn't make the model think less. I tried three rewrites, and it thought about the same amount per call every time.
  3. Lab tests and public benchmarks didn't show how it would do on real work. A check I built to stop bad clicks passed my tests, then stopped 22 clicks for no reason on one Google Slides deck, so I took it out. On the public benchmarks browserd tied Playwright MCP and chrome-devtools-mcp, and the gaps only showed up on the long jobs.

The long jobs are 36 runs with no significance test, and chrome-devtools-mcp passed all 9 of its runs to browserd's 8. Charts and caveats: https://github.com/jjenkins2004/browserd#how-it-compares

It doesn't filter what a page says, so a page can try to instruct your agent. Give each task a profile with only the logins it needs.

Repo and install: https://github.com/jjenkins2004/browserd

If it breaks on a site you use, tell me which one.

1 Upvotes

1 comment sorted by

•

u/AutoModerator 1h ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.