Repository navigation
Conversation
zlareb1
force-pushed
the
fix/codex-hook-labels
branch
from
November 18, 2026 07:53
b84732a to
d9db850
Compare
Show each hook’s purpose in the hooks browser through statusMessage metadata. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The hook validates memory keys written during the session. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Keep the handler-field allowlist aligned with the supported statusMessage field. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Give each retry a new session so cached empty lookups do not suppress its request. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Publish the hook labels with a plugin version distinct from other pending changes. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
zlareb1
force-pushed
the
fix/codex-hook-labels
branch
from
November 18, 2026 09:10
98115b1 to
32b85b8
Compare
This branch has not been deployed
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.
Changelog category (leave one):
Changelog entry:
The Codex
/hooksbrowser shows each Loom hook's purpose instead of "Unnamed hook".Why
The hooks browser uses
statusMessageas the display title. Each of the 22 hook definitions supplies a concise Loom-prefixed label so users can identify its purpose.Scope and risk
The change adds display metadata to the Codex hooks file and bumps both plugin manifests to 1.2.31. Commands, Windows commands, event matchers, ordering and hook execution stay the same. The existing parser-field contract accepts the supported
statusMessagefield; it continues to reject unknown fields. Fail-open test retries use fresh sessions so a cached empty lookup cannot suppress the next HTTP check. Their request assertions, deadlines and retry limit stay the same.Compatibility, rollout and rollback
statusMessageis supported hook metadata.Tests
Local checks:
git diff --checkpassed.node --checkpassed for both changed test files.statusMessagereproduces the base hook wiring byte for byte. Each manifest changes only its paired version, and the merged plugin guidance is preserved.Full unit, coverage, offline benchmark, integration, browser and plugin platform suites must pass in PR CI. The upstream parser test accepts
statusMessage. No new test duplicates the static label mapping.AI assistance in the code
AI-generated with Codex. Reviewed all labels and verified that removing
statusMessageleaves the hook wiring identical and that the manifests change only their paired version.Checklist
make format-check,make lint,make typecheckandmake test-unitpass; the integration suite passes if server behaviour changed.agent_plugin_sync --check.