# Pin the browser environment when comparing agent behavior

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Pin the browser environment when comparing agent behavior

ID: MHC-D-RESEARCH-1172 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/pin-the-browser-environment-when-comparing-agent-behavior

If the browser moves under your feet, you do not know what the agent change caused.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- Browser-agent benchmarks change between runs because the environment changes along with the model or harness.

### Avoid when

- A perfectly fixed browser is not production. Use it for causal comparison, then test realistic variability.

### Explanation

For controlled comparison, pin relevant browser version, locale, viewport, extensions, login state and seed data. Reset the environment between trials. After the comparison is stable, add representative environment variants to test robustness.

### Steps

1. Pin browser and relevant runtime versions.
2. Control locale, viewport and login state.
3. Reset task data between trials.
4. Run environment variants after the controlled baseline.

### Example

When comparing two browser agents on expense submission, keep the same browser version, account state and seeded expense before testing different models.

### Check

The benchmark can distinguish agent changes from environment changes, and later robustness runs intentionally vary the environment.

### Limits

- A perfectly fixed browser is not production. Use it for causal comparison, then test realistic variability.

### Evidence and sources

- supports: Keeping the browser environment consistent improves the interpretability of comparisons between agent strategies by reducing unrelated execution variation. — RS-6442420642D13047. A pinned environment can hide real-world variability. Use it for controlled comparison, then test against representative live conditions. (Sections on measuring the harness against a baseline, combining browser interaction with code and keeping the browser environment consistent)
- RS-6442420642D13047: Bringing agents onto the world wide web — https://ai.engineer/talks/GqoNrUz8hEU-bringing-agents-onto-world-wide-web

No review details supplied.
