feat(codex): sync project plugin hooks - #429
Merged
Merged
Conversation
Deploying allagents with
|
| Latest commit: |
8785847
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://71d902a5.allagents.pages.dev |
| Branch Preview URL: | https://feat-codex-project-plugins.allagents.pages.dev |
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.
Summary
Codex workspaces can now reproduce plugin-scoped setup from
workspace.yamlwithout requiring users to run global Codex plugin installs. Project sync now merges plugin-declared Codex hooks into.codex/hooks.json, preserves existing user hooks, and replaces only the allagents-managed hook groups recorded in sync state on later updates.This covers hook-capable plugins such as Beads and Superpowers while keeping Compound Engineering project-scoped through synced skills. Codex still reads true
[plugins]configuration from user-level config only, so this does not try to fake Codex's global plugin registry in project config.Details
.codex-plugin/plugin.jsonhook declarations as a path, path array, inline object, or inline object array, withhooks/hooks.jsonas the fallback..allagents/sync-state.jsonso uninstall/update flows can remove or replace only managed hook groups.plugins%2Fbeadsto resolve asplugins/beads.examples/workspaces/codex-plugin-stack, a copy-and-run Codex workspace with workmux, Beads, Compound Engineering, and agent-tui.Testing
bun testbun run lintbun run typecheckbun run buildbun run test:integrationwas attempted, but the command cannot run in this checkout becausetests/integration/does not exist..codex/hooks.jsonwas created./home/entity/projects/EntityProcess/allagents.worktrees/feat-codex-project-plugins/dist/index.js updateincoding-agent-playgroundwith workmux, deepwiki, Beads, Compound Engineering, agent-tui, and Superpowers. It synced 63 Codex skills, updated DeepWiki MCP, generated project hooks once, and repeated updates kept hook counts stable:PreCompact: 1,PostCompact: 1,SessionStart: 2,UserPromptSubmit: 1.examples/workspaces/codex-plugin-stackto a temp directory and randist/index.js update --dry-run; all four example plugins resolved,Total generated: 1was reported, andworkspace.yamlremained unchanged.Post-Deploy Monitoring & Validation
No additional production monitoring is required because this is local CLI filesystem behavior. Validate release candidates by running
allagents updatein a temporary workspace with existing.codex/hooks.jsonplus Beads/Superpowers-style plugin hooks, then confirm user hooks remain intact and repeated updates do not duplicate managed hooks. Failure signal: user-owned hooks are removed, malformed project hooks are overwritten, or managed hooks accumulate duplicates; rollback by reverting this change.