Cursor Telemetry in Beacon | Asymptote
What is Cursor?
Cursor hooks were part of Beacon initial runtime support. Later releases improved prompt reliability, cloud setup, branch attribution, and visible reasoning telemetry.
Collection path: Native hooks
Authoritative date: May 13, 2026 from v0.0.1 in the Beacon CLI changelog.
How Beacon reads Cursor
Cursor invokes beacon-hooks from Cursor hook configuration. Beacon writes normalized endpoint events with workspace and branch context when available.
The result is normalized into Beacon's endpoint event schema so security teams can investigate activity by harness, repository, session, user, model, command, file, tool, MCP server, or approval context where the runtime exposes those fields.
Telemetry coverage
- Prompt submission through beforeSubmitPrompt
- Tool, shell command, MCP-like, approval, and file edit payloads
- Agent reasoning through afterAgentThought where Cursor exposes visible thinking
- Repository and branch context from workspace metadata
What you can do now
- Monitor local Cursor activity from the endpoint.
- Install user-level or project-level hooks depending on rollout needs.
- Pair Cursor events with repository and branch context for investigation.
Get started
- Run beacon endpoint hooks install --harness cursor.
- Restart Cursor so new sessions load the updated hook configuration.
- Use beacon endpoint hooks status --harness cursor to inspect hook state.