Summary

PR #11029 ("feat: add hooks system for CLI event interception") merged on 2026-03-04 introduced a significant new feature: a Claude Code-compatible hooks system for the Continue CLI. This feature currently has no user-facing documentation in the docs/ folder.

Feature Details

The hooks system allows external handlers (shell commands, HTTP endpoints) to intercept and respond to 16 CLI event types. Key capabilities include:

• Regex-based event matching for targeting specific events
• Command hooks: Execute shell commands with JSON piped to stdin
• HTTP hooks: Send POST requests to endpoints
• Exit code semantics: 0 = proceed, 2 = block (stderr becomes feedback)
• Config sources (in precedence order):
  • ~/.claude/settings.json, ~/.continue/settings.json (user-global)
  • .claude/settings.json, .continue/settings.json (project)
  • .claude/settings.local.json, .continue/settings.local.json (project-local)
• Async/sync execution modes
• Multi-source config merging

Documentation Needed

A new documentation page should be created (suggested location: docs/cli/hooks.mdx) covering:

1. Overview - What hooks are and when to use them
2. Configuration - How to set up hooks in settings files
3. Event Types - List of the 16 available event types
4. Hook Types - Command hooks vs HTTP hooks
5. Exit Code Semantics - How to control flow (proceed/block)
6. Examples - Practical use cases (pre-commit validation, logging, custom integrations)

Reference Implementation

• Source code: extensions/cli/src/hooks/
• Internal docs: extensions/cli/AGENTS.md (Hooks System section)
• Original PR: feat: add hooks system for CLI event interception #11029

Labels

This is a tier 1 (XXL) feature that should have user-facing documentation.

Generated with Continue

Co-Authored-By: Continue noreply@continue.dev