Browser
Use browser workflows to inspect a running application, identify issues, and verify the experience users will see.
Verification loop
A useful browser workflow follows a repeatable path: build the app, launch the server, navigate to the relevant page, inspect the UI, identify the issue, repair it, and verify again.
- Start from a known URL
- Inspect visible state and interactive elements
- Use screenshots for visual issues
- Check the browser console for runtime errors
- Report the final URL and result
What browser access can do
Browser access can help with navigation, inspection, interaction, and visual verification. It should be granted only for the pages and duration needed by the task.
Keep verification concrete
Instead of asking to "check the app," ask the agent to open a specific route, test a named interaction, capture the resulting state, and report any console errors.
Security and privacy
Do not grant browser access to accounts, private dashboards, or sensitive data unless the task requires it and you understand the exposure. Close or sign out of sessions that should not remain available to the agent.