Tracing for Cursor records each prompt as a trace, with the tools and file operations it triggered nested beneath it. It covers both the Cursor IDE and the Cursor CLI, though the two report different amounts of detail.

​
Install

On macOS or Linux:
On Windows:
The installer prompts for your license key and project name, stores them in ~/.atatus/harness/config.json, and registers the hooks in ~/.cursor/hooks.json. Add --with-skills to also link the manage-cursor-tracing skill into the current directory.
The hooks are registered per user in ~/.cursor/hooks.json, so they apply to every workspace you open, not just the one you ran the installer from.

​
What gets captured

​
IDE compared with CLI

Cursor emits a different set of events depending on how you use it, so the CLI produces less detail than the IDE:
The remaining events are IDE-only, so CLI traces show shell commands and file edits but not file reads or tab completions. This is a limit of what Cursor reports, not of the tracing.

​
Where things live

Fifteen hook events are registered: sessionStart, sessionEnd, beforeSubmitPrompt, afterAgentResponse, afterAgentThought, beforeShellExecution, afterShellExecution, beforeMCPExecution, afterMCPExecution, beforeReadFile, afterFileEdit, beforeTabFileRead, afterTabFileEdit, postToolUse, and stop.

​
Uninstall

This removes the hook entries from ~/.cursor/hooks.json. See Uninstall for the full-wipe option.