meta-hook-create

Cursor lifecycle hooks intercept agent actions by defining events in a .cursor/hooks.json file, writing shell or JS/TS scripts to process JSON payloads, and reloading the Cursor window to apply the automation changes.

A .cursor/hooks.json file is used to define Cursor lifecycle events like beforeReadFile, beforeShellExecution, and stop, enabling you to run custom hook scripts that perform auditing, logging, or context injection before or after key agent actions.

Yes, you can use shell scripts for Cursor hooks to automate pre-action logic. Hook scripts can be written in shell or JS/TS, receive JSON payloads containing event data, and execute automation or auditing tasks across lifecycle events like beforeMCPExecution.

To capture and log prompts in Cursor, configure a beforeSubmitPrompt hook in your .cursor/hooks.json file that triggers a script to write message payloads to a log file, such as .cursor/logs, then reload the Cursor window to activate the logging automation.

Available Cursor hook lifecycle events include beforeSubmitPrompt, beforeReadFile, beforeShellExecution, beforeMCPExecution, and stop. These events allow you to intercept agent actions and execute custom scripts for context injection or auditing.

Yes, you need to reload the Cursor window after modifying hooks.json configurations. Reloading the Cursor window is required to apply changes and activate newly defined lifecycle hooks and their associated automation scripts.