Description
Cursor CLI (cursor-agent) runs headless on Linux arm64 with CURSOR_API_KEY, but Cursor staff confirm that in -p mode the prompt, response and stop hooks do not fire, so the agento11y plugin would capture tool spans with no prompt, text or tokens, and no preflight guard. It also needs paid Cursor seats and has no published checksum. The maintainer gated it. Facts and workarounds in doc-0002 “Cursor”. Only the maintainer can provision seats and keys.
Acceptance Criteria
- #1 Spike notes on the pinned CLI on Linux arm64 record which hooks fire in -p mode, which payload fields are populated, and whether stream-json usage and chat ids are available
- #2 The maintainer decides between hooks-only capture, a stream-json-to-SDK wrapper, or deferral, plus seat source and identity model, recorded in this task
- #3 A go/no-go is signed off by the maintainer; on go, follow-up tasks are created through the AIO-0005.01 seams, and on no-go this task is closed with the reason
Definition of Done
- #1 just check
Implementation Notes
2026-10-15 maintainer decision: defer Cursor deployment this session. Current official headless output documentation does not establish token usage; staff-confirmed lifecycle-hook gaps remain without a verified fix. Resume when a pinned Linux arm64 release proves prompt, response and usage capture, or maintainer explicitly accepts a bounded incomplete-telemetry spike. Existing stream-json usage assertion in research is unverified.