A repository tells its own story

We taught software
how to see.

Not with a better prompt. With a browser that can act, remember what happened, and hand the evidence to the next mind.

›thinkrun story --replay
Scroll to open the flight recorder
Agents had hands. They needed eyes, memory, and a receipt.

The first ThinkRun commit landed August 20, 2025. The premise was small. The distance between a click and trust was not.

No mythology. Just receipts.

The build, counted.

Every headline figure on this page comes from the repository’s corrected raw-history recomputation and development memory.

0commits examined
0unique merged PRs
0product threads connected
0days in the record
✓ Snapshot window: 2025-08-20 → 2026-07-09  ·  6 distinct phases  ·  source: raw git history + memory wiki
The flight recorder

Six versions
of the same question.

How do you give an agent browser access that is useful, inspectable, resilient, and safe? Drag the reel, use the arrows, or just keep scrolling.

01 / GENESIS

A window
opens.

The first browser automation service learned to create sessions, take instructions, and survive deployment.

  • Initial browser automation service
  • First merged PR: #1
AUG 20 — NOV 30, 2025 · 38 commits01
02 / CORE ENGINE

Seeing becomes
doing.

Authentication, task resilience, and replay turned a remote browser into a working system.

  • ClearAuth
  • Obstacle recovery
  • Video player
DEC 1, 2025 — JAN 31, 2026 · 279 commits02
03 / EXTENSION + LOCAL

The agent enters
your Chrome.

The boundary moved. The agent could work where you were already signed in.

  • Chrome MV3 extension
  • Native host + local bridge
  • Loom-style session shares
FEB 1 — MAR 31, 2026 · 520 commits03
04 / SHARING + MCP

A session becomes
a language.

A share could carry replay, context, and a path for another agent to continue the work.

  • oEmbed share videos
  • @thinkrun/mcp parity
  • Hybrid recording upload
APR 1 — MAY 15, 2026 · 280 commits04
05 / RECORDING PIPELINE

Show, don’t
prompt.

Screen, voice, clicks, console, and network became one time-synced artifact.

  • In-page screen recording
  • Media derivative pipeline
  • Activity Hub redesign
MAY 16 — JUN 17, 2026 · 306 commits05
06 / DISTRIBUTION

The tool learns
to travel.

SEO, connectors, remote control, and one pricing source made the tool easier to enter anywhere.

  • Remote browser control grants
  • Connector gateway
  • Pricing source of truth
JUN 18 — JUL 9, 2026 · 148 commits06
01 / 06
The velocity signature

One week.
155 commits.

March 16–22, 2026 was the peak. Not a launch spike: a systems spike. Extension, local bridge, sharing, recovery. The week ThinkRun stopped being merely a remote browser and started becoming a way of working.

155 commits · Mar 16–22
What ThinkRun changed

The bug report
grew a memory.

A screenshot tells a person what was visible. A ThinkRun artifact gives a person or agent the trace: the moment, the action, the console, the network, the intent.

It is built for one useful handoff: “Here is what happened. You can start from here.”

00:17 / 01:24
Time-synced evidencelive trace
“This button jumps.”voice
Layout shift detectedscreen
Console warning attachedconsole
Failed request linkednetwork
The most ThinkRun moment

The timeline failed review.

An earlier version estimated six numbers, called them verified, and invented a plausible caveat to explain the arithmetic. The memory wiki challenged it. Git recomputed it.

The product built to make agents observable had to observe itself.

Independent recomputation · July 9, 2026
Total commits1,5701,571
PRD threads5962
Phase 3 PRs~350147
Strict phase sum—1,571 ✓
VERIFY THE ARTIFACT

No lifetime cost figure is shown because the repository does not contain verified lifetime cost data.

The session is still running

Let the work
explain itself.

Record the thing that broke. Give it context. Hand the evidence to a person or an agent—and keep moving.

Start with ThinkRun ↗