af-engineer-hook

To set up Cursor hooks, configure .cursor/hooks.json to define events globally or per-project, and implement hook scripts under .cursor/hooks/. You define events like beforeShellExecution and write policy logic using command-based scripts or prompt-based instructions to control agent actions.

You can intercept events like beforeShellExecution and afterFileEdit to enforce security and auditing in Cursor workflows. These hooks allow you to apply rules, filter sensitive actions, and enforce organizational standards by implementing blocking or modification logic via scripts.

Cursor hooks support both global and per-project configuration. You define rules in .cursor/hooks.json and store hook scripts under .cursor/hooks/, allowing you to tailor events, data formats, and output handling to enforce governance and auditability across your automation workflows.

Implementing Cursor hooks supports both command-based scripts and prompt-based logic, so scripting knowledge is not strictly required. You can choose to write executable scripts for complex blocking logic or use prompt-based instructions to control agent actions within your workflows.

The best way to audit file access during Cursor automation is by implementing hooks for events like afterFileEdit. You configure .cursor/hooks.json and use scripts to intercept, log, and filter sensitive file modifications, enforcing governance and auditability across your workflows.

The hooks.json configuration file is required to define events, apply rules globally or per-project, and specify how hook scripts intercept agent actions. It provides the central configuration needed to enforce security, auditing, and customization policies within Cursor automation workflows.