Repository navigation
what a run should log
An agent run produces an answer and a transcript. The transcript is long, hard to search, and usually gone by the time somebody asks "where did this number come from". A small log, written deliberately, answers that question in one line.
Here is the field list, why each one is there, and what to keep out.
| field | why |
|---|---|
| timestamp, UTC | every other field is meaningless without when |
| the final URL | after redirects, not the one you asked for |
| the value, raw | exactly as the page said it, before any cleaning |
| the value, normalised | what you will actually use |
| read or inferred | whether the page stated it or the model concluded it |
| the exit country | pages vary by market, and yours is a fact about the run |
| the identity seed | so the same browser can be reconstructed |
| outcome | done, not found, blocked, error, needs a person |
The first six each prevent a specific argument. The seventh makes the run repeatable. The eighth is the one people leave out and the one that makes a file of results usable rather than a file of successes.
This pattern runs through the whole corpus and it is the same reason each time: the raw string is a fact and the normalised value is a judgement, and when the judgement turns out wrong you want the fact still there.
It applies to prices, dates, statuses and addresses. Normalising values across sites is the general case, and collecting event and course listings is where getting it wrong is most expensive, because a numeric date read in the other order is wrong by up to eleven months and looks fine.
The browser's identity is deterministic from a seed. Recording it means a run can be reproduced with the same identity later, which matters when you are trying to work out whether a site treated you differently today or you were simply somebody else.
Without it, "it worked last week" is unfalsifiable. With it, the week-old run can be repeated exactly. The setting and how a session picks one are on the MCP server page.
Credentials, obviously, and also the things that arrive without being asked for: your name, your email, the account identifiers a logged-in page prints. A log is the artifact most likely to be shared, pasted into a ticket, or committed by accident.
The habit that works is to log the fields above rather than page dumps. A whole page read into a log file carries whatever the page was showing about you, which is the problem described in secrets in an agent task.
The full transcript. It is already somewhere, it is enormous, and it is not searchable in the way this log is. Reference it if your client gives runs an id; do not copy it.
Once per run rather than once per row: the task text, or a hash of it, and the model that ran it.
Six weeks later the question is never only "what did the page say", it is "what did we ask, and with what". A results file whose rows are perfect and whose prompt is lost is a file nobody can extend, because nobody can produce more rows the same way.
done and failed collapse cases that need different responses. The set that
earns its complexity:
- done with a value;
- not found, the page loaded and the thing is not there, which is a finding;
- blocked, the page would not serve, which is not about the data;
- error, the run broke, so retrying is reasonable;
- needs a person, a login, a code, an upload the agent cannot do.
The difference between the second and the fourth is the important one. "Not found" is an answer and "error" is the absence of one, and a file that scores them the same is a file you will re-run entirely instead of re-running the eleven rows that need it.
On list tasks. Forty rows, six of them empty, and no column saying why, is the failure described in running one AI agent task across a list of sites. The log fields above are what turn those six into a to-do list instead of a mystery.
What should an AI agent run record? Timestamp, final URL, raw value, normalised value, whether it was read or inferred, exit country, identity seed and an outcome from a small set.
Why record the raw value as well? Because the normalisation is a judgement and will sometimes be wrong. The raw string is the only thing that lets you redo it.
Why log the seed? So the run can be repeated with the same browser identity. Without it you cannot tell whether the site changed or you did.
What should never go in the log? Credentials, and the personal data that logged-in pages print into every read. Log fields, not page dumps.
Is done/failed enough for an outcome? No. "Not found" is a result and "error" is the absence of one, and they need different responses.
See also: validating an AI agent's output, which is what you do with the log once you have it, and extracting data to a CSV with an AI agent for the shape of the output file itself.
- No external figures are cited: this is a field list and an argument for it. The seed and exit settings named here are this project's own, documented on the MCP server page.
Eight fields and one line per run. The test of whether it is enough: can you answer "where did this number come from" without opening a transcript.
- OpenAI Operator alternatives
- Open-source Operator-style agents
- Is OpenAI Operator still available?
- OpenAI Operator vs Claude computer use
- browser-use alternatives
- Choosing an AI browser agent
- Open-source AI browser agents
- Open-source computer-use agents
- What is an AI web agent?
- AI browser agents vs traditional scraping
- Cloud browser infrastructure for AI agents, explained
- Browserbase alternatives
- Firecrawl vs an AI browser agent
- Skyvern alternatives
- Stagehand vs browser-use
- Project Mariner is gone: what replaced it
- Manus alternatives
- Gemini computer use vs Claude computer use
- A stealth browser MCP, reviewed honestly by its own wiki
- AI browser vs AI browser agent: which one do you want?
- AI browser agent vs RPA: which one fits the job
- AI browser agent vs n8n, Zapier and Make
- Vercel agent-browser alternatives, compared honestly
- What is an agentic browser? Definition and the two kinds
- Open-source agentic browsers: the three layers, compared
- Choosing an MCP server for browser automation: four axes
- Stealth MCP servers compared: Camoufox, nodriver, Patchright
- Playwright MCP alternatives, and the three you don't need
- Autonomous browser agents: the four rungs of autonomy
- What is actually free in the AI browser agent stack
- browser-use on GitHub: what the repo actually gives you
- Playwright MCP vs Chrome DevTools MCP: different jobs
- How to choose among MCP servers: a map by category
- Which MCP servers are worth adding to Claude Code
- MCP on GitHub: finding servers and judging them fast
- MCP vs an API: the decision, and what the wrapper costs
- MCP alternatives: when the protocol is the wrong shape
- Why does my AI agent get blocked?
- The timing signal AI agents give off
- Agent retry loops trip rate limits, not fingerprints
- Claude computer use detected as a bot
- browser-use getting blocked: what you can and cannot change
- Playwright MCP session blocked: four causes, four fixes
- Playwright MCP and captchas: what actually gets you past
- Cloudflare and a browser MCP server: what is being read
- Can an AI agent solve a captcha? The honest answer
- Getting an AI agent to fill out forms
- The best model for an MCP browser agent, and what it really costs
- Browser problem or model problem?
- How to use a Playwright MCP server with Claude Code
- Extracting data to a CSV with an AI agent
- Monitoring a page for changes with an AI agent
- How to let Claude Desktop control a browser
- How to add a browser to Cursor as an MCP server
- Using an AI agent to hunt for apartments
- Getting website data into Google Sheets with an AI agent
- Using an AI agent to download invoices from portals
- AI agents for web research
- Using an AI agent to test your own website
- How to add a browser to Cline as an MCP server
- Posting to social media with an AI agent
- Posting to Facebook with an AI agent
- Posting to Instagram with an AI agent
- Posting to X with an AI agent
- Automating LinkedIn posts: read this first
- Appointment bots: what they are and what an agent can legitimately do
- Track prices across sites with an AI agent
- Build a lead list with an AI browser agent
- Run an AI browser agent on a schedule
- AI browser agent with a local LLM: what changes
- Should you log your AI agent into your accounts?
- How to write a task an AI browser agent can follow
- Move data between two web apps with an AI agent
- The MCP server
- How the tools are shaped, and why
- Playwright MCP vs the Playwright CLI: which fits when
- Playwright MCP: browser is already in use, and the fix
- Playwright MCP best practices: four decisions that matter
- Playwright MCP with a proxy, and the three leaks it leaves
- A browser MCP server in GitHub Copilot: setup and limits
- Using a browser MCP server for web scraping: the pattern
- Which LLM for browser automation: the four properties
- How to build a browser agent, and what to take instead
- Getting an AI agent to log into a website: three routes
- MCP tools, resources and prompts: who controls each
- How many MCP tools is too many? The context arithmetic
- How to build an MCP server: the decisions, not the scaffold
- Local or remote MCP server: what changes, and what does not
- Writing an MCP client in Python: the thirty-line version
- Self-hosted AI agent: what one actually costs to run
- How long an AI browser agent takes per step, measured
- Text, HTML, snapshot or screenshot: what the agent should read
- Giving an AI browser agent a stopping condition
- Keeping an AI browser agent out of destructive actions
- Why did the AI agent click the wrong thing
- When the page changes under the AI agent
- Running one AI agent task across a list of sites
- Seeing a page as it appears in another country
- Getting data out of a dashboard with no export button
- Two browsers in one session: main and support
- Finding the dead links on a site with an AI agent
- Filling a CRM record from a company's website
- One form submission per spreadsheet row, with an AI agent
- Dated screenshots of a page as evidence
- Checking order and delivery status with an AI agent
- Reading a PDF that opens inside the browser
- Summarising a long page or thread with an AI agent
- Collecting every image on a page with its caption
- Collecting event and course listings with an AI agent
- Cancelling a subscription with an AI agent
- What an AI agent can and cannot do inside an iframe
- Shadow DOM and an AI agent: you can click it, you cannot read it
- How to add a browser to Codex as an MCP server
- What a page snapshot costs, per control
- How to let Gemini CLI use a browser
- Native selects and the ones that only look like selects
- Clicking by selector or by coordinates
- How long the agent waits before it gives up
- What a second browser costs
- Uploading a file with an AI agent, and why this one cannot
- Watching the agent work, and when it is worth it
- When not to use an AI browser agent
- Agent or script: deciding once instead of every time
- Using the keyboard instead of the mouse
- Secrets in an agent task: where they end up
- What an agent run should log
- Deduplicating what an AI agent collects
- Normalising values across sites
- Validating an AI agent's output
- Reading a table with an AI agent
- Driving a site's own search and filters
- The task works headed and fails headless
- How to let the AdaL CLI use a browser