use-browser

use-browser — snapshot, act by ref, verify; the owner says yes to pay/post/send/delete

5dive browser drives a real Chrome on this box. Give any page verb a URL and it picks the profile itself: the host's one connected login, or the public profile (nothing logged in) when there is none. A box with zero connected sites can still browse and act on any public page. Connecting a site is only for the owner's own accounts — their inbox, their cart, their repo — and that is the connect-site skill, not this one.

The loop: ONE snapshot per decision

5dive browser snapshot <url> --interactive     # the refs you can act on
5dive browser act <url> --steps='[{"op":"click","selector":"ref=button/Star"}]'
5dive browser act <url> --steps='[{"op":"fill","selector":"ref=textbox/Title","value":"Bug: …"},
                                  {"op":"click","selector":"ref=button/Save draft"}]' --expect='Draft saved'

1. Snapshot the page with --interactive and pick refs from what it printed. Never invent a ref; a page you have not snapshotted is a page you are guessing about. A web app (Gmail) shows a loading screen first: add --wait-for='[role=main]' (or text=<words> the loaded page has). Exit 76 is not the page — a loading screen or a --wait-for that never came; run it again with a --wait-for, and do not ask anyone to log in.
2. Act on those refs. Steps are goto fill type click wait_for select press, run in order, in one tab under one lease. Without a URL, act continues on the page a served browser holds. Use type for search boxes and autocompletes that react to keystrokes, and fill for plain inputs: fill sets the value with no key presses, so a suggestion list never opens. type goes key by key ("delay_ms", default 50); pick the suggestion with a wait_for and a click.
3. Verify. --expect=<regex> grades the page as the steps left it, re-read for up to 5 s so a toast counts. Without it, act only says the steps ran — open the page.png it wrote before you tell anyone it worked.