Cursor

Cursor telemetry is captured via editor hook scripts that the CLI installs.

Automatic Setup

flowstate-telemetry install --tool cursor

This installs a hook script into ~/.cursor/hooks/ and configures ~/.cursor/hooks.json to capture session events.

Manual Setup

The CLI creates hook scripts and a JSON configuration file. Manual setup is not recommended for Cursor — use the CLI instead.

If you need to configure manually, the CLI writes to:

• ~/.cursor/hooks/flowstate.sh — hook script
• ~/.cursor/hooks.json — hook event configuration

The hooks capture events on: stop, beforeMCPExecution, beforeShellExecution, afterFileEdit.

What Gets Captured

Event	Data Collected
Prompts	Prompt text, session ID
Chat requests	Model, input/output tokens, cost
Composer sessions	Duration, file modifications
Tool calls	Tool name, success/failure

TIP

Prompt capture is always on for Cursor — the hook scripts capture prompt content by default. There is no opt-in flag.

Limitations

• Tab completions (autocomplete) are not tracked — only chat and composer sessions