Browser-agent builder solves stale-page races with control epochs and page revisions
OyaAI · reddit · 2026-10-29
A developer building a browser where humans and agents share tabs explains the hardest design problem: staleness. By the time an agent's planned click lands, a modal, human takeover, or navigation may have changed the target. Their fix: every agent call carries a control epoch (who is driving the tab) and the page revision the plan was computed from; on mismatch the call fails with a stale-target error and the agent must re-read. Tab open/close is human-only. The cost is more round trips and treating staleness as a normal outcome; the benefit is no silent wrong clicks on submitted forms. He asks how Playwright/CDP users handle the same race.
More from coding & agent
- x401 Protocol Aims to Give the Agentic Web Verifiable Identity Proof at HTTP Level — csuwildcat · 2026-10-29
- ExtraHand Debuts as an Outer Loop to Route Multiple Models Into Your Coding Agents — cneuralnetwork · 2026-10-29
- Mirendil Launches Lor, Agents That Run Hundreds of Parallel AI R&D Experiments — shayan_ · 2026-10-29
- Oqoqo: hillclimb your MCP server with evals across 11 coding agents — pegasus013 · 2026-10-29
- ProgramLab gives agents 1,261 real-world programs to train and rebuild on, solo or in teams — jyangballin · 2026-10-29
- Android Studio Rabbit 2 Ships: Bring Claude, Codex or Any of 40+ Agents Into Android Dev — rseroter · 2026-10-29