Repository navigation
Description
Summary
On OpenClaw 2026.6.5, openclaw plugins install can fail deterministically with npm EOVERRIDE for managed npm-root projects whose manifests were created by earlier OpenClaw versions. Two behaviours compound:
-
2026.6.5 imports pnpm workspace overrides into managed npm roots.
readOpenClawManagedNpmRootOverrides()now callsreadHostWorkspaceOverrides(packageRoot), which reads thepnpm-workspace.yamlthat ships inside the published npm package and exports itsoverrides:block (~26 entries, includinghono: 4.12.18,@hono/node-server: 1.19.14,@aws-sdk/*) into~/.openclaw/npm/projects/<name>-<hash>/package.jsonas npmoverrides— including pins for packages that are not part of the host's runtime dependency graph. -
Managed peer-dependency pins never advance.
syncManagedNpmRootPeerDependencies()keeps an existing pin vianextDependencies[packageName] = dependencies[packageName] ?? dependencySpec. A project manifest that earlier OpenClaw versions pinned tohono: "4.12.23"(recorded inopenclaw.managedPeerDependencies) keeps that exact spec forever.
The combination writes a manifest npm itself rejects: dependencies.hono = "4.12.23" plus overrides.hono = "4.12.18". npm's assertRootOverrides (@npmcli/arborist/lib/node.js) throws EOVERRIDE because an override may not change the effective spec of a root direct dependency:
npm error code EOVERRIDE
npm error Override for hono@4.12.23 conflicts with direct dependency
The install then rolls back the manifest, so the conflicting state is invisible after the fact — which makes this confusing to debug. (I captured the mid-install manifest by snapshotting package.json on a 50 ms loop while the install ran.)
Environment
- OpenClaw 2026.6.5 (
5181e4f), installed via npm into~/.npm-global - node v24.16.0, npm 11.13.0, Linux (systemd)
- Plugin being updated:
@drakon-systems/shieldcortex-realtime(extension-format pack,openclaw.extensions; it declares nohonodependency and nooverridesitself)
Reproduction
- A managed project at
~/.openclaw/npm/projects/<plugin>-<hash>/whosepackage.jsoncontains a stale managed peer pin, e.g."hono": "4.12.23"independencieswith"hono"listed inopenclaw.managedPeerDependencies(created by a pre-2026.6 OpenClaw; observed on several machines). - Upgrade host to 2026.6.5.
openclaw plugins install --force <plugin>@latest→ EOVERRIDE, rollback, plugin left on the previous version.
Mid-install manifest captured right before npm ran (trimmed):
{
"dependencies": {
"@drakon-systems/shieldcortex-realtime": "4.31.2",
"hono": "4.12.23",
"...": "..."
},
"overrides": {
"hono": "4.12.18",
"@hono/node-server": "1.19.14",
"@anthropic-ai/sdk": "0.100.1",
"...": "..."
},
"openclaw": {
"managedOverrides": ["hono", "..."],
"managedPeerDependencies": ["hono", "..."]
}
}Impact
- Every subsequent plugin install/update in an affected project fails until the manifest is repaired by hand.
- After the npm failure the installer prints
Also not a valid hook pack: Error: package.json missing openclaw.hooks, which is misleading for extension-format packs — the actionable error is the npm one. - Related: because existing pins are never advanced, plugins can keep running against stale peer-dependency versions indefinitely even when installs succeed (we found a plugin running against a peer lib several versions behind the plugin itself).
Workaround
Edit the project package.json: delete the stale entry (e.g. hono) from both dependencies and openclaw.managedPeerDependencies, then re-run the install. The peer plan re-pins it consistently with the override and the install succeeds.
Suggested fixes
- (a) Before running npm, reconcile managed overrides against root dependencies: if an override key is also a root dependency in the managed root, align the dependency spec to the override (or drop that override key). This makes EOVERRIDE structurally impossible.
- (b) Advance managed peer pins from the fresh peer plan rather than unconditionally preserving the existing spec (
dependencies[name] ?? dependencySpec). - (c) Optionally filter workspace overrides to packages actually reachable in the host runtime graph before exporting them to plugin roots.
Happy to provide more detail or test a fix.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Activity
clawsweeper commentedon Jun 9, 2026
Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed June 20, 2026, 12:43 PM ET / 16:43 UTC.
Summary
Keep open: current main and latest release still preserve stale managed peer pins while importing fresh managed overrides, and the open linked PR is the active fix candidate rather than a reason to close before merge.
Reproducibility: yes. Source inspection shows a managed root with stale
dependencies.honoandopenclaw.managedPeerDependenciescan receive a newer managedoverrides.honobefore npm runs, which npm Arborist rejects asEOVERRIDE.Root-cause cluster
Relationship:
canonicalCanonical: #91772
Summary: This issue is the canonical user report for stale managed peer pins conflicting with managed npm-root overrides; the active fix candidate is the open maintainer PR.
Members:
fixed_by_candidate: fix(plugins): reconcile managed npm root overrides with managed peer pins #91786 - The open mergeable PR uses closing references for this issue and implements the broader managed-root reconciliation with focused tests.superseded: fix: resolve stale peer dep pins conflicting with managed overrides #93718 - This closed unmerged PR attempted the same stale-pin conflict but was superseded by the broader canonical repair path.Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.
Next step
A linked open maintainer PR already owns the implementation, so ClawSweeper should not queue a competing fix PR.
Review details
Best possible solution:
Review and land #91786 if maintainers accept its managed-root upgrade behavior, then close this issue as implemented while tracking the misleading post-failure hook-pack message separately.
Do we have a high-confidence way to reproduce the issue?
Yes. Source inspection shows a managed root with stale
dependencies.honoandopenclaw.managedPeerDependenciescan receive a newer managedoverrides.honobefore npm runs, which npm Arborist rejects asEOVERRIDE.Is this the best way to solve the issue?
Yes. The fix belongs in shared managed npm-root reconciliation across install/update/rollback writers; the open PR is the best current path, pending maintainer acceptance of the upgrade rewrite behavior.
AGENTS.md: found and applied where relevant.
Remaining risk / open question:
Codex review notes: model internal, reasoning high; reviewed against 2166652eb3e8.
Label changes
Label justifications:
P1: Affected managed plugin npm roots can have every later plugin install or update blocked by npm EOVERRIDE.impact:other: The concrete impact is managed plugin install/update failure and possible plugin disablement, which is maintainer-visible but outside the more specific owned impact labels.Evidence reviewed
What I checked:
readOpenClawManagedNpmRootOverrides()readspnpm-workspace.yamlfrom the OpenClaw package root and returns itsoverridesblock for managed npm roots. (src/infra/npm-managed-root.ts:231, 2166652eb3e8)syncManagedNpmRootPeerDependencies()still writesdependencies[packageName] ?? dependencySpec, then assigns managed overrides without reconciling same-name root dependencies. (src/infra/npm-managed-root.ts:798, 2166652eb3e8)src/plugins/install.ts:1285, 2166652eb3e8)v2026.6.8contains the same stale-pin preservation line insyncManagedNpmRootPeerDependencies(), so there is no shipped fix yet. (src/infra/npm-managed-root.ts:799, 844f405ac1be)assertRootOverrides()throwsEOVERRIDEwhen an override changes a root direct dependency's effective spec, matching the stale pin plus newer override manifest.Likely related people:
pnpm-workspace.yamloverride set. (role: introduced related override export behavior; confidence: high; commits: 392af2e61201; files:src/infra/npm-managed-root.ts,pnpm-workspace.yaml)src/infra/npm-managed-root.ts,src/infra/npm-managed-root.test.ts,src/plugins/install.ts)src/infra/npm-managed-root.ts,src/plugins/install.ts)src/infra/npm-managed-root.ts,src/infra/npm-managed-root.test.ts)How this review workflow works
@clawsweeper re-reviewcomments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.@clawsweeper re-reviewor@clawsweeper re-runon an open PR or issue to request a fresh review only.@clawsweeper reviewto request a fresh review only.@clawsweeper autofix,@clawsweeper automerge,@clawsweeper fix ci, or@clawsweeper address review.@clawsweeper explainto ask for more context, or@clawsweeper stopto stop active automation.feat(openclaw): detect + auto-repair the EOVERRIDE plugin-disable tra…
mkdelta221 commentedon Jun 13, 2026
Reproduced on OpenClaw 2026.6.6 —
EOVERRIDEon plugin update, plugin then silently disabledConfirming this is still live on
2026.6.6and adding a root-cause trace.openclaw update/openclaw plugins install --forcefails for our plugin (@drakon-systems/shieldcortex-realtime) with:OpenClaw then sets
plugins.entries.<id>.enabled = falseand continues without the plugin, so the failure is easy to miss until telemetry from the plugin goes quiet.Mechanism (verified against the installed bundled dist)
Each plugin gets a managed npm "project" at
~/.openclaw/npm/projects/<name>-<hash>/package.jsoncontainingdependencies(managed peer pins),overrides(imported from OpenClaw's bundledpnpm-workspace.yaml), and anopenclaw: { managedOverrides, managedPeerDependencies }tracking block.readHostWorkspaceOverrides()(npm-managed-root-*.js:56) andreadOpenClawManagedNpmRootOverrides()(:88) import OpenClaw'spnpm-workspace.yamloverridesinto the managed manifest'soverrides. These advance every release — currentlyhono: 4.12.21inpnpm-workspace.yaml:73.collectNpmLockPeerDependencyPins()(:207) derives managed peer-dep pins from the resolved lockfile'speerDependenciesand writes them intodependencies.syncManagedNpmRootPeerDependencies()(:387) is where the two collide::398-400writes peer pins todependencies, but preserves any existing pin:nextDependencies[packageName] = dependencies[packageName] ?? dependencySpec.:404-405clears prior managed override keys, thenObject.assign(overrides, managedOverrides)writes the current override version — with no check that the same key also sits independenciesat a different version.collectExistingManagedPeerDependencyPins()+ its use incollectNpmResolvedManagedNpmRootPeerDependencyPins()(:263,:296) and thereturn fallbackPeerPinson resolution failure (:339). So the pin from an older OpenClaw era survives even though the override version has since moved on.Root cause: the managed-peer dependency pin never advances across OpenClaw upgrades, but the imported override does advance each release. When a package ends up in BOTH
dependencies(stale, e.g.hono@4.12.23from an older era) andoverrides(current, e.g.hono@4.12.21), npm'sassertRootOverridesrejects the manifest — you may not override a root direct dependency at a different version.Version-mismatch nuance (verified empirically): the conflict fires only on a version mismatch. When
dependencies.honoandoverrides.honoare the same version, the install succeeds. Deleting the staledependencies.honoand reinstalling makes OpenClaw re-derive it at the override version in both places (4.12.21), and the install then succeeds. (After applying that workaround locally, our managed manifest now readshono: 4.12.21in bothdependenciesandoverrides, and updates pass.)This is not a plugin-side bug
dependenciesand zerooverrides— onlypeerDependencies: { shieldcortex: ">=4.18.3 <5.0.0", openclaw: ">=2026.3.22" }. Nothing in the plugin pins or overrideshono.honoentry in our manageddependenciesis entirely OpenClaw-injected (via the managed-peer-pin path, because our peer graph pullshonotransitively) and never pruned or reconciled against the advancing override.openclaw-brave-pluginandopenclaw-codexhave nomanagedPeerDependenciesblock and carryhonoinoverridesonly (4.12.21), never independencies— so they have nothing to drift, and they update fine. Only a plugin that triggers a managed peer pin forhonois exposed.Suggested fixes (either resolves it)
syncManagedNpmRootPeerDependencies(), beforeObject.assign(overrides, managedOverrides), for any managed-override key that also exists independencies, align them — set the dependency pin to the override version (or drop the dependency pin so the override governs). Equivalently: never let a managed-peer pin and a managed override for the same package drift to different versions.previousManagedPeerDependencySet); making update behave the same way prevents the pin from ever going stale relative to the override.Separately: please consider not silently disabling a plugin on this specific npm error class without a clearly surfaced, one-command remediation. The current
enabled=falsebehaviour makes a recoverable manifest-reconciliation issue look like the plugin simply stopped working.Suggested patch (pseudo-diff, against bundled
npm-managed-root-*.jssymbols)async function syncManagedNpmRootPeerDependencies(params) { // ... const overrides = readOverrideRecord(manifest.overrides); for (const key of readManagedOverrideKeys(manifest.openclaw)) delete overrides[key]; Object.assign(overrides, managedOverrides); + + // Reconcile: a managed override and a managed-peer pin for the same package + // must never sit at different versions, or npm's assertRootOverrides rejects + // the manifest (EOVERRIDE). Let the (always-current) override govern. + for (const [packageName, overrideSpec] of Object.entries(managedOverrides)) { + if (typeof overrideSpec !== "string") continue; + if (Object.hasOwn(nextDependencies, packageName) && + nextDependencies[packageName] !== overrideSpec) { + nextDependencies[packageName] = overrideSpec; + } + } // ... }Option 2 instead drops the
dependencies[packageName] ??preservation at:400(and/or thefallbackPeerPinsreturn atinstall-*.js:339) so peer pins are re-derived from the current resolution every time, keeping them aligned with the advancing override by construction.Happy to test a patched build against our managed project if useful — it's a clean repro (managed
dependencies.honoat an older version than the bundledpnpm-workspace.yamloverride).