openclaw - 💡(How to fix) Fix Dreaming-generated sessions appear in normal Control UI session picker

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…

Dreaming-generated sessions (for example dreaming-narrative-light-* and dreaming-narrative-rem-*) are being persisted into the normal session store and show up in the Control UI session switcher/dropdown as if they were ordinary user sessions.

This clutters the session picker with many internal/background sessions and makes it harder to switch between real conversations.

Root Cause

Notes

  • Restarting the gateway does not remove them, because they are stored sessions rather than stale UI state.
  • This feels more like a product/session-classification issue than a refresh bug.
RAW_BUFFERClick to expand / collapse

Summary

Dreaming-generated sessions (for example dreaming-narrative-light-* and dreaming-narrative-rem-*) are being persisted into the normal session store and show up in the Control UI session switcher/dropdown as if they were ordinary user sessions.

This clutters the session picker with many internal/background sessions and makes it harder to switch between real conversations.

What I expected

Internal dreaming/background runs should either:

  • not be persisted as normal switchable sessions, or
  • be hidden from the default Control UI session picker, or
  • be clearly separated behind a filter like "internal/system sessions".

What actually happens

The session dropdown contains many entries like:

  • dreaming-narrative-light-1776455140188
  • dreaming-narrative-rem-1776455140188
  • many more similar dreaming-* sessions

These appear alongside real chat sessions such as main / Dustin (@dct1n) ..., so the picker becomes noisy very quickly.

Evidence

On my instance, sessions_list returns persisted sessions with keys such as:

  • agent:main:dreaming-narrative-rem-1776455140188
  • agent:main:dreaming-narrative-light-1776455140188
  • agent:main:dreaming-narrative-rem-1776455123413
  • agent:main:dreaming-narrative-light-1776455123413

And the Control UI dropdown shows those same entries intermixed with real user sessions.

Notes

  • Restarting the gateway does not remove them, because they are stored sessions rather than stale UI state.
  • This feels more like a product/session-classification issue than a refresh bug.

Environment

  • OpenClaw: 2026.4.15
  • Gateway service: LaunchAgent on macOS
  • Control UI connected to local gateway
  • Dreaming enabled

Suggested fixes

Any of these would solve it:

  1. Mark dreaming sessions as internal/non-switchable
  2. Exclude internal session classes from the default session picker
  3. Add a UI toggle/filter for system/background sessions
  4. Store dreaming runs somewhere other than the normal conversational session list

If helpful, I can provide a screenshot of the session dropdown showing the cluttered list.

extent analysis

TL;DR

Marking dreaming sessions as internal/non-switchable or excluding internal session classes from the default session picker could resolve the issue.

Guidance

  • Identify the session classification logic to determine how dreaming sessions are currently being persisted and displayed.
  • Consider implementing a filter or toggle in the Control UI to separate internal/system sessions from user sessions.
  • Review the session storage mechanism to assess the feasibility of storing dreaming runs separately from conversational sessions.
  • Evaluate the suggested fixes provided in the issue, such as marking dreaming sessions as internal/non-switchable or excluding internal session classes from the default session picker.

Example

No code snippet is provided as the issue does not contain sufficient technical details to generate a specific example.

Notes

The issue seems to be related to session classification and storage, rather than a refresh bug. The provided environment details, such as OpenClaw version and Gateway service, may be relevant in determining the root cause and suitable fix.

Recommendation

Apply a workaround, such as marking dreaming sessions as internal/non-switchable, as it is a straightforward solution that can help mitigate the issue without requiring significant changes to the underlying infrastructure.

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

openclaw - 💡(How to fix) Fix Dreaming-generated sessions appear in normal Control UI session picker