Why does @openclaw/feishu show 404 Not Found?

The @openclaw/feishu scoped package is not published to the public npm registry. The openclaw plugins install command attempts npm pack from the registry, which fails with 404. You need to install it from the local plugin directory or build from source.

What does "Access token expired or revoked" mean?

This means your npm CLI has a stale authentication token (from npm login). The token is either expired or was revoked. Even though the package is public, the stale token causes npm to attempt authenticated access, which fails.

Is the feishu plugin officially supported?

The feishu channel plugin is part of the OpenClaw repository as a community plugin. It requires building from source or using the local install method rather than npm registry download.

I installed feishu but get "Cannot find module zod" — what now?

The feishu plugin has peer dependencies that aren't automatically installed via local install. Run npm install zod in the plugin directory, or install all dependencies with pnpm install from the OpenClaw source root.

Is this related to generic exec plugin install failures in v2026.3.2?

Yes. Some v2026.3.2 reports show plugin install/npm pack failures beyond Feishu. The same local-install and dependency-first workflow is the safest recovery path.

Feishu Plugin Install Fails — npm 404 / Token Expired

Common Feishu Setup Issue

Tracked in openclaw/openclaw#8576. Running openclaw plugins install @openclaw/feishu fails because the scoped package is not published to the npm public registry. This affects all feishu/飞书 users trying the standard install path.

Also watch: openclaw/openclaw#32833 (exec plugin install failures on v2026.3.2).

You want to connect OpenClaw to Feishu (飞书). You run openclaw plugins install @openclaw/feishu and get two errors: "npm notice Access token expired or revoked" followed by "npm error 404 Not Found — GET https://registry.npmjs.org/@openclaw%2ffeishu." Neither error tells you the real problem: the package simply isn't on npm.

Next Step

Fix now, then reduce repeat incidents

If this issue keeps coming back, validate your setup in Doctor first, then harden your config.

Open Doctor Harden Config

Jump to Section

What the Error Looks Like Why This Happens Fix A: Local Install (Recommended) Fix B: Build from Source Fix C: Clear Stale npm Token Fix Missing Dependencies Verify Feishu Channel Works Still Stuck

What the Error Looks Like

The command that fails

openclaw plugins install @openclaw/feishu

npm notice Access token expired or revoked. Please try logging in again.

npm error code E404

npm error 404 Not Found - GET https://registry.npmjs.org/@openclaw%2ffeishu - Not found

npm pack failed: npm notice Access token expired or revoked.

Failed to install @openclaw/feishu: npm pack failed

You might also see a secondary error after attempting a workaround: Error: Cannot find module 'zod'. This is a separate dependency issue covered in the Missing Dependencies section below.

Why This Happens

Package not published to npm

The @openclaw/feishu scoped package was never published to the public npm registry. The plugin exists in the OpenClaw source repository but isn't distributed as a standalone npm package. The openclaw plugins install command assumes all plugins are on npm, which is wrong for community/first-party plugins like feishu.

Stale npm auth token amplifies the error

If you previously ran npm login, your local .npmrc has an auth token. When npm tries to fetch a non-existent scoped package, it first tries authenticated access (which fails with "token expired"), then falls back to public access (which fails with 404). Two confusing errors for one simple problem.

Missing peer dependencies after local install

Even if you get past the 404 with a local install, the feishu plugin depends on zod, node-fetch, and other packages that aren't bundled. The local install method doesn't run npm install inside the plugin directory, so these dependencies are missing.

Fix A: Local Install (Recommended)

Download the plugin source and install it locally. This is the officially recommended method for plugins not published to npm.

Step 1 — Clone the plugin

git clone https://github.com/openclaw/openclaw.git /tmp/openclaw-src
cd /tmp/openclaw-src/plugins/feishu

Step 2 — Install dependencies

npm install

Step 3 — Install plugin locally

openclaw plugins install --local /tmp/openclaw-src/plugins/feishu

Step 4 — Restart gateway

openclaw gateway restart

Fix B: Build from Source

If you want the full development setup (useful for contributing fixes or running multiple plugins):

Full source build

git clone https://github.com/openclaw/openclaw.git
cd openclaw
pnpm install       # installs all dependencies including plugin deps
pnpm build         # builds all plugins
openclaw plugins install --local plugins/feishu

Fix C: Clear Stale npm Token

Even though the real issue is the 404, the "token expired" error is annoying and can mask other problems. Clear it to get cleaner error messages:

Remove stale npm auth

# Check if you have a token
npm whoami 2>&1

# If it shows an error, clear the token
npm logout
# Or manually remove the auth line from ~/.npmrc
# grep -n "authToken" ~/.npmrc

Clearing the token doesn't fix the 404 — the package still isn't on npm. But it removes the confusing "token expired" noise so you can focus on the real solution (local install).

Fix Missing Dependencies (zod, node-fetch, etc.)

After local install, if the feishu channel fails to load with module errors:

Install missing peer deps

# Navigate to where the plugin was installed
cd $(openclaw plugins path)/feishu

# Install missing dependencies
npm install zod node-fetch

# Restart gateway to reload plugin
openclaw gateway restart

Verify Feishu Channel Works

Plugin is listed as installed

openclaw plugins list

Expected: @openclaw/feishu shows as installed (green)

Feishu channel loads without module errors

openclaw logs --tail 20 | grep -i feishu

Expected: "feishu channel started" or similar — no "Cannot find module" errors

Doctor reports feishu as healthy

openclaw doctor

Expected: Feishu channel check passes (green checkmark)

Test message roundtrip

Expected: Send a test message in Feishu to your bot — it should respond within a few seconds

Still Stuck?

If the plugin installs but Feishu messages aren't reaching OpenClaw, check your Feishu bot configuration:

Verify Feishu config in clawdbot.json

openclaw config get channels.feishu
# Should show appId, appSecret, and webhook URL
# If any are empty, reconfigure:
# openclaw config set channels.feishu.appId "cli_xxxx"
# openclaw config set channels.feishu.appSecret "your-secret"

Run the Doctor

npx clawkit-doctor@latest

Checks plugin installation, channel configuration, and message delivery health.

Related Issues

Other plugin & channel setup problems:

Fix It Faster With Our Tools

Config Wizard

Generate a production-ready clawhub.json in 30 seconds.

Cost Simulator

Calculate your agent burn rate before you get surprised.

Skill Registry

Browse 9,000+ verified plugins for your OpenClaw agent.

Skill Finder

Describe your use case and find the right Claude Code skill instantly.

Did this guide solve your problem?