Public openai-curated-remote plugin installs bundled hooks but does not expose them for review or trust

What version of the Codex App are you using (From “About Codex” dialog)?

26.825.51511

What subscription do you have?

Plus

What platform is your computer?

Windows(x64) and Windows Sandbox (x64) clean environment account (WDAGUtilityAccount)

What issue are you seeing?

AI Software Architect 0.2.2 and 0.2.3 installs successfully from the public universal directory, but Codex Desktop does not display its five bundled lifecycle hooks in the plugin Hooks section and provides no way to review or trust them.

The public package is fully materialized at:

C:\Users\WDAGUtilityAccount\.codex\plugins\cache\openai-curated-remote\ai-software-architect\0.2.3

Inspection confirms:

• Manifest version: 0.2.3
• Manifest hooks field: ./hooks/hooks.json
• hooks/hooks.json exists: True
• Bundled Windows runtime exists: True

The same plugin structure exposes all five hooks correctly when installed from a local marketplace. The problem occurs only for the public openai-curated-remote installation.

The user configuration contains neither hooks = false nor allow_managed_hooks_only = true.

What steps can reproduce the bug?

1. Start with a clean Windows Sandbox environment.
2. Install AI Software Architect 0.2.3 from the public plugin directory.
3. Open the installed plugin details and inspect its Hooks section.
4. Observe that no bundled hooks are listed and there is no review/trust action.
5. Inspect the downloaded plugin cache and confirm that both .codex-plugin/plugin.json and hooks/hooks.json are present.
6. Install the same plugin structure through a local marketplace and observe that all five hooks are shown correctly.

What is the expected behavior?

Codex should discover the five bundled lifecycle hooks from ./hooks/hooks.json and list them for review and trust. Once trusted, the hooks should be available to run in new tasks, matching the documented behavior for enabled plugin-bundled hooks.

Additional information

This appears specific to the remote catalog or desktop discovery path for openai-curated-remote, because the package reaches the client intact and local marketplace discovery works.

Official documentation:

• https://learn.chatgpt.com/docs/hooks
• https://developers.openai.com/plugins/build/plugins

A separate known issue tracks the stale plugin-creator validator rejecting the supported hooks manifest field:

• https://github.com/openai/codex/issues/27141

Start by comparing the public openai-curated-remote installation path with the local marketplace path, using the cached .codex-plugin/plugin.json and hooks/hooks.json files described in the report. Trace the desktop plugin discovery flow for the remote catalog and verify where the five hooks stop being exposed. Done means the public installation lists all five hooks for review and trust, matching local marketplace behavior.