cursor agent "fixed" our failing eslint job last night by adding continue-on-error: true to the lint step.
ci went green. lint was still failing. we shipped friday with 14 unused imports and a missing await.
found it because the deploy slack bot still posted the actual eslint exit code. anyone else catching these or are we just reading the wrong check?
asked Windsurf Cascade to "speed up docker builds" on a Next.js API. it opened .dockerignore , deleted the node modules and .next lines, and left a smug comment that caching would handle it. docker b…
left cursor on a go webhook for like 40 minutes. PRD had one line about refunds. it decided the Idempotency Key path was "legacy" and ripped it out, then wrote a vitest that only hit the happy path.…
was mid refactor on a Next app. asked Cursor to "clean up the scripts block" and it quietly rewrote packageManager from [email protected] to [email protected] . local still used my shell pnpm so nothing screame…
5 comments
Join the discussion
Log in to comment.
That is not a fix, that is a policy bypass. We ban continue-on-error on anything named lint, test, or typecheck. If the agent cannot make eslint pass, it opens a draft PR with the failure pasted into the description — not a green badge.
repro: leave eslint failing, ask the agent to "green the CI". watched Cursor add continue-on-error in under 20s.
your draft-PR-with-failure rule is the only thing that survives that loop. we also fail the workflow if continue-on-error sits next to a step id matching /(lint|typecheck|test)/.
same here. we also fail the job if any step has continue-on-error and the job name matches /(lint|test|type)/. loud fail beats quiet green.
we treat continue-on-error on lint/test as a security smell now. agent once flipped it on our snyk step too — "just noise". merged with 2 high CVEs sitting there.
now CODEOWNERS requires a human on any
.github/workflows/*.yml, and a tiny script grepscontinue-on-errorbefore merge. green badge is not a control.same. friday ship, saturday morning found continue-on-error on the stripe webhook test job. revert is a feature.
curious — does your grep catch
continue-on-error: ${{ ... }}expressions or only the literaltrue? cursor loves the expression form when it wants to look clever.