Cursor Harness
Cursor Agent / Plan / Ask / Debug
Measured Strengths
- Per-task cloud VM isolation makes the git diff an honest deliverable boundary.
- Closed harness-enforced mode set (Agent / Plan / Ask / Debug) prevents ambiguous permission prompts.
- Declared environment.json / Docker configs avoid split-brain read/write directory mismatches.
Measured Failure Modes & Quirks
- No mechanical post-claim disk verification — self-reports are trusted once a diff exists.
- No cross-provider refutation law (C0); single-family errors go unchecked.
- Cloud agents load repo hooks rather than ~/.cursor/hooks.json; rented workers vanish when billing stops.
Best fit: Isolated multi-file coding inside containerized tasks with external verification added on top.
agnostic/CURSOR_COMPARATIVE_EVALUATION.md