feat(cli): add recall command and local Codex hook - #78
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.
Add
flicknote recall QUERYfor readable candidate lists andflicknote recall --hookfor Codex event JSON on stdin. Both reuse the existing daemon query; hook mode shares the bounded MCP output contract, and MCPnote_recallremains supported.The installer writes a static, shell-quoted absolute CLI command with a one-second timeout. Reinstalling updates only the new command-hook form. Old MCP hooks remain untouched and must be removed manually to avoid duplicate recall. README, CLI help, and agent guidance describe the new behavior.
Validation: workspace tests/build, workspace/all-target/all-feature check and Clippy, format, cargo deny, pre-push checks, and focused CLI/installer tests passed. Standards and spec reviews passed. An isolated actual Codex command-hook smoke with a fake command and local Responses endpoint confirmed exact stdin delivery and developer-context injection; product CLI behavior is covered separately by daemon integration tests. No live configuration or deployment was changed.