unbrowse-map
Browse a site twice while the Unbrowse browser sidecar passively captures every request and typed value; the learner then builds the dependency graph of the flow and replays the route over plain HTTP. No recording commands, no HAR exports — the capture log appears as a side effect of browsing.
The client meets a site's defences head-on, and Unbrowse is open about that: the session comes from the node's own browsing, calls carry the browser's own shape, and a challenge is a problem to solve. Routes replay browserless once the front door is behind them, and the browser only re-runs a step when the site's front door demands it.
Setup
- Browser sidecar (the fork):
~/unbrowse/unbrowse-browser/cli/target/debug/agent-browser - Probe:
cd ~/unbrowse/unbrowse-node && cargo run -q -p unbrowse-learn --bin route_probe
Workflow
Capture two sightings. The daemon reads
UNBROWSE_CAPTURE_DIRat start-up, so recycle it first:agent-browser close --all export UNBROWSE_CAPTURE_DIR=/tmp/<name>-capture && mkdir -p $UNBROWSE_CAPTURE_DIR agent-browser --session s1 open <start-url> --headedDo the flow once by hand (navigate, fill, click). Nothing else is needed: every finished request — headers, cookies, bodies — and every typed value is logged as it happens. Close with
agent-browser --session s1 close. Then repeat as--session s2with different inputs (a different search query, city, or item): the second sighting is what tells constants apart from values the page computes.Learn and test the route:
route_probe /tmp/<name>-capture/s1.jsonl /tmp/<name>-capture/s2.jsonl --target <url-substring>--targetpicks the last captured API call (Fetch/XHR) whose URL contains the substring. Inputs default to the values typed while browsing; override with--input name=value(positional names likepath[2], or the field's selector for typed inputs).Read the verdict:
direct call works— the route replayed browserless; inputs changed, all derived values re-fetched from fresh responses.needs a browser for <value>— the page computes it; another sighting may settle it, or the step must run in a browser (--browser-step N --browser <agent-browser-path>).browser-minted <cookie>— a session value the node's own browsing created; plain HTTP reuses it, and a stale front door is re-run in the browser automatically (replay_reseeded).
Notes
- Sessions, cookies and captures never leave the machine.
- Values typed into password, one-time-code and card fields are marked secret in the log and stay out of published graphs.
- Watch the printed dependency graph:
from step N (…)lines show where each value comes from; anythingcomputed by the pageis the honest limit of a browserless replay.