feat: support Codex hooks engine (v0.114.0+) SessionStart/Stop events#61
Merged
feat: support Codex hooks engine (v0.114.0+) SessionStart/Stop events#61
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why hooks support now
Codex rust-v0.114.0 introduced an experimental hooks engine with SessionStart and Stop hook events. This enables ceeker to receive session lifecycle events via stdin JSON (same mechanism as Claude Code hooks), providing a cleaner integration path compared to the notify argv-based approach.
Hooks vs notify fallback strategy
Async config choice
The README config examples use async: true so ceeker hooks run in the background and do not block the Codex agent loop. A note warns that async may not be supported in all versions and provides a sync fallback.
Changes
Tests
Residual risk / review points