Repository navigation
chore: publish Codex plugin v0.7.2 - #15
Merged
Merged
Conversation
Codex installs the marketplace from this repository, not from the npm @everme/codex package, so the two releases published to npm since v0.7.0 never reached a Codex host. The runtime bundles here are what a Codex user actually loads. The functional carry is in hook.mjs: every hook write now claims the hook channel and declares the turns it carries. An unclaimed write is anonymous to the session gate, so it gets no ledger row, the watermark does not advance past its turns, and the importer's later scan of the same session stores all of them a second time instead of trimming them. It also splits the channel claim from the loss reporter, which used to share one flag and so divided one population's losses by another's writes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
2 participants
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.
What this is
Codex does not install the plugin from npm.
evercli plugin install codexpulls the marketplace from this repository, so the two plugin releases
published to npm since
v0.7.0(0.7.1 and 0.7.2) never reached a singleCodex host. This syncs the two allow-listed paths and nothing else.
What changed
plugins/everme/.codex-plugin/plugin.json0.7.0->0.7.2plugins/everme/bin/hook.mjsplugins/everme/bin/memory-mcp.mjsPKG_VERSIONline.agents/plugins/marketplace.jsonwas already identical, so it is not inthe diff.
Why it matters
Every hook write now claims the hook channel and declares the turns it
carries. An unclaimed write is anonymous to the session gate: it gets no
ledger row, the watermark never advances past its turns, and the importer's
later scan of the same session stores every one of them a second time
instead of trimming them.
The same change splits the channel claim from the loss reporter. Those used
to share one flag, so a host that never claimed the channel still reported
losses -- one population's losses divided by another population's writes.
The bundle on
maintoday has two channel claims and nocompletedUserTurns;this one has three and uses it.
Verification
Produced by the documented sync procedure.
rsync --deleteremoved nothing,so this repository carries no local patch under
plugins/everme/that thesync would have dropped.
plugin.jsonversion equals the source tree:0.7.2hook.mjsandmemory-mcp.mjsare byte-identical to the published sourcetree (
cmp, both clean)git diff --checkcleanof the internal monorepo came along.
0.7.2, verifiedfile-for-file against the published tarballs.
After merge
Install into a clean Codex environment, confirm the installed version is
0.7.2, and check the SHA-256 of both assets against this commit.