openclaw - 💡(How to fix) Fix [Bug]: Dreaming memory files incorrectly appear as agents in Web UI agent switcher

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…
RAW_BUFFERClick to expand / collapse

Bug Description

Markdown files under memory/dreaming/ (e.g. deep/2026-04-21.md, rem/2026-04-21.md, light/2026-04-21.md) are incorrectly listed as selectable agents in the Web UI top-left agent switcher dropdown.

These files are auto-generated dreaming/memory log files and should not appear in the agent list.

Steps to Reproduce

  1. Have a multi-agent setup with dreaming enabled (files generated under workspace/memory/dreaming/{deep,rem,light}/)
  2. Open the Web UI
  3. Click the agent switcher in the top-left corner
  4. Observe that dreaming .md files appear as selectable "agents"

Expected Behavior

Only actual agent configurations should appear in the agent switcher. Files under memory/ (and its subdirectories) should be excluded from agent discovery.

Actual Behavior

Multiple dreaming memory files show up as agents in the switcher menu, cluttering the UI and causing confusion.

Possible Cause

The gateway or UI agent discovery logic may be scanning the entire workspace directory for .md files without properly filtering out memory/ subdirectories.

Environment

  • OS: macOS (Apple Silicon)
  • OpenClaw: latest
  • Channel: Web UI

extent analysis

TL;DR

The issue can likely be fixed by modifying the agent discovery logic to exclude Markdown files under the memory/ directory.

Guidance

  • Review the agent discovery logic to ensure it properly filters out memory/ subdirectories and only includes actual agent configurations.
  • Verify that the memory/ directory and its subdirectories are not being scanned for .md files by the gateway or UI agent discovery logic.
  • Consider adding a configuration option to exclude specific directories or file patterns from agent discovery.
  • Check if there are any existing filters or settings in the OpenClaw configuration that can be modified to achieve the desired behavior.

Example

No code snippet is provided as the issue does not contain sufficient information about the implementation details of the agent discovery logic.

Notes

The solution may require modifications to the OpenClaw codebase or configuration, and may involve updating the agent discovery logic to properly handle the memory/ directory and its subdirectories.

Recommendation

Apply a workaround by modifying the agent discovery logic to exclude Markdown files under the memory/ directory, as this is likely to be a more straightforward and targeted solution than attempting to upgrade to a potentially non-existent fixed version.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING