openclaw - 💡(How to fix) Fix Feature Request: Add configurable stopwords/filter for REM phase theme extraction [1 comments, 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#70881Fetched 2026-04-24 10:38:20
View on GitHub
Comments
1
Participants
1
Timeline
2
Reactions
0
Author
Participants
Timeline (top)
closed ×1commented ×1

Root Cause

  1. Noise reduction: Prevents structural terms from drowning out actual content themes
  2. Better UX: Users see meaningful themes instead of conversation mechanics
  3. Low impact fix: Doesn't affect the "persistent truths" extraction, only the theme labeling

Fix Action

Fix / Workaround

The current workaround is to ignore these false positive themes, but they appear consistently across all REM outputs, reducing the signal-to-noise ratio of the dreaming feature.

Code Example

• 反思主题:assistant 在 1171 条记忆中持续出现(confidence: 1.00
---

{
  "plugins": {
    "entries": {
      "memory-core": {
        "config": {
          "dreaming": {
            "enabled": true,
            "rem": {
              "themeStopwords": ["assistant", "user", "system"]
            }
          }
        }
      }
    }
  }
}
RAW_BUFFERClick to expand / collapse

Problem Description

The REM phase in dreaming extracts themes from session transcripts, but it currently includes structural role markers like assistant, user, and system as "themes" because they appear frequently in the conversation corpus.

Example:

• 反思主题:assistant 在 1171 条记忆中持续出现(confidence: 1.00)

This is a false positiveassistant is a message role marker, not a content theme. While the "persistent truths" extracted alongside are valuable, the theme label itself is misleading and creates noise in the dreaming output.

Current Behavior

  • REM phase extracts high-frequency terms as "themes"
  • No filtering mechanism for common structural terms
  • Results in themes like assistant, user, system being reported

Desired Behavior

Option to configure excluded/stop words for REM theme extraction, e.g.:

{
  "plugins": {
    "entries": {
      "memory-core": {
        "config": {
          "dreaming": {
            "enabled": true,
            "rem": {
              "themeStopwords": ["assistant", "user", "system"]
            }
          }
        }
      }
    }
  }
}

Or alternatively, hardcode common role markers as excluded from theme extraction.

Why This Matters

  1. Noise reduction: Prevents structural terms from drowning out actual content themes
  2. Better UX: Users see meaningful themes instead of conversation mechanics
  3. Low impact fix: Doesn't affect the "persistent truths" extraction, only the theme labeling

Environment

  • OpenClaw version: 2026.4.21 (f788c88)
  • memory-core plugin

Additional Context

The current workaround is to ignore these false positive themes, but they appear consistently across all REM outputs, reducing the signal-to-noise ratio of the dreaming feature.

extent analysis

TL;DR

Configure excluded/stop words for REM theme extraction to filter out common structural terms like assistant, user, and system.

Guidance

  • Identify the list of common structural role markers that are being incorrectly extracted as themes, such as assistant, user, and system.
  • Add these markers to the themeStopwords configuration option in the memory-core plugin, as shown in the desired behavior example.
  • Verify that the REM phase no longer extracts these structural terms as themes by checking the output of the dreaming feature.
  • Consider hardcoding common role markers as excluded from theme extraction if a configuration option is not available.

Example

{
  "plugins": {
    "entries": {
      "memory-core": {
        "config": {
          "dreaming": {
            "enabled": true,
            "rem": {
              "themeStopwords": ["assistant", "user", "system"]
            }
          }
        }
      }
    }
  }
}

Notes

The effectiveness of this solution may depend on the specific implementation of the REM phase and the memory-core plugin. Additional configuration options or code changes may be required to fully address the issue.

Recommendation

Apply workaround by configuring themeStopwords to exclude common structural terms, as this is a low-impact fix that can improve the signal-to-noise ratio of the dreaming feature.

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