Skip to main content

​
Runtime Overview

Asymptote supports Cursor through native hook payloads sent to beacon-hooks. For provider-managed Cursor cloud sessions, see Cursor Cloud Agents.

​
Prerequisites

Before enabling Cursor hooks, make sure:
  • Cursor is installed for the user or the ~/.cursor directory exists.
  • beacon endpoint install has run so shared endpoint config and runtime log paths exist.
  • Asymptote hooks are installed with beacon endpoint hooks install --harness cursor.
  • For project-level collection, install hooks from the target project with --level project.
  • Cursor is restarted after hook install or removal so new sessions load the updated hook configuration.

​
Collection path

Cursor invokes Asymptote’s hook adapter from Cursor hook configuration. The adapter writes normalized endpoint events to the configured runtime JSONL log.

​
Discovery and status

Asymptote detects Cursor through the Cursor binary or ~/.cursor, then checks Asymptote hook configuration. Use beacon endpoint hooks status --harness cursor to inspect Cursor hook status.

​
Install or configuration support

beacon endpoint install prepares shared endpoint config and runtime log paths. Install Cursor hooks separately:
Install runtime hooks
For project-level hooks, run:
Install project-level hooks

​
Telemetry coverage

​
Deployment notes

Restart Cursor after installing or removing hooks so the updated hook configuration is picked up by new sessions. Hook events include metadata such as file path, operation, language, diff hash, and diff byte count. Raw diffs and reasoning text are subject to Asymptote’s redaction, sanitization, truncation, and event-size limits before writing.

​
Token usage

Cursor’s hook payloads do not include token counts today, so hook telemetry alone cannot power the token views for Cursor sessions. Two mechanisms close the gap:
  • Local state-store sync. beacon token-usage sync-cursor reads a private snapshot of Cursor’s local state store (state.vscdb) and appends the runtime-recorded per-generation token counts to the runtime log as token.usage events attributed to the cursor harness, keyed by the same conversation id the hooks record. The store is undocumented and best-effort: generations without recorded counts are skipped, and Beacon never estimates token counts or derives cost locally.
  • Hook passthrough. If a Cursor release starts including usage fields in hook payloads, the hook adapter normalizes them into gen_ai.usage automatically, and rollups prefer hook-reported usage over synced usage for the same session, so the two sources never double count.
After syncing, Cursor usage appears in beacon token-usage and the dashboard token view alongside other harnesses.

Supported agent harnesses

Return to the runtime support overview.

Hooks

Install, inspect, and uninstall runtime hook integrations.

Cursor Cloud Agents

Capture Cursor cloud agent telemetry with sandbox-local hooks and GCS upload.