release: 0.28.2 — Codex loads ProjectStore's hooks - #26
Merged
Merged
Conversation
The Codex shell ships .codex-plugin/plugin.json alone. Codex picks a root Agent Plugins plugin.json first, and since openai/codex#37027 (merged 2026-08-05; 0.153.4 and 0.160.0 alike) it loads no hooks from that format. So 0.28.1, like every checkout build since rc.3, reached Codex with no hook loaded. With no hooks key, a legacy manifest falls back to hooks/hooks.json, which is where ours is. - packaging/shells.mjs: renders one manifest; the files list and the --dev version site follow - scripts/version-guard.mjs: the Codex shell has one version site, and a root plugin.json in it is refused, with the reason - tests: the shell and its dev build carry no root manifest, and the guard's refusal is pinned; the registration fixtures take the shipped shape - harnesses/codex.json and docs/harnesses.md say how the hooks load and why there is no root manifest; README.md and the shell's README name the one manifest - the version at every guard site Codex's app-server hooks/list reports 0 ProjectStore hooks for an installed 0.28.1. It reports 6 for 0.28.2, both freshly installed and upgraded from 0.28.1. Live on the maintainer's Codex 0.160.0, with the root manifest renamed away in the installed cache, /hooks listed all six. Our SessionStart and PreCompact ran, a recorder saw PreToolUse, PostToolUse and Stop fire, and $projectstore-status answered from the vault. Maintainer: [email protected]
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.
The 0.28.2 release: Codex now loads ProjectStore's hooks.
The maintainer's first live Codex session on 0.28.1 showed no ProjectStore hook in
/hooks. The cause, read from Codex's source:plugin.jsonfirst.codex-cli0.153.4 and 0.160.0 alike), it loads no hooks from that format.0.28.1 shipped exactly that root manifest. 0.28.2 ships
.codex-plugin/plugin.jsonalone, with nohookskey, so Codex falls back tohooks/hooks.json. The record is the Finding of 2026-10-04 in The Codex shell's plugin root: .codex-plugin, the rendered surfaces, and the first Codex install (PS-HARNESS). It passed two critic passes, and the code passed a reviewer pass.Merging this is the git marketplace's release for Claude Code users, with no code change for them. After the merge,
v0.28.1's successorv0.28.2is tagged onmain, and CI publishes all three packages underlatest.Checks
npm run release:check: 541 of 541, both inside a Claude Code session and with its markers stripped.node scripts/version-guard.mjs --tag v0.28.2reports ok.hooks/liston isolated installs (codex-cli 0.160.0), counts our hook commands:planwrites nothing;installleaves the plugin installed and enabled;Codex stays experimental (
verified: null).Maintainer: [email protected]