Summary
The current LazyCodex marketplace payload for omo@sisyphuslabs still appears to omit two bundled hook CLI files:
plugins/omo/components/start-work-continuation/dist/cli.js
plugins/omo/components/ulw-loop/dist/cli.js
This looks related to the previously closed issue:
That issue was marked fixed via:
However, after updating to the current LazyCodex marketplace revision, the generated marketplace payload still lacks those two files.
Observed behavior
Codex/LazyCodex repeatedly detects dangling managed bins and runs a marketplace local repair for commands including:
omo-start-work-continuation
omo-ulw-loop
ulw
ulw-loop
The repair reports the plugin as current at 4.15.1, but the marketplace payload still does not contain the missing CLI files. As a result, manual repairs to the active plugin cache can become necessary again after update or repair cycles.
Evidence
Environment summary:
codex-cli: 0.142.5
omo plugin version: 4.15.1
LazyCodex marketplace source: https://github.com/code-yeongyu/lazycodex.git
LazyCodex marketplace revision observed: dac44057c70eedbdbca5afaeb1d16502e518fbdc
platform: macOS arm64
The marketplace snapshot still shows:
plugins/omo/components/start-work-continuation/dist/cli.js MISSING
plugins/omo/components/ulw-loop/dist/cli.js MISSING
plugins/omo/components/rules/dist/cli.js OK
plugins/omo/components/ultrawork/dist/cli.js OK
The latest synced LazyCodex repo source showed the same result:
plugins/omo/components/start-work-continuation/dist/cli.js MISSING
plugins/omo/components/ulw-loop/dist/cli.js MISSING
plugins/omo/components/rules/dist/cli.js OK
plugins/omo/components/ultrawork/dist/cli.js OK
Why #5768 may not fully cover this
oh-my-openagent#5768 appears to fix ULW CLI aliases and bin-link repair behavior. It adds/tests aliases such as:
omo-ulw-loop
ulw
ulw-loop
But the current LazyCodex marketplace payload still needs to actually include the generated component CLI files that those hooks/bins point to.
So this may be an incomplete propagation/regeneration issue in the LazyCodex generated marketplace payload rather than only an upstream alias/link issue.
Expected behavior
A fresh LazyCodex marketplace sync/update should install an omo@4.15.1 payload where all declared hook/bin targets exist, including:
components/start-work-continuation/dist/cli.js
components/ulw-loop/dist/cli.js
After update/repair, UserPromptSubmit and Stop hooks should not fail with missing module errors and should not require manually rebuilding or copying files into the plugin cache.
Actual behavior
The marketplace payload can be current at 4.15.1, but still lack the two generated hook CLI files. The user then has to manually rebuild or restore them after updates.
Suggested fix
Please regenerate/sync the LazyCodex marketplace payload from an upstream artifact that includes the built component CLIs, or add a packaging check that fails marketplace generation if any declared hook/bin target points to a missing file.
A useful validation would be to assert these files exist in the generated LazyCodex repo before publishing/syncing:
plugins/omo/components/start-work-continuation/dist/cli.js
plugins/omo/components/ulw-loop/dist/cli.js
plugins/omo/components/rules/dist/cli.js
plugins/omo/components/ultrawork/dist/cli.js
Summary
The current LazyCodex marketplace payload for
omo@sisyphuslabsstill appears to omit two bundled hook CLI files:plugins/omo/components/start-work-continuation/dist/cli.jsplugins/omo/components/ulw-loop/dist/cli.jsThis looks related to the previously closed issue:
That issue was marked fixed via:
However, after updating to the current LazyCodex marketplace revision, the generated marketplace payload still lacks those two files.
Observed behavior
Codex/LazyCodex repeatedly detects dangling managed bins and runs a marketplace local repair for commands including:
The repair reports the plugin as current at
4.15.1, but the marketplace payload still does not contain the missing CLI files. As a result, manual repairs to the active plugin cache can become necessary again after update or repair cycles.Evidence
Environment summary:
The marketplace snapshot still shows:
The latest synced LazyCodex repo source showed the same result:
Why #5768 may not fully cover this
oh-my-openagent#5768appears to fix ULW CLI aliases and bin-link repair behavior. It adds/tests aliases such as:omo-ulw-loopulwulw-loopBut the current LazyCodex marketplace payload still needs to actually include the generated component CLI files that those hooks/bins point to.
So this may be an incomplete propagation/regeneration issue in the LazyCodex generated marketplace payload rather than only an upstream alias/link issue.
Expected behavior
A fresh LazyCodex marketplace sync/update should install an
omo@4.15.1payload where all declared hook/bin targets exist, including:After update/repair,
UserPromptSubmitandStophooks should not fail with missing module errors and should not require manually rebuilding or copying files into the plugin cache.Actual behavior
The marketplace payload can be current at
4.15.1, but still lack the two generated hook CLI files. The user then has to manually rebuild or restore them after updates.Suggested fix
Please regenerate/sync the LazyCodex marketplace payload from an upstream artifact that includes the built component CLIs, or add a packaging check that fails marketplace generation if any declared hook/bin target points to a missing file.
A useful validation would be to assert these files exist in the generated LazyCodex repo before publishing/syncing: