Why does npm global install of OpenClaw 2026.4.x break?

OpenClaw's package.json declares pnpm as package manager. npm's flat hoisting doesn't replicate pnpm's content-addressable layout, silently dropping channel plugin dependencies.

What is the MODULE_NOT_FOUND error in OpenClaw 2026.4.x?

After npm global install, every CLI command fails with Cannot find module errors for @slack/logger, @buape/carbon, @larksuiteoapi/node-sdk, grammy, and other channel plugins.

How to fix OpenClaw npm install broken CLI?

Uninstall via npm, then install using pnpm: npm uninstall -g openclaw && pnpm add -g openclaw@latest.

Which OpenClaw versions have the npm install bug?

All 2026.4.x versions from 4.5 through 4.12 are affected when installed via npm globally. The issue persists across macOS, Linux, and Windows.

Is the OpenClaw npm install breakage fixed?

As of v2026.4.12, the underlying pnpm/npm mismatch remains. The official workaround is to use pnpm for global installation instead of npm.

← Back to dashboard

clawsmith.com/signal/openclaw-npm-install-breakage-pattern-v2026-4x

⚠ IssueUnknownCoreLive

OpenClaw v2026.4.x npm Global Install Systematically Broken: pnpm Layout Mismatch Causes MODULE_NOT_FOUND on Every CLI Command

Every OpenClaw 2026.4.x npm global install silently breaks CLI due to pnpm/npm node_modules layout mismatch. At least 6 GitHub issues document cascading MODULE_NOT_FOUND failures across versions 4.5 through 4.12. Workaround: use pnpm instead of npm for global install.

Product Idea from this Signal

A sandbox environment that tests OpenClaw upgrades against your agents before they break production

399.4k ▲

Every OpenClaw release breaks something. v2026.3.22 broke the Dashboard and WhatsApp. v2026.3.2 silently disabled all agent tools. v2026.3.8 killed cron jobs and compaction. v2026.3.28 permanently broke the exec tool in a way that downgrading could not fix. Users discover these regressions after upgrading their production instance. There is no pre-upgrade testing, no rollback plan, and no way to know if a new version will break your specific configuration. This tool creates a sandboxed replica of your OpenClaw setup, runs the upgrade there first, executes your critical workflows against it, and gives you a pass/fail verdict before touching production.

DEVTOOLCLITESTINGSYSADMIN

Wide OpenView Opportunity →

Product Idea from this Signal

A process supervisor that keeps the OpenClaw gateway alive through crashes, silent restarts, and update-induced failures

396.9k ▲

The OpenClaw gateway silently restarts every 50 minutes killing all active ACP sessions. Telegram integration crashes with AbortError every 20-30 minutes. The doctor --fix command hits a stack overflow and generates thousands of clobbered backup files instead of recovering. After updates, the gateway fails to restart because npm overwrites dist/ while the process is still running. There is no reliable supervision layer that keeps the gateway running, detects crash loops, and recovers gracefully. This tool wraps the gateway in a battle-tested supervisor that handles all known failure modes and keeps your agents online.

DEVTOOLCLISYSADMINRELIABILITY

UnderservedView Opportunity →