Saccade

It is built for real browser work: signed-in admin pages, long forms, dynamic controls, iframes, rich text, uploads, and pages that change while an Agent is working. The Agent reads semantic objects instead of repeatedly transferring a whole page, and the browser waits locally before an action is dispatched.

Release candidate: @nanlogic/saccade 0.2.0 with Extension 0.4.0 . The same Extension candidate passed the release gate in Chrome and Edge. Release notes · Evidence

One exact tab per request. Every read and action names a leased tab_id ; each tab has one writer and stays isolated from other Agent sessions.

Current page state without polling. Ask for a bounded full view once, then read browser-pushed deltas after a known revision.

Actions that wait and verify locally. Visibility, enabled state, stable geometry, topmost state, and current action authority are checked under one deadline. The receipt includes the resulting semantic transition.

Safe recovery. A replaced object stays stale. An action with an ambiguous side effect is not replayed automatically.

Less model work on forms. Independent fields can be preflighted and sent as one batch; submit, navigation, and upload remain explicit actions.