browser-automation

Automating browser UI testing with long-lived SSE streams requires offloading feed verification to server-side logs to prevent the automated browser environment from hanging. This approach manages the network request monitoring without blocking the testing session.

Tab orchestration manages browser tabs to prevent agent collisions during automated UI testing. It safely handles tab ownership so multiple testing agents can interact with the web interface without conflicting.

The best way to verify Datastar UI updates is using an automated browser skill to navigate to the local pod, take screenshots to verify layout, and inspect console logs for errors. This removes the need to manually switch browser windows.

Yes, Chrome-MCP supports taking screenshots and inspecting console logs for local web interfaces. It facilitates visual and functional testing of UI components like world rosters, agent pages, and datom browsers.

Automated browser testing hangs when verifying SSE streams because the long-lived feed keeps the network connection open indefinitely. You must handle this by offloading feed verification to server-side logs instead of monitoring the stream directly.

Yes, you can test world rosters, agent pages, and datom browsers in a single automated browser session. The automation skill facilitates UI verification for all these components while managing tab ownership to prevent collisions.