Lodestar 2.1.4
Package: lodestar-agent-context@2.1.4.
This release fixes an installation defect in the optional Codex plugin. Versions
through 2.1.3 could be installed and enabled by Codex, but their cached MCP server
could not find the shared runtime. The CLI and MCP adapter worked inside the full
npm package; the plugin's advertised directory did not contain that full package.
What changed
- The package root is now the plugin root. Root plugin and MCP manifests ensure
that Codex caches the adapter, executable, shared declarations, and runtime
together. The implementation continues to use one core and one mutation contract. - A local marketplace entry points to that complete root. Installation instructions
explain the optional plugin, native skill setup, and upgrading a cached plugin. - A plugin hosted inside WSL uses the installed WSL launcher to reach the
Windows-owned database. Declared path arguments are translated before stdin
transport, preserving long reads and the complete guarded mutation body. - Package tests and release smoke checks launch the declared plugin from an
isolated cache, with no source-runtime overrides. They exercise actual requests
and inspect persisted results, replay behavior, and refusal of stale writes.
The earlier tests used real processes and databases, but ran the adapter inside
the full npm layout. They did not reproduce Codex copying only the declared plugin
root. The new check covers that missing installation boundary.
Upgrade
Upgrade the CLI with:
npm install --global lodestar-agent-context@2.1.4
lodestar setup --target all
lodestar setup --target all --apply
For the optional Codex plugin, use the complete package root. Custom marketplace
entries pointing at codex-plugin/ must be updated before reinstalling. A global
npm upgrade does not update a plugin already copied into Codex's cache. Follow
plugin installation,
keep one active Lodestar plugin, and begin a fresh task after updating it.
The CLI and native skill remain useful without the optional plugin. Automatic
invocation eligibility remains enabled as corrected in 2.1.3. Host settings and
native instructions retain their authority.
Compatibility
Requires Node.js 24.15.0 or newer. Contract 5 and schema 5 are unchanged; existing
2.x stores require no new migration. Windows/WSL access still uses the Windows-owned
one-shot boundary. Release checks run on Windows, Linux, and macOS. Installation
and protocol tests establish executable behavior; they do not guarantee that every
model task selects a skill or tool.