RetrySight Docs collectors
Cursor
How RetrySight collects Cursor sessions, retries, and token events from local logs.
On this page
Cursor is a Core+ source (and available in-process on Lite). The collector tails Cursor’s local logs — session boundaries, token events, and retry-related edits.
Requirements
- Cursor installed and used on the same machine as Lite or the fleet agent
- On macOS fleet agents: Full Disk Access if log folders are unreadable
- Enterprise: Core or higher; agent pointed at your manager
What you get
- Session and task timelines
- Token events associated with Cursor usage
- Retry taxonomy signals (edits, failed loops) when they appear in the logs
RetrySight does not require a Cursor plugin or an SDK in your repo.
Setup
Lite: install the app and use Cursor as usual. See Lite install.
Cloud: enroll the collector, then confirm the hostname on Collectors.
Enterprise: install the fleet agent, then confirm the collector on the Agents page.