openclaw - 💡(How to fix) Fix qqbot plugin cache causes EACCES permission errors on every gateway restart (macOS) [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#75673Fetched 2026-05-02 05:31:57
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
2
Timeline (top)
closed ×1commented ×1

Error Message

On every gateway restart, the following error appears and causes the gateway to hang or fail to become reachable: 3. Observe EACCES error on qqbot plugin cache

Fix Action

Workaround

sudo chmod -R 777 ~/.openclaw/plugin-runtime-deps

Code Example

[channels] failed to load bundled channel qqbot: EACCES: permission denied, unlink '/Users/<user>/.openclaw/plugin-runtime-deps/openclaw-2026.4.26-17c3fa238f70/dist/extensions/qqbot/api.js'

---

sudo chmod -R 777 ~/.openclaw/plugin-runtime-deps
RAW_BUFFERClick to expand / collapse

Environment

  • macOS 12.7.6 (x64)
  • OpenClaw 2026.4.26
  • Node 22.22.0
  • Installed via npm global

Problem

On every gateway restart, the following error appears and causes the gateway to hang or fail to become reachable:

[channels] failed to load bundled channel qqbot: EACCES: permission denied, unlink '/Users/<user>/.openclaw/plugin-runtime-deps/openclaw-2026.4.26-17c3fa238f70/dist/extensions/qqbot/api.js'

The gateway process starts and says "ready" in logs but the websocket never becomes reachable until sudo chmod -R 777 ~/.openclaw/plugin-runtime-deps is run manually after every restart.

Steps to reproduce

  1. Install OpenClaw on macOS
  2. Run openclaw gateway restart
  3. Observe EACCES error on qqbot plugin cache
  4. Gateway hangs — openclaw gateway probe returns timeout

Workaround

sudo chmod -R 777 ~/.openclaw/plugin-runtime-deps

Expected behavior

Gateway should start cleanly without requiring manual permission fixes after every restart.

Notes

  • qqbot is disabled in config but the bundled plugin still attempts to clean up its cache directory on startup
  • Issue began after updating from 2026.4.24 to 2026.4.26
  • sudo rm -rf on the cache directory also fails with permission denied

extent analysis

TL;DR

The issue can be resolved by adjusting the permissions of the plugin-runtime-deps directory to allow the gateway process to access and manage the qqbot plugin cache without requiring manual intervention.

Guidance

  • The error message EACCES: permission denied indicates a permissions issue, suggesting that the gateway process lacks the necessary permissions to access or modify the api.js file within the plugin-runtime-deps directory.
  • The provided workaround sudo chmod -R 777 ~/.openclaw/plugin-runtime-deps temporarily resolves the issue by granting read, write, and execute permissions to all users, but this is not a secure long-term solution.
  • To mitigate the issue, consider adjusting the ownership of the plugin-runtime-deps directory to the user running the gateway process, or use a more restrictive permission setting that still allows the gateway to function.
  • Investigate why the qqbot plugin, despite being disabled in the config, attempts to clean up its cache directory on startup, as this behavior may be contributing to the permissions issue.

Example

No code snippet is provided as the issue is related to permissions and directory management rather than code functionality.

Notes

The solution may depend on the specific requirements and constraints of the OpenClaw gateway and its plugins. The issue began after updating from version 2026.4.24 to 2026.4.26, suggesting a potential change in how permissions are handled in the newer version.

Recommendation

Apply a more targeted workaround, such as adjusting the ownership or permissions of the plugin-runtime-deps directory to allow the gateway process to run without requiring sudo privileges, rather than relying on the provided chmod -R 777 workaround. This approach would help maintain security while resolving the functional issue.

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

Gateway should start cleanly without requiring manual permission fixes after every restart.

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 qqbot plugin cache causes EACCES permission errors on every gateway restart (macOS) [1 comments, 2 participants]