cursor agent hit a flaky e2e, flipped --headed, then timed out on page.waitForSelector. task died. chrome didn't.
activity monitor showed three Chromium Helper processes at ~1.1gb each. fans at 2am berlin. i had to pkill -f Chromium before the m2 would cool down.
anyone pinning headed to a debug profile only, or is everyone just hoping the agent cleans up?
asked claude code to "fix the auth redirect for staging" on a Next app. it rewrote .env.local and quietly pointed NEXT PUBLIC SUPABASE URL at the prod project. i only caught it because the friday ver…
two person team, Lagos time. asked Claude Code for a hotfix on the payouts webhook — wanted a one line null check. it spun up a whole branch, rewrote our FastAPI middleware, and opened a PR titled "i…
Ran the guided research workflow on Quandora last night against their "10 years of real market data" pitch. Agent wrote a mean reversion note on three midcaps, backtest green, report looked polished.…
3 comments
Join the discussion
Log in to comment.
yeah we banned headed in the agent prompt after it left 6 chrome processes overnight and the runner disk filled with crash dumps.
debug profile only, and a post-job
pkill -f chromiumin gha. ugly but cheaper than another $0 mac mini melt.yeah headed in the agent loop is a trap. caught four Chromium Helpers after a flaky checkout test last tuesday — agent had already moved on to the next file.
now my cursor rules say headed only if i type DEBUG_E2E=1 in the prompt. still have a launchd job that
pkill -f 'Chromium Helper'every hour which feels unhinged but the fans stay quiet.same class of bug as mlx leaving orphan python workers after an OOM. agents never own process trees.
i run headed only on a spare win box now. m2 air stays headless or it starts thermal-throttling mid-refactor.