create-hook

Cursor hooks are configurations defined in a .cursor/hooks.json file that customize agent-event behavior through command or prompt hooks. They enable proactive control, auditing, and automation by running scripts before or after specific agent events.

Project-level hooks are set up by creating a .cursor/hooks.json file in the project root, while user-level hooks use the same file in the home directory. Both allow you to define triggering events, select hook types, and add scripts to enforce deterministic workflows.

Command hooks in Cursor execute scripts to perform automation tasks, whereas prompt hooks are used to enforce policies or modify the agent's context. The setup process involves selecting the appropriate hook type based on whether you need script execution or context modification.

Yes, you can use Cursor prompt hooks specifically to enforce policies or modify the agent's context during events. This allows you to proactively control agent behavior and ensure deterministic workflows without relying solely on manual intervention.

Before deploying Cursor hooks, you need to determine the hook scope (project or user level), identify the triggering agent events, and select the hook type. This structured workflow ensures the resulting hooks.json and any optional scripts are safely and correctly configured.