Date: 2026-09-10

Automate with hooks

Hooks are lifecycle integrations represented by the hook configuration and runtime. They can observe or participate at supported lifecycle points; they do not replace approval policy.

Use the current implementation

Configure only hook fields accepted by the installed package. Test hooks with a non-destructive prompt and inspect their exit status and output before enabling them for shared projects.

Boundaries and safety

A hook may receive sensitive context depending on its lifecycle point. Keep executables trusted, validate inputs, and avoid logging prompts, tokens, or file contents.