Give the agent a real browser—not a simulation.
2025-08-20 · genesisA true story, reconstructed from the machine
The browser became a memory.
This is how ThinkRun learned to give AI agents something they never had: eyes, evidence, and a way back to the moment everything went wrong.
Software used to leave a trail of code. ThinkRun leaves a trail of understanding.
Execution log
Seeing is useful. Remembering every action is leverage.
session recording + artifactsCapture video, DOM state, screenshots, decisions, and the human correction.
extension · local · cloudHand the evidence back to the agent. Let it understand what to change.
screen recording → proposed fixNot a launch story. A learning curve with receipts.
The week the machine caught fire.
Peak · 155 commits · Mar 16 week
Every version changed what “seeing” meant.
Git recorded what changed. The development memory recorded why. Together they reveal six distinct acts.
Give the agent a browser.
The first 38 commits established the premise: a browser task system with sessions, screenshots, and a visible trail of execution.
Make the run observable.
Auth, task execution, video playback, artifacts, before-and-after screenshots, analytics, and real-time task plans turned a command into a session you could inspect.
Move into the browser people already use.
The Chrome extension and local-control path collapsed the distance between an agent’s plan and the user’s real tab. This was the peak sprint: 530 commits.
Turn evidence into a language.
Public share pages, embeds, recording feedback, MCP parity, and attach receipts made a browser run portable—something humans and agents could point to together.
The screen became the prompt.
Video import, large uploads, media derivatives, recovery, and finally in-page screen recording shipped live. Record what happened; let the agent propose what happens next.
Make the evidence reachable everywhere.
Agent-facing CLI/MCP parity, SEO/AEO, remote-control grants, connector work, and publish-drift guards moved ThinkRun from capability toward distribution.
“The system kept saying success at the wrong level.”The recurring lesson in ThinkRun’s development memory
Show it.Don’t explain it.
ThinkRun was built around a simple belief: when an agent can see the actual experience, the distance between feedback and a fix collapses.