Uh oh!
There was an error while loading. Please reload this page.
Document /hooks as the real hook-status verification method - #54
Merged
Conversation
Tested live: the in-TUI /hooks command shows a real status table (event, installed/active counts) and, per-hook, Source/Command/Mode/Timeout/Trust - a genuine sanctioned view, not something to infer from grepping config files. Confirms a trusted throughline hook reads "Source: Plugin - throughline@throughline", "Trust: Trusted", and shows the exact resolved command path. This also resolves the discovery-mechanism question the previous doc pass left open: the Command field shows Codex resolving each hook straight from the installed plugin's cache path (~/.codex/plugins/cache/throughline/throughline/<version>/hooks/*.sh) with no plugin.json "hooks" key declared - confirmed convention-based discovery, not inferred. Left open: whether toggling an untrusted hook in /hooks can grant trust (only tested against an already-trusted profile so far) - noted as unknown rather than assumed either way. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013cG9PVNGundwPjNB4Yz5AS
/review-pr on PR #54 found: - A line-initial "- " broke the intro paragraph into a stray bullet list under GFM (a bullet item CAN interrupt a paragraph, confirmed by rendering through GitHub's own markdown API) - swallowed "What's confirmed working today:" into the bullet as a side effect. Moved the hyphen to a comma at the end of the prior line instead. Re-verified via gh api /markdown: now a single clean <p>, no stray <ul>. - "confirmed rather than inferred" overclaimed relative to the evidence - the /hooks detail view shows *where* a hook resolved from, not *which* matching rule Codex actually applies. Softened to "observed rather than assumed" and restored the residual-unknown clause the previous revision had dropped, matching this section's existing hedging style elsewhere. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013cG9PVNGundwPjNB4Yz5AS
Uh oh!
There was an error while loading. Please reload this page.
This was referenced Aug 26, 2026
jsirish added a commit
that referenced
this pull request
Aug 26, 2026
Corrects the README, promo site, and CHANGELOG to reflect actual current Codex behavior, confirmed live from a genuinely reverted, out-of-the-box config: Codex CLI shows a native "Hooks need review" dialog on first use (choose "Trust all and continue"); Codex Desktop grants trust silently. Both platforms get full automatic capture, same as Claude Code, gated only by that one-time step. No code changed - this was always true of the shipped plugin. Replaces the "Advanced: enabling automatic capture (unsupported)" section from #53/#54 (obsolete) and corrects v0.13.0's CHANGELOG entry, which asserted "skills only, not automatic capture" about the currently-shipped release - via an [Unreleased] correction and bracketed inline notes, without rewriting released history. /review-pr found and fixed: the CHANGELOG contradiction above, a paragraph narrating investigation history rather than stating current behavior (violates a writing-style rule added this session), an overclaimed "isn't asked again" permanence statement, and a missing jq requirement note on both the README and promo site's Codex sections. Closes#52.
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 freeto 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.
Summary
Follow-up to #53, based on live testing in a real Codex session (Jason). The in-TUI
/hookscommand turns out to be a genuine, sanctioned status view — not something we need to infer from grepping config files.Source: Plugin - throughline@throughline,Trust: Trusted, and the exact resolved command path.Commandfield shows Codex resolving each hook straight from the installed plugin's cache path with noplugin.json"hooks" key declared — confirmed convention-based discovery./hookscan grant trust (only tested against an already-trusted profile).Test plan
/local-ci— 167/167 pass, manifest checks pass/hooksbehavior verified live by Jason in a real Codex session (~/Sites/skanaaluminum, screenshots)🤖 Generated with Claude Code
https://claude.ai/code/session_013cG9PVNGundwPjNB4Yz5AS