browser-use

Using the built-in browser

curl gets you the signed-out version of everything that matters, because the session lives in a browser. agentglass has one, already signed in to whatever the person using it is signed in to. agentglass-browser drives it, and it is built for you rather than lent to you: the whole DevTools protocol is here, so is running JavaScript, so is faking a broken API.

Start here, in this order

agentglass-browser health                     # is anything listening; always answers
agentglass-browser open https://example.com/app
agentglass-browser observe --shot             # EVERYTHING at once

observe is the verb to reach for first. One answer with the url and title, whether the view is visible and focused, the console and the network since last time, a tree of the interactive page addressed by role and accessible name, the current value of every input, and optionally the picture. Polling six verbs in turn is where the time goes.

After the first look, ask for only what changed:

agentglass-browser observe --delta            # {delta:true, added, removed, changed, same, console, network}
agentglass-browser click e12 --observe        # `after` is a delta too

added are whole nodes, removed are ids gone from the page, unlisted are ids still there but past the tree's cap, changed is {e, field: new value} (null = the field went away), same is how many did not move. New console and network rows only. form, storage and viewport appear only when they changed — absent means unchanged. Positions (at) are not diffed. After a navigation, with no earlier look, or after a look you only saw part of (--max-tokens, --summary), you get the full answer with delta:false and a reason. Plain observe is always the full page.

The baseline (and checkup's "since your last checkup") is kept per --as name; callers without one share a single baseline, so pass --as to get your own.

click and press wait for what they caused (the navigation, or a quiet page with no request in flight, capped at 1 s) and answer with an effect: navigated, newDocument, newErrors, failedRequests, dialog, settledBy. Often that is all you need to know — no look at all.