feat: align Lumen packaging across Codex, Cursor, and OpenCode#73
Merged
feat: align Lumen packaging across Codex, Cursor, and OpenCode#73
Conversation
Member
Author
Codex only normalizes the `cwd` field relative to the plugin root, not `command`. Without `"cwd": "."`, `./scripts/run.sh` resolves from the user's working directory instead of the plugin directory, breaking MCP server startup for installed plugins. Also fixes stale branch reference in multi-language plan doc. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
aeneasr
changed the title
…Code skills injection
- Use ~/.agents/skills (canonical) instead of deprecated $CODEX_HOME/skills
for Codex native skill discovery in .codex/INSTALL.md and README.md
- Replace relative ./scripts/run.cmd with ${CURSOR_PLUGIN_ROOT}/scripts/run.cmd
in hooks/hooks-cursor.json and mcp.json so Cursor resolves paths from the
plugin root rather than the user's project CWD
- Remove config.skills mutation from .opencode/plugins/lumen.js — skills is
not a field on OpenCode's Config type so the block silently did nothing;
update .opencode/INSTALL.md to drop the false claim that skills are
auto-registered
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
rcdailey
reviewed
Apr 3, 2026
README.md
Outdated
|
|
||
| ```json | ||
| { | ||
| "plugin": ["lumen@git+https://github.com/ory/lumen.git"] |
There was a problem hiding this comment.
I think it would be better to publish a package proper.
Member
Author
There was a problem hiding this comment.
I agree - would you happen to have good docs around that?
There was a problem hiding this comment.
I don't, but I'm sure an LLM could be instructed to build a plan for that work.
Member
Author
There was a problem hiding this comment.
Fair enough ;) Found out you can publish an npm package for opencode.
…ed publishing Switch OpenCode plugin distribution from git clone to a proper npm package. Use OIDC trusted publishing (--provenance) instead of an NPM_TOKEN secret, and prefix launcher invocation with 'sh' to handle npm stripping execute bits.
…nternal/release/ - Move root mcp.json to .cursor/mcp.json to keep Cursor-specific config out of the repo root (avoids Claude Code treating it as project-scoped MCP) - Update .cursor-plugin/plugin.json and INSTALL.md to reference new path - Update AGENTS.md to reflect .cursor/mcp.json and clarify the no-root-mcp rule - Move metadata_test.go from package main to internal/release (package release_test) with ../../-prefixed paths; root package now has no test files
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.
Summary
scripts/run.cmddirectly executable on Unix and using a platform-appropriate launcher in the OpenCode plugin$CODEX_HOME/skillsand add a regression test for direct execution ofscripts/run.cmdWhy
Lumen now ships through multiple agent hosts from the same repository, so the plugin metadata, MCP wiring, hooks, skills, and docs need to stay aligned across those entry points.
The review fixes in this update address two concrete root causes:
scripts/run.cmdpath breaks withENOEXEC$CODEX_HOME/skillsby default, so instructions that point to~/.agents/skillsdo not exposedoctorandreindexUser impact
.cursor-plugin/plugin.json$CODEX_HOME-based instructionsValidation
./scripts/test_run.sh./scripts/test_run_cmd.shnode --check .opencode/plugins/lumen.js