deepseek-harness/packages/hooks
2026-08-05 16:16:57 +08:00
..
hook-protocol refactor(session): route construction through Session.create 2026-08-05 11:56:14 +08:00
hooks-claude Merge origin/master into xjt/proofreading-active-docs-2-apply 2026-08-05 10:57:53 +08:00
hooks-codex Merge origin/master into xjt/proofreading-active-docs-2-apply 2026-08-05 10:57:53 +08:00
README.i18n.yaml docs: rescan rebased documentation hierarchy 2026-08-05 16:16:57 +08:00
README.md docs: apply hierarchy across the corpus 2026-08-05 16:13:28 +08:00
README.zh.md docs: rescan rebased documentation hierarchy 2026-08-05 16:16:57 +08:00

hooks/ — hook bridges + shared protocol

English | 中文

The hooks subsystem lets users extend the agent at lifecycle points the way Claude Code and Codex do — by pointing a bridge plugin at an existing hooks.json (or settings) so those external shell hooks run faithfully. The canonical extension surface itself is the harness's typed interception seams (the interception-seams Agent Note); a "native hook" is just an ordinary cordis plugin on those seams. These packages are the bridges that translate the external shell-hook protocol onto that same surface, plus the shared wire-protocol library they build on.

Package Role Shape
hook-protocol/ Shared shell-hook protocol library library
hooks-claude/ Claude Code hook bridge plugin
hooks-codex/ Codex hook bridge plugin

The shared library owns common protocol behavior; each bridge owns its dialect-specific event mapping. The child READMEs document those contracts.