Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Dreaming only creates sessions for main agent in multi-agent setup on 2026.4.15 [1 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#68674•Fetched 2026-04-19 15:08:45
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
najef1979-codenajef1979-code
Participants
najef1979-codenajef1979-code
Timeline (top)
labeled ×2

In a multi-agent setup, I enabled dreaming, but only the main/default agent gets dreaming sessions. Other agents do not appear to get automatic dream sessions.

Error Message

[openclaw] Failed to start CLI: Error: The openclaw help command is unavailable because plugins.allow excludes "help".

Root Cause

openclaw help is blocked in my setup because plugins.allow excludes "help": bash openclaw help | grep memory || true [openclaw] Failed to start CLI: Error: The openclaw help command is unavailable because plugins.allow excludes "help". But that seems separate from the actual dreaming behavior.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Summary

In a multi-agent setup, I enabled dreaming, but only the main/default agent gets dreaming sessions. Other agents do not appear to get automatic dream sessions.

Version

bash openclaw --version OpenClaw 2026.4.15 (041266a)

Steps to reproduce

  1. Configure multiple agents
  2. Enable dreaming
  3. Wait for dreaming to run
  4. Observe that only the main/default agent gets dream sessions

Expected behavior

When dreaming is enabled, I expected automatic dreaming runs to apply across configured agent memory workspaces, not just the main agent.

What actually happens

Only the main/default agent gets dream sessions.

Things I checked

I verified this is not just a binary/path mismatch: bash which openclaw /home/najef/.nvm/versions/node/v24.14.1/bin/openclaw I also checked the relevant plugin config paths: bash openclaw config get plugins.slots.memory Config path not found: plugins.slots.memory openclaw config get plugins.entries.memory-core.enabled Config path not found: plugins.entries.memory-core.enabled And plugins.allow includes the memory plugins: bash openclaw config get plugins.allow [ "browser", "lossless-claw", "telegram", "minimax", "metaclaw-openclaw", "anthropic", "memory-wiki", "memory-core", "active-memory", "brave", "duckduckgo", "firecrawl" ] So from what I can tell:

  • memory-core is allowlisted
  • the memory slot/config is just using defaults
  • this does not look like a local config mistake

Extra note

openclaw help is blocked in my setup because plugins.allow excludes "help": bash openclaw help | grep memory || true [openclaw] Failed to start CLI: Error: The openclaw help command is unavailable because plugins.allow excludes "help". But that seems separate from the actual dreaming behavior.

Actual behavior

Only see session for my main agent.

OpenClaw version

OpenClaw 2026.4.15 (041266a)

Operating system

Ubuntu

Install method

Script

Model

NVT

Provider / routing chain

NVT

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

Suspected issue

This looks like the managed dreaming cron/session is only targeting the main session/agent, instead of fanning out to all configured memory workspaces in a multi-agent setup.

Repro

  1. Configure multiple agents
  2. Enable dreaming
  3. Wait for dreaming to run
  4. Observe that only the main/default agent gets dream sessions

Expected fix

Either:

  • dreaming should automatically fan out across all configured agent memory workspaces, or
  • docs should clarify that auto-dreaming is main-agent-only

Docs referenced

extent analysis

TL;DR

The issue can be resolved by either modifying the dreaming configuration to fan out across all configured agent memory workspaces or updating the documentation to clarify that auto-dreaming is main-agent-only.

Guidance

  • Review the OpenClaw configuration to ensure that the dreaming setup is correctly configured for multi-agent environments.
  • Check the documentation for any specific settings or flags that need to be enabled for dreaming to work across multiple agents.
  • Verify that the plugins.allow list includes all necessary plugins for dreaming to function correctly across all agents.
  • Consider testing the dreaming functionality with a minimal setup to isolate the issue and determine if it's specific to the multi-agent configuration.

Example

No code snippet is provided as the issue seems to be related to configuration and documentation rather than code.

Notes

The issue might be related to a limitation or misunderstanding of the current OpenClaw version (2026.4.15) and its dreaming functionality in multi-agent setups. Further investigation into the documentation and configuration is necessary to determine the root cause.

Recommendation

Apply workaround: Modify the dreaming configuration to manually target all configured agent memory workspaces if automatic fanning out is not supported. This approach allows for a temporary solution until the documentation or the dreaming functionality is updated to support multi-agent environments.

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

When dreaming is enabled, I expected automatic dreaming runs to apply across configured agent memory workspaces, not just the main agent.

#agent setup#cache issue#memory leak#API versioning#request timeout

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]: Dreaming only creates sessions for main agent in multi-agent setup on 2026.4.15 [1 participants]