openclaw - 💡(How to fix) Fix Bundled LINE plugin fails to start: no bundled plugin manifest found for line [1 participants]

Bug Report: Bundled LINE plugin fails to start with "no bundled plugin manifest found"

Environment

• OS: macOS
• OpenClaw Version: 2026.4.2 (installed via Homebrew: /opt/homebrew/bin/openclaw)
• Plugin: bundled LINE plugin (@openclaw/line is not installed globally via npm)
• Bundled plugin version shown by CLI: 2026.4.1-beta.1

Describe the Bug

In OpenClaw 2026.4.2, the bundled LINE channel provider fails to start.

The physical manifest file exists on disk and the plugin is recognized as loaded by the CLI, but the runtime still throws:

Bundled plugin public surface access blocked for "line" via line/runtime-api.js: no bundled plugin manifest found for line

This happens even after removing plugins.load.paths and plugins.installs.line so the setup falls back to pure bundled discovery.

Steps to Reproduce

1. Install OpenClaw 2026.4.2 via Homebrew.
2. Configure channels.line with valid credentials.
3. Ensure pure bundled discovery by removing:
   • plugins.load.paths entries for LINE
   • plugins.installs.line
4. Keep:
   • plugins.entries.line.enabled=true
   • valid channels.line credentials
5. Restart the gateway.
6. Run:

   openclaw channels status --probe --json

Expected Behavior

The LINE provider should transition to the running state.

Actual Behavior

The LINE provider starts, then immediately exits with the bundled manifest lookup error.

Relevant Observations

• which openclaw → /opt/homebrew/bin/openclaw
• openclaw --version → OpenClaw 2026.4.2 (d74a122)
• openclaw plugins inspect line reports:
  • Status: loaded
  • Source: /opt/homebrew/lib/node_modules/openclaw/dist/extensions/line/index.js
  • Install source: path (before cleanup)
  • Version: 2026.4.1-beta.1
• The following files exist:
  • /opt/homebrew/lib/node_modules/openclaw/dist/extensions/line/openclaw.plugin.json
  • /opt/homebrew/lib/node_modules/openclaw/dist/extensions/line/runtime-api.js
  • /opt/homebrew/lib/node_modules/openclaw/dist/extensions/line/package.json
• After removing plugins.load.paths and plugins.installs.line, the error still persists.

Logs

{"subsystem":"gateway/channels/line"} "[default] starting LINE provider (Hama-bot)"
{"subsystem":"gateway/channels/line"} "[default] channel exited: Bundled plugin public surface access blocked for \"line\" via line/runtime-api.js: no bundled plugin manifest found for line"
{"subsystem":"gateway/channels/line"} "[default] auto-restart attempt 1/10 in 5s"

Later retries show the same failure repeatedly.

Additional Context

It looks like the runtime facade tries to resolve the LINE bundled manifest through the bundled manifest registry, but fails to find a manifest record for line even though the manifest file is physically present in dist/extensions/line.

So this appears to be a bundled plugin registry / facade resolution issue rather than a credential/config issue.