A browser agent for checking your web app.

A browser check starts with a running app

1. Open the web project's folder in LoopCode desktop.
2. Start the project's development server with the appropriate command and permissions.
3. Give the agent the local URL, the behavior to exercise, and the result you expect.
4. Inspect the browser evidence and terminal output, then review the code diff.

Open the app at http://localhost:3000. Add two items to the
cart, increase one quantity, and confirm the displayed total
matches price × quantity. Check the empty-cart state too.
Report what you observed and any steps you could not verify.

Use browser observations for the right questions

Interaction is useful for a form that should show an error, a cart that should recalculate, or navigation that should preserve state. A screenshot can support a visual review, but cannot prove that a hidden request was authorized or a calculation handles every input.

Ask for concrete observations: which page was opened, which controls were used, which result was visible, and which checks failed or were unavailable. Keep the regression test for the underlying logic even when the browser interaction succeeds.

Know the environment and the limits

Use a disposable test account for flows that change data. Review destructive or external actions before running them. If a step cannot be performed, have the agent state that limitation rather than describe an imagined successful result.

• These tools depend on LoopCode desktop's browser integration; do not assume they are available in a standalone CLI or remote VS Code session.
• The development server must be reachable from that browser environment.
• Authentication, permissions, and sensitive actions still require appropriate access and developer judgment.
• One browser state does not verify all screen sizes, keyboard navigation, or supported browsers. Add those checks explicitly.

Combine visual and programmatic verification

For a web change, define a small verification matrix: unit tests for calculations, integration tests for requests, type checks for interfaces, and browser interactions for the user flow. Check the actual exit codes and assertions. A careful workflow is more meaningful than an unsupported promise of fewer tokens or perfect accuracy.