Remote ArcREMOTE ARC
Test a website in a real browser
Check navigation, forms, accessibility and responsive layouts with screenshots and browser evidence.
With Arc
Test the website or app I own at the URL I provide. Read the browser-testing skills, identify representative user flows and screen sizes, run bounded real-browser checks and capture failures with screenshots/logs. Avoid submissions or external writes unless included in my authorization, and report only checks that actually ran. Check current connections, permissions and dependencies first. Use real tools and continue from observations; claim only results actually observed or verified. Inspect uncertain external effects before any repeat. Report specific missing capabilities.
Arc requirements
A running app, authorized test scope and an available local browser-testing engine.
Arc boundaries
Passing selected checks is not proof that every user flow works. Production data changes need explicit scope.
With Connect: example request
Test the website or app I own at the URL I provide. Read the browser-testing skills, identify representative user flows and screen sizes, run bounded real-browser checks and capture failures with screenshots/logs. Avoid submissions or external writes unless included in my authorization, and report only checks that actually ran.
With Connect: how the work proceeds
Choose user flows and start the available browser environment. Exercise interactions and inspect screenshots, logs and failures.
Connect tools and permissions
read_skill · read_file · write_file · start_process. A running app, authorized test scope and an available local browser-testing engine.
What useful evidence looks like
Actual browser results, screenshots and reproducible failing cases.
Know the boundary
Passing selected checks is not proof that every user flow works. Production data changes need explicit scope.