Connect Cursor to Terma - Terma

Coming soon. Cursor appears as Coming Soon in the terma setup agent picker, and you can’t connect it yet. This page describes what Terma will capture once it is available. Today, terma setup connects Claude Code and Codex.

Cursor’s IDE and its agent / cursor-agent CLI share the same hooks. Terma will use those hooks for commit attribution and for an ordered record of each conversation. Cursor has no telemetry export Terma can use, so support will be partial: commits are attributed, but cost, plan, and quota data are unavailable.

Hooks

Hook	What Terma will record
`sessionStart`, `sessionEnd`	Conversation boundaries
`beforeSubmitPrompt`, `afterAgentResponse`, `stop`	Ordered turn observations, with the selected model and optional token snapshots
`preCompact`	Context occupancy before compaction
`afterFileEdit`	Files edited, for commit attribution
`postToolUse`, `postToolUseFailure`	Every finished tool call
`subagentStop`	Subagents the conversation spawned, with their files

subagentStart is not used: it is a permission gate, and a hook that prints nothing would deny the spawn on a machine without terma.

What’s captured

Signal	Available
Commit attribution	Yes
Conversations, turns, and ordering	Yes
Selected model and Cursor version	Yes
Tool calls	Yes
Subagents	Yes
Token counts	Optional snapshots, when Cursor supplies them
Cost, plan, quota, and billed amount	No
Prompt and response text	No — hooks never read it

Token values from Cursor’s hooks are snapshots, not a complete ledger of model requests, and are not enough to compute exact cost. When Cursor runs in Auto mode, the selected model is not necessarily the model that was billed.

Privacy

Terma’s Cursor hooks will not read or forward prompt or response text, messages, edit contents, error text, transcript paths, or credentials. Cursor may supply the signed-in account email; when it does, Terma includes it as personal metadata. As with every agent, your team’s collection policy decides which repositories are collected.