Cursor CLI omits beforeSubmitPrompt, afterAgentResponse, and stop hooks, loses token usage, and emits inconsistent generation_id values

[Colin]

Hey @Rahul_Chauhan, thanks for the detailed report!

First, could you confirm you were running the CLI in non-interactive mode (with -p/--print)? Assuming so, here’s where things stand:

@Rahul_Chauhan

1. Is the absence of beforeSubmitPrompt, afterAgentResponse, and stop in Cursor CLI 2026.08.11-e8db854 expected?

2. Is this a known regression or an intentionally unsupported part of CLI hook behavior?

Yes, in non-interactive mode there’s a known gap where beforeSubmitPrompt, afterAgentResponse, and stop aren’t emitted.

@Rahul_Chauhan

3. Is sessionEnd intended to replace stop in CLI mode?

4. If sessionEnd replaces stop, can it expose token usage, loop count, final response text, and the actual model-generation ID?

No,sessionEnd is a separate session-teardown event (it carries the end reason and duration) and isn’t meant as a stand-in for stop. Today no non-interactive event carries token usage, loop count, or the final response text. In interactive mode, afterAgentResponse carries input/output/cache token counts and stop carries status and loop count.

@Rahul_Chauhan

5. Why do CLI afterAgentThought hooks use a separate suffixed generation-ID family which is different from the base generation id with which the current generation starts ?

Those are per-model-generation IDs, while in non-interactive mode the session and tool events currently fall back to using the conversation ID as generation_id instead of the real per-generation ID. For now, conversation_id is the reliable correlation key in non-interactive runs.

@Rahul_Chauhan

6. Is full lifecycle and payload parity between Cursor IDE and Cursor CLI planned?

Closing the hook lifecycle gap between the IDE and CLI (including non-interactive mode) is on the team’s radar, though I can’t share a timeline!