Tianyi Cui
a7a5be1703
Run the dsh-archive-agent-notes audit over every active Agent Note on current master, judging each record by whether its rationale still guides work rather than by size or age. - Archive 453 implemented bilingual triplets (417,882 English words): completed UI chrome, narrow adapters, closed bug fixes, implementation walkthroughs whose package READMEs, docs pages, generators, or successor notes now carry the useful behavior, and 51 records fully superseded by a later active note. Keep 201 implemented notes whose ownership rules, negative guarantees, durable or wire semantics, security rules, reintroduction conditions, or still-tempting rejected alternatives remain useful. - Reject 7 proposals whose premise is gone or whose work shipped in amended form under other records; delete 2 rejected notes that no longer prevent a plausible mistake. - Retarget every remaining inbound link to the archived path, and repair active prose that named an archived record as the owner of a live fact: parenthetical citations drop, ownership sentences redirect to the README, docs page, or active note that states the fact, and history citations say so. Chinese files link the English archived path because the pairing gate treats the frozen tree as outside the bilingual corpus. - Seal 1,359 new frozen artifacts; existing seals are unchanged and outbound links from archived notes are neither inspected nor repaired. - Regenerate docs/config-catalog.md after the hook-bridge comment edits shifted two source line numbers.
description, kind
| description | kind |
|---|---|
| The hooks group map: run existing Claude Code and Codex shell-hook configs during agent runs, for users and maintainers navigating the group. | package-group |
packages/hooks
English | 中文
Summary
The hooks group lets agent runs use the shell hooks you already wrote for Claude Code or Codex: mount the matching bridge, point it at your existing hooks.json, and those hooks fire at the corresponding moments in agent runs — when a session starts, when a prompt is submitted, before and after a tool runs, or when a run is about to stop. Hooks can block a prompt or tool call with a message the model sees, attach extra context to the conversation, or force the run to continue. Choose this group when existing hook configs should keep working without being rewritten as native plugins; each bridge covers the command-hook subset its reference tool documents. hook-protocol is the shared hook engine both bridges use, so the two dialects behave the same way where their protocols agree.
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.
Dev Note
Working context for maintainers — click to expand
None.