Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

openclaw plugins install appears to fail in the ClawHub-first resolution path with fetch failed and does not appear to fall back to npm for at least some npm package specs.

Steps to reproduce

1. Run:

openclaw plugins install @scope/plugin-name@1.0.1

2. Observe output similar to:

Resolving clawhub:@scope/plugin-name@1.0.1…
fetch failed

3. Optionally verify the same package is resolvable with npm:

npm view @scope/plugin-name@1.0.1 name version dist.tarball --json

Expected behavior

According to the CLI docs for openclaw plugins install ("ClawHub first, then npm"), if ClawHub resolution does not succeed, OpenClaw should fall back to npm resolution for valid npm package specs.

Actual behavior

OpenClaw attempts ClawHub resolution for the package spec, prints Resolving clawhub:..., then fails with fetch failed and exits without completing installation. Based on observed behavior, npm fallback does not occur.

OpenClaw version

2026.03.24

Operating system

Ubuntu 22.04

Install method

npm global

Model

soonet 4.6

Provider / routing chain

openclaw->claude

Additional provider/model setup details

No response

Logs, screenshots, and evidence

openclaw plugins install @scope/plugin-name@1.0.1
Resolving clawhub:@scope/plugin-name@1.0.1…
fetch failed

Optional comparison:

npm view @scope/plugin-name@1.0.1 name version dist.tarball --json

Impact and severity

Plugin installation can fail for npm package specs that should be handled by the documented "ClawHub first, then npm" flow.

Additional information

This was first noticed with a package hosted on a private/internal npm registry, but further testing suggests the issue is not specific to private registries. The broader issue appears to be that ClawHub resolution failure does not properly fall back to npm.