README.md 2.0 KB
description: "The hooks group map: run existing Claude Code and Codex shell-hook configs during agent runs, for users and maintainers navigating the group."
kind: "package-group"
packages/hooks
English | 中文
Summary
The hooks group lets agent runs reuse shell hooks written for Claude Code or Codex. Point the matching integration at an existing hooks.json to run supported command hooks when sessions start, prompts arrive, tools run, or runs stop. These hooks can block prompts or tool calls with model-visible messages, add conversation context, or require the run to continue. Choose this group to preserve existing hook configurations; each integration supports only the command-hook subset documented by its source tool.
Table of Contents
Packages
| Package | Role | Shape |
|---|---|---|
hook-protocol |
Shared hook engine both bridges use; never configured directly | library |
hooks-claude-code |
Run your existing Claude Code hooks.json hooks during agent runs |
plugin |
hooks-codex |
Run your existing Codex hooks.json hooks during agent runs |
plugin |
Related documentation
- Interception extension-points Agent Note — the typed-Decision surface the bridges program against.
- Hook bridges Agent Note — the bridge design and its decision mapping.
- Hook protocol library Agent Note — what the shared library owns and why.