A development story in six acts

The browser remembers.

AI could write the fix. It just couldn't see what happened. So we built it a memory.

This is the story of ThinkRun: a screen recorder, a real logged-in browser, and a structured audit trail for AI coding agents.

scroll to execute
00 / The missing sense
The web was visual. The agent was brilliant. Between them was a blank terminal.
SESSION CAPTURED00:01:42

human_action → click
viewport → 1440 × 900
console → 2 errors
network → 1 failed request
artifact → html + json + markdown

Now the agent can see the bug.

thinkrun.ai / recording / live
Recording in progress

A video for you.
Structured context for your agent.

One artifact travels in two directions: a human watches the moment; an agent reads exactly what happened.

03 / Shipped in public

A product made of
hard-won corrections.

APRIL 2026

Memory becomes infrastructure.

Daily logs begin accumulating the failures, recoveries, and operating rules that would become the development wiki.

Source · memory/daily
Earliest indexed daily log · 2026-04-22
JUNE 12, 2026

ThinkBrowse becomes ThinkRun.

A rename across product surfaces—while preserving legacy config, environment variables, storage keys, and existing user continuity.

MIGRATION, NOT A REPAINT
Source · memory/technical-patterns.md
JUNE 17, 2026

Recording escapes the extension.

In-page screen recording ships live. Capture, upload, and analysis are proven end-to-end in production.

Source · memory/prd_0089_web_recording.md
Status · complete & live
JUNE 22, 2026

The activity trail gets a home.

Recordings and sessions become one navigable history—posters, source filters, detail views, and honest empty states.

Source · memory/prd_0090_activity_hub_redesign.md
4 tasks · 4 PRs
JUNE 26, 2026

The invisible site learns to speak.

The SPA had served answer engines an empty root. ThinkRun rebuilt its public surface as prerendered, machine-readable pages.

Source · memory/prd_0101_spa_seo_aeo.md
18 routes · 25/25 crawler checks
JULY 2026

The product remembers how it was built.

Corrections stop disappearing into transcripts. They become linked, searchable operating knowledge.

Source · memory/MEMORY.md
Wiki index · 161 pages

The receipts are part of the product.

0Pull requests found in the generated merge historymemory/threads/pr-merge-log.md
0Pages indexed by the development memory wikimemory/MEMORY.md
25/25Page × bot checks passed after the crawler rebuildmemory/marketing/LOG.md
04 / A system that learns

Every mistake should become infrastructure.

Feedback / reliability

Smoke the headline command

Public entry points need run-the-binary proof, not file-listing confidence.

Feedback / judgment

Prove before create

Before building a new system, prove the capability does not already exist.

Project / product

Real browser, real state

Local, extension-agent, and cloud paths are different contracts—not cosmetic modes.

The loop

Record → understand → fix → remember

The artifact that helps an agent solve today's bug should make tomorrow's agent wiser.

05 / What are we really building?

Not an agent.Its senses.

ThinkRun gives your coding agent the browser you already use, the moment you actually saw, and the evidence it needs to act. A shared visual memory between the human who noticed and the machine that can fix it.

See what ThinkRun sees ↗