ThinkRun
A build log, not a brand myth

We taught a browser
to show its work.

ThinkRun began with a stubborn idea: when software can act for you, it should leave behind a story you can inspect.

THINKRUN / DEVELOPMENT RECORDSCROLL TO REPLAY2025 → 2026

Most software tells you it worked. ThinkRun lets you watch the evidence arrive.

The original interface

One command.
Then a question.

Every chapter started as a test of the same belief: an agent should see enough to act — and leave enough behind to be trusted.

thinkrun — build history
$ thinkrun replay origin
 
✓ browser session opened
✓ actions made inspectable
✓ evidence packaged for the next human — or agent
 
$ what changed?

Six chapters.
One throughline.

Not a straight line. A sequence of systems made more observable, more local, more shareable, and more honest about the messy reality of browsers.

01
2025.08 — 2025.11

Genesis

The first browser automation service: a small, direct wager that agent work needed a place to run.

browser automation servicePR #1
02
2025.12 — 2026.01

The engine learns resilience.

Identity, task resilience, and a video player turned execution into something people could return to, not just trigger and forget.

ClearAuthtask resiliencevideo player
03
2026.02 — 2026.03

Bring the agent closer.

The Chrome extension and local bridge brought control to the browser people already use — while Loom-style sharing made the result visible beyond the terminal.

Chrome extensionlocal bridgeLoom sharing
04
2026.04 — 2026.05

Make it portable.

Share surfaces, embeds, and MCP parity turned a private run into an artifact that can move between tools, people, and agents.

oEmbed@thinkrun/mcp parityhybrid upload
05
2026.05 — 2026.06

Capture the bug, not the retelling.

Web recording, the Activity Hub, and billing brought the product’s clearest proposition into focus: show your agent what happened once.

web recordingActivity Hubsubscription billing
06
2026.06 — 2026.07

Let the work travel.

Search, connector infrastructure, and pricing clarity shaped a product that can meet agents where they already work — without pretending browsers are simple.

SPA SEOconnector gatewaypricing SSOT
The receipts

The story has numbers. So we kept the provenance, too.

0commits in the verified record
0unique merged pull requests
0days of development
0PRD threads

Counts are drawn from the repository’s corrected, verified timeline: 1,571 commits, 572 unique merged PRs, 323 days from 2025-08-20, and 62 PRD thread pages. No lifetime cost or token total is shown because the record explicitly says none exists. READ THE METHOD →

The point of the whole thing

An agent can move fast without becoming invisible.

ThinkRun is an attempt to make the work inspectable: the browser session, the recording, the actions, and the handoff. The story is still being written — in public, in the artifacts.