A window opens.
Initial browser automation turned navigation, screenshots, and extraction into the first primitive verbs of a new sense.
An origin story · verified through July 9, 2026
ThinkRun began with a stubborn idea: when something breaks in a browser, an agent should receive the evidence—not a paraphrase of the evidence.
The premise
A browser is not a page.
It is a place where intent leaves evidence.
The first commit landed on August 20, 2025. The premise fit in one sentence. The work did not.
The build log
Not a bot that clicks. A system that can perceive, act, recover, and leave enough evidence for the next person—or the next agent—to understand what happened.
Initial browser automation turned navigation, screenshots, and extraction into the first primitive verbs of a new sense.
Identity, task resilience, and playback made browser work durable enough to survive more than a happy-path click.
The extension and local bridge changed the boundary: the agent could work in the browser session you already trusted.
Share links, oEmbed, MCP parity, and hybrid upload let a replay carry its context between people and tools.
Screen, voice, clicks, console, and network became a synchronized handoff—so “watch this” could finally be complete.
SEO, connectors, remote control, and a pricing source of truth moved ThinkRun from a product into a place agents could enter from anywhere.
The product in miniature
Choose an evidence layer. The story changes because the artifact changes.
Screen replay
A replay gives an agent the moment as you saw it: the layout, the cursor, the sequence. It replaces “it looks wrong” with an inspectable starting point.
The receipts
All figures are from the independently recomputed July 9, 2026 snapshot: raw Git history first, then the memory wiki for context.
The second source of truth
Git says what changed. The memory explains why: a CORS allowlist drift, a dropped pixel, a broken install command, an auth outage, and the decisions that make the same failure less likely next time.
The interesting part is not that ThinkRun has history. It is that the history can answer back.
The most ThinkRun part
An earlier story artifact called several estimates “verified,” including an invented explanation for numbers that did not add up. Independent recomputation caught it.
That correction belongs in the story. A product built for observable work has to be observable about its own claims.