Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: plugins.allow excludes 'lcm' — bundled CLI surface unavailable and unmodifiable [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#77183•Fetched 2026-05-05 05:51:20
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
2
Author
Nerdless-ship-itNerdless-ship-it
Participants
clawsweeper[bot]clawsweeper[bot]Nerdless-ship-itNerdless-ship-it
Timeline (top)
closed ×1commented ×1

The plugins.allow configuration path is protected and cannot be modified via config.patch, which means the bundled lcm CLI surface is permanently inaccessible on affected installations.

Error Message

Error: The openclaw lcm command is unavailable because plugins.allow excludes "lcm". Add "lcm" to plugins.allow if you want that bundled plugin CLI surface.

Root Cause

  1. Run openclaw lcm status (or any openclaw lcm * subcommand) on a Windows or macOS installation.
  2. Observe error: 
    Error: The `openclaw lcm` command is unavailable because `plugins.allow` excludes "lcm".
Add "lcm" to `plugins.allow` if you want that bundled plugin CLI surface.
  3. Attempt to add lcm to plugins.allow via config.patch: 
    gateway config.patch { "plugins": { "allow": ["lcm"] } }
  4. Observe the patch is silently rejected or fails because plugins.allow is a protected path.

Fix Action

Fix / Workaround

The plugins.allow configuration path is protected and cannot be modified via config.patch, which means the bundled lcm CLI surface is permanently inaccessible on affected installations.

  1. Run openclaw lcm status (or any openclaw lcm * subcommand) on a Windows or macOS installation.
  2. Observe error: 
    Error: The `openclaw lcm` command is unavailable because `plugins.allow` excludes "lcm".
Add "lcm" to `plugins.allow` if you want that bundled plugin CLI surface.
  3. Attempt to add lcm to plugins.allow via config.patch: 
    gateway config.patch { "plugins": { "allow": ["lcm"] } }
  4. Observe the patch is silently rejected or fails because plugins.allow is a protected path.

One of:

  1. Allow plugins.allow to accept lcm via config.patch (remove the protection, or add a specific override for bundled plugins)
  2. Ship openclaw lcm commands without requiring plugins.allow entry (since it is bundled, not third-party)
  3. Document clearly what the supported path forward is for users who need LCM diagnostics

Code Example

Error: The `openclaw lcm` command is unavailable because `plugins.allow` excludes "lcm".
   Add "lcm" to `plugins.allow` if you want that bundled plugin CLI surface.

---

gateway config.patch { "plugins": { "allow": ["lcm"] } }

---

[plugins] Failed to start CLI: Error: The `openclaw lcm` command is unavailable because `plugins.allow` excludes "lcm". Add "lcm" to `plugins.allow` if you want that bundled plugin CLI surface.
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug / Design issue

Summary

The plugins.allow configuration path is protected and cannot be modified via config.patch, which means the bundled lcm CLI surface is permanently inaccessible on affected installations.

Steps to reproduce

  1. Run openclaw lcm status (or any openclaw lcm * subcommand) on a Windows or macOS installation.
  2. Observe error: 
    Error: The `openclaw lcm` command is unavailable because `plugins.allow` excludes "lcm".
Add "lcm" to `plugins.allow` if you want that bundled plugin CLI surface.
  3. Attempt to add lcm to plugins.allow via config.patch: 
    gateway config.patch { "plugins": { "allow": ["lcm"] } }
  4. Observe the patch is silently rejected or fails because plugins.allow is a protected path.

Expected behavior

Either:

  • plugins.allow should accept modifications to enable the bundled lcm CLI, OR
  • The openclaw lcm command should be available without requiring plugins.allow changes (since it is a bundled plugin, not a third-party one), OR
  • A clear error message should be shown explaining how to resolve the situation.

Actual behavior

The openclaw lcm command is blocked by default, and the user cannot add lcm to plugins.allow because that path is protected against modification. The only path forward is modifying openclaw.json manually, which users should not do directly.

Impact

Users cannot access the LCM status/diagnostics for lossless-claw context engine, which is the recommended context engine for production use. This makes it impossible to diagnose whether lossless-claw is properly registered and active.

Additional context

  • OpenClaw version: 2026.5.2
  • OS: Windows 10.0.26200 (x64)
  • Install method: npm global
  • Error message reproduced verbatim: 
    [plugins] Failed to start CLI: Error: The `openclaw lcm` command is unavailable because `plugins.allow` excludes "lcm". Add "lcm" to `plugins.allow` if you want that bundled plugin CLI surface.
  • Related: Issue #77063 (context-engine lossless-claw not registered) - the inability to run /lcm prevents users from self-diagnosing this exact problem.

Suggested fix

One of:

  1. Allow plugins.allow to accept lcm via config.patch (remove the protection, or add a specific override for bundled plugins)
  2. Ship openclaw lcm commands without requiring plugins.allow entry (since it is bundled, not third-party)
  3. Document clearly what the supported path forward is for users who need LCM diagnostics

extent analysis

TL;DR

To resolve the issue, consider allowing plugins.allow to accept lcm via config.patch or shipping openclaw lcm commands without requiring a plugins.allow entry.

Guidance

  • The error message suggests that adding lcm to plugins.allow would resolve the issue, but the path is protected against modification.
  • Users can try manually modifying openclaw.json to add lcm to plugins.allow, but this is not recommended.
  • The issue can be mitigated by documenting a clear path forward for users who need LCM diagnostics.
  • Consider removing the protection on plugins.allow or adding a specific override for bundled plugins like lcm.

Example

No code snippet is provided as the issue is more related to configuration and design.

Notes

The suggested fixes are based on the information provided in the issue and may not be exhaustive. The issue highlights a design or behavior bug that needs to be addressed to provide a seamless user experience.

Recommendation

Apply a workaround by documenting a clear path forward for users who need LCM diagnostics, as this is the most immediate way to help users without waiting for a potential code change to remove the protection on plugins.allow or to ship openclaw lcm commands without requiring a plugins.allow entry.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Either:

  • plugins.allow should accept modifications to enable the bundled lcm CLI, OR
  • The openclaw lcm command should be available without requiring plugins.allow changes (since it is a bundled plugin, not a third-party one), OR
  • A clear error message should be shown explaining how to resolve the situation.
#installation#training loop#device allocation#model download#tokenizer error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: plugins.allow excludes 'lcm' — bundled CLI surface unavailable and unmodifiable [1 comments, 2 participants]