core-agent-ide/codex-rs/app-server-protocol
Andrei Eternal 244b2d53f4
start of hooks engine (#13276)
(Experimental)

This PR adds a first MVP for hooks, with SessionStart and Stop

The core design is:

- hooks live in a dedicated engine under codex-rs/hooks
- each hook type has its own event-specific file
- hook execution is synchronous and blocks normal turn progression while
running
- matching hooks run in parallel, then their results are aggregated into
a normalized HookRunSummary

On the AppServer side, hooks are exposed as operational metadata rather
than transcript-native items:

- new live notifications: hook/started, hook/completed
- persisted/replayed hook results live on Turn.hookRuns
- we intentionally did not add hook-specific ThreadItem variants

Hooks messages are not persisted, they remain ephemeral. The context
changes they add are (they get appended to the user's prompt)
2026-03-10 04:11:31 +00:00
..
schema start of hooks engine (#13276) 2026-03-10 04:11:31 +00:00
src start of hooks engine (#13276) 2026-03-10 04:11:31 +00:00
tests Stabilize protocol schema fixture generation (#13886) 2026-03-09 13:51:50 -07:00
BUILD.bazel feat: vendor app-server protocol schema fixtures (#10371) 2026-02-01 23:38:43 -08:00
Cargo.toml feat(app-server): support mcp elicitations in v2 api (#13425) 2026-03-05 07:20:20 -08:00