openclaw - 💡(How to fix) Fix Feature Request: Support excludePrefixes for session visibility filtering [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#70483Fetched 2026-04-24 05:57:29
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
Participants

Code Example

{
  "tools": {
    "sessions": {
      "visibility": {
        "mode": "all",
        "excludePrefixes": ["dreaming-", "cron-", "task-"]
      }
    }
  }
}
RAW_BUFFERClick to expand / collapse

Problem

Memory Dreaming system creates background sessions with names like:

  • dreaming-narrative-deep-xxx
  • dreaming-narrative-rem-xxx

These sessions clutter the session list in Control UI, making it harder to find actual user sessions.

Current Behavior

tools.sessions.visibility only accepts: self | tree | agent | all

No way to filter out specific session name prefixes.

Proposed Solution

Add excludePrefixes option to session visibility config:

{
  "tools": {
    "sessions": {
      "visibility": {
        "mode": "all",
        "excludePrefixes": ["dreaming-", "cron-", "task-"]
      }
    }
  }
}

This would:

  1. Hide sessions matching prefixes from Control UI session list
  2. Keep functionality intact (sessions still exist, just not visible)
  3. Allow users to customize which background sessions to hide

Use Case

Users who enable Memory Dreaming want the memory consolidation feature, but don't need to see the internal dreaming sessions in their UI.

Environment

  • OpenClaw: 2026.4.15 (041266a)
  • OS: Windows 10

extent analysis

TL;DR

Adding an excludePrefixes option to the session visibility config may help hide unwanted background sessions from the Control UI session list.

Guidance

  • Review the proposed solution and consider adding the excludePrefixes option to the session visibility config to filter out specific session name prefixes.
  • Verify that the excludePrefixes option works as expected by testing it with different prefixes and session names.
  • Check the documentation for the tools.sessions.visibility config to ensure that the new option is compatible with the existing mode options (self, tree, agent, all).
  • Test the proposed solution in a non-production environment before applying it to the production environment.

Example

{
  "tools": {
    "sessions": {
      "visibility": {
        "mode": "all",
        "excludePrefixes": ["dreaming-", "cron-", "task-"]
      }
    }
  }
}

Notes

The proposed solution assumes that the excludePrefixes option can be added to the existing session visibility config without breaking any existing functionality. However, this may not be the case, and further testing is needed to ensure compatibility.

Recommendation

Apply the proposed workaround by adding the excludePrefixes option to the session visibility config, as it provides a flexible way to filter out unwanted background sessions from the Control UI session list.

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 Feature Request: Support excludePrefixes for session visibility filtering [1 participants]