Codex, Cursor, GitHub Copilot and Gemini CLI now ship their own hook systems with similar event names but different blocking semantics. Map each vendor's events to one internal policy so a rule like "never read .env files" is enforced the same way everywhere. Note where a vendor says hooks are a guardrail rather than a complete boundary.
Read in this order
- OfficialHooks (Cursor docs)Start here: Cursor's events and how a hook blocks or allows an action.
- OfficialHooks (OpenAI Codex docs)Codex's hook events, to compare against Cursor's semantics.
- OfficialCustomize agent workflows with hooks (GitHub Copilot docs)How Copilot's cloud agent uses hooks, and what they cannot stop.