# Turn repeated browser work into persistent programs

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

---

## Turn repeated browser work into persistent programs

ID: MHC-D-RESEARCH-1171 · Version: 0.1.0 · Kind: heuristic
Source: https://vedokrok.com/knowledge/turn-repeated-browser-work-into-persistent-programs

Use the browser to learn the path; use code to stop relearning it every time.

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

### Use when

- A browser agent repeatedly rediscovers the same navigation and action sequence on a site.

### Avoid when

- Do not freeze brittle selectors or bypass site rules. Persistent automation still needs authorization, monitoring and recovery.

### Explanation

After a browser interaction pattern becomes stable, encode the repeatable mechanics in a script or reusable skill. Let the live browser remain the state and feedback surface for checking whether the program still matches reality. Fall back to exploratory interaction when the site changes.

### Example

An agent first learns how to export a monthly report through the UI; after repeated success, a reusable automation handles the known sequence while the browser verifies the resulting state.

### Check

Repeated work uses a versioned, testable action path and still detects when the live site no longer matches it.

### Limits

- Do not freeze brittle selectors or bypass site rules. Persistent automation still needs authorization, monitoring and recovery.

### Evidence and sources

- supports: Repeated browser interactions can be moved into persistent programs or reusable website skills while live browser state remains the feedback surface. — RS-05CEF906EF829016. Persistent automation becomes stale when websites or permissions change; it still needs error handling, observation and a fallback to fresh discovery. (8:12, turn browser actions into persistent programs, within a harness that continues until a verifiable goal is reached)
- RS-05CEF906EF829016: Codex, Behind the Harness — https://ai.engineer/talks/shRR1e2HXMk-codex-behind-harness

No review details supplied.
