mirror of https://github.com/callstack/agent-device.git synced 2026-09-14 20:06:34 +08:00

Files

T

Michał Pierzchała d8e6bb7aa7 fix: add web viewport control and screenshot aliases (#865 )

* fix: add web full-page screenshots

* fix: add web viewport command and screenshot aliases

* fix: address viewport CI regressions

2026-06-24 19:35:03 +02:00

1.4 KiB

Raw Permalink Blame History

Web Backend

Web automation uses a managed agent-browser backend as an implementation detail.

Runtime web commands resolve the backend only from the state-dir managed install at tools/agent-browser/<version>.
Normal --platform web commands do not install the managed backend on first use. If the backend is missing, they fail with a setup hint.
Use agent-device web setup before first web automation and in CI/sandbox bootstrap steps.
Use agent-device web doctor to run the backend health check.
The managed install respects --state-dir / AGENT_DEVICE_STATE_DIR.
Web automation requires Node 24+ while the rest of agent-device keeps its Node 22 baseline.

Default first-run flow:

agent-device web setup
agent-device open "https://example.com" --platform web
agent-device snapshot -i --platform web
agent-device viewport 1280 900 --platform web
agent-device screenshot ./artifacts/web-full.png --platform web --fullscreen
agent-device network dump 25 --platform web
agent-device close --platform web

Do not document direct agent-browser commands as agent-device features. Web network dump is the narrow exception: it adapts agent-browser network requests to the existing agent-device network evidence shape. Browser-specific network routing/interception/HAR, CDP, React web, tabs, downloads, auth vaults, and profiling stay out of the minimal web surface until there is an explicit agent-device command design for them.

1.4 KiB Raw Permalink Blame History

Web Backend

1.4 KiB

Raw Permalink Blame History