Genesis
The browser automation service takes its first breath. The foundational promise is simple: programmatic control of the web should feel native to agents.
The development story2025 → now
A browser
learned to listen.
Not a polished origin myth. A living build log about teaching agents to see, act, and know when to hand control back.
scroll to run history
The premise
Software has always had a browser. Now the browser has an agent.
0commits, verified July 9
0unique merged PRs
0days of development
0commits in the peak week
August 20, 2025 · first commit
$ thinkrun --help
› One question started it all:
Can an agent work in a browser without becoming a black box?
› So we built the missing verbs.
navigate · observe · act · pause · resume · share
$ run the real thing
› One question started it all:
Can an agent work in a browser without becoming a black box?
› So we built the missing verbs.
navigate · observe · act · pause · resume · share
$ run the real thing
ThinkRun began as browser automation. It became a more interesting question: how do you give an agent a real browser—logged in, observable, interruptible—without asking humans to surrender trust?
The build, in six movements
Core engine
Authentication, task resilience, and the video player transform a command surface into a system that can keep context—and show its work.
Local becomes real
The Chrome extension and local bridge make the pivotal move: agents can work with the browser you already use, including the sessions where you are logged in.
Work can travel
Sharing, oEmbed, MCP parity, and hybrid upload turn a browser run from an ephemeral action into an artifact another person—or agent—can understand.
Teach once
Web recording, Activity Hub, and billing arrive. A workflow can be demonstrated, captured, and made repeatable rather than explained from memory.
Distribution
SEO, a connector gateway, and pricing clarity extend the work beyond a single interface: any capable agent should have a way in.
Three ways to workOne browser.
One browser.
Different distances.
Work in the browser on your desk. Keep your tabs, sessions, and the power to intervene.
← choose a distance
Receipts, not hype
We kept the difficult parts in the story.
Every number here is from the project’s timeline notes and raw git history. No lifetime cost figure is shown because verified data does not exist.
Background-tab screenshots captured in a near-hour live transport soak.
median 696ms · PR #687 fixService-worker suspensions or disconnects during those eleven five-minute idle gaps.
~57-minute test · June 12PRD thread pages in the memory wiki: the work’s interpretive layer, alongside git history.
verified July 9 refreshA deliberate blank
We won’t make up a number just because a big number looks good in a hero.
There is no verified lifetime token or dollar cost for the project’s 323-day history. So it is not on this page. The record includes the correction, too: an earlier timeline claimed estimates were verified. They were recomputed, corrected, and the lesson stayed.
The next commit is the pointHand off the browser.
Hand off the browser.
Keep the agency.
ThinkRun gives agents room to do real work—and gives people the ability to watch, step in, and understand what happened.
Built from the ThinkRun memory wiki · figures verified from repository records