openclaw - 💡(How to fix) Fix Feature: Configure dedicated LLM model for Dreaming subsystem [1 comments, 2 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#70475Fetched 2026-04-24 05:57:37
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
0
Author
Participants
Timeline (top)
commented ×1

Request the ability to configure a separate/dedicated LLM model for the Dreaming subsystem (REM / Light / Deep phases), instead of inheriting the agent's primary model.

Root Cause

Request the ability to configure a separate/dedicated LLM model for the Dreaming subsystem (REM / Light / Deep phases), instead of inheriting the agent's primary model.

Code Example

plugins:
  entries:
    memory-core:
      config:
        dreaming:
          model: ollama/qwen2.5:7b
RAW_BUFFERClick to expand / collapse

Summary

Request the ability to configure a separate/dedicated LLM model for the Dreaming subsystem (REM / Light / Deep phases), instead of inheriting the agent's primary model.

Problem

Currently, Dreaming uses the same model as the agent (e.g. ollama/glm-5.1:cloud). However, Dreaming tasks — claim extraction, reflection, pattern detection — are structured and low-complexity. Running them on a large/cloud model is unnecessary and expensive.

Cost impact: With 7 agents × 3 Dreaming phases per night, that's ~21 LLM calls/night hitting a cloud endpoint that could run locally on a smaller model.

Proposed Solution

Add a config option to specify a dedicated model for Dreaming, e.g.:

plugins:
  entries:
    memory-core:
      config:
        dreaming:
          model: ollama/qwen2.5:7b

When unset, Dreaming should inherit the agent model (current behavior) — ensuring backwards compatibility.

Related

  • agents.defaults.experimental.localModelLean exists but only controls tool availability, not model selection for subsystems like Dreaming.

Benefits

  • Cost reduction: Offload ~21 nightly cloud calls per agent group to a local model.
  • Performance: Smaller models are faster for structured extraction tasks.
  • Flexibility: Users can tune cost/quality trade-offs per subsystem.

Acceptance Criteria

  • Config key to set a Dreaming-specific model
  • Default behavior unchanged (inherit agent model)
  • Documentation update

extent analysis

TL;DR

Implement a configuration option to specify a dedicated model for the Dreaming subsystem, allowing for cost reduction and performance improvement.

Guidance

  • Add a dreaming.model configuration key to the memory-core plugin, as proposed in the issue, to enable specification of a dedicated model for Dreaming tasks.
  • Update the documentation to reflect the new configuration option and its benefits, including cost reduction and performance improvement.
  • Test the new configuration option with a smaller model, such as ollama/qwen2.5:7b, to verify its effectiveness in offloading cloud calls and improving performance.
  • Consider adding a fallback mechanism to ensure backwards compatibility, where the agent's primary model is used if the dedicated Dreaming model is not specified.

Example

plugins:
  entries:
    memory-core:
      config:
        dreaming:
          model: ollama/qwen2.5:7b

This example demonstrates how to configure a dedicated model for the Dreaming subsystem using the proposed dreaming.model key.

Notes

The proposed solution assumes that the smaller model is capable of handling the structured and low-complexity tasks of the Dreaming subsystem. Further testing and evaluation may be necessary to determine the optimal model for this use case.

Recommendation

Apply the proposed workaround by adding the dreaming.model configuration key and updating the documentation, as this will allow for cost reduction and performance improvement while maintaining backwards compatibility.

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: Configure dedicated LLM model for Dreaming subsystem [1 comments, 2 participants]