feat(cli): add Codex entity recall hook and installer - #75
Merged
Merged
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
1 participant
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.
Codex can now recall existing FlickNote notes automatically on each
UserPromptSubmit. The read-onlynote_recallMCP tool matches extracted entity names in the current prompt, returns up to five active-note candidates ordered by modification time, and supplies bounded context with numeric IDs for further reading. It uses the daemon boundary, has a one-second timeout, and does not read note bodies or write notes.Adds
flicknote hook install codexwith an interactive project/global choice and--local/--globalflags. Installation preserves existing configuration, follows user/project MCP field inheritance and tool availability, avoids duplicate hooks, and leaves service lifecycle and hook trust to the operator. README and agent guidance are included. The daemon IPC protocol advances to v5.Validation: workspace all-target/all-feature tests, check and clippy; build; formatting; cargo deny; focused installer/backend/MCP contract regressions. An isolated Codex 0.153.4 smoke test confirmed the hook context reaches the first model request through MCP. An actual temporary PowerSync fixture with 1,024 notes and 1,024 extractions returned five candidates in one ~10.8 ms observation using existing indexes; no new indexes or production-performance claim. No live configuration, notes, credentials or services were used in tests, and no deployment was performed.