openclaw - 💡(How to fix) Fix Feature Request: Add execution field to dreaming config with fallback model support [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#70616Fetched 2026-04-24 05:55:39
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Participants

Currently, the memory-core schema only supports these dreaming fields:

  • enabled
  • frequency
  • timezone
  • verboseLogging
  • storage
  • phases

The execution field is not in the allowed list, preventing users from configuring fallback or cheaper models for DREAMING.

Root Cause

Currently, the memory-core schema only supports these dreaming fields:

  • enabled
  • frequency
  • timezone
  • verboseLogging
  • storage
  • phases

The execution field is not in the allowed list, preventing users from configuring fallback or cheaper models for DREAMING.

Code Example

dreaming:
  enabled: true
  execution:
    model: minimax/minimax-m2.5:free
    fallback:
      - model: google/gemini-2.0-flash-exp
      - model: anthropic/claude-3-haiku
RAW_BUFFERClick to expand / collapse

Description

Currently, the memory-core schema only supports these dreaming fields:

  • enabled
  • frequency
  • timezone
  • verboseLogging
  • storage
  • phases

The execution field is not in the allowed list, preventing users from configuring fallback or cheaper models for DREAMING.

Request

Please add an execution field to the dreaming configuration that allows users to specify:

  1. Fallback models - When the primary model fails or is unavailable
  2. Cheaper/Lightweight models - For cost-effective background dreaming tasks

This would help reduce costs while maintaining the dreaming functionality.

Use Case

Many users want to use cheaper models (like MiniMax-M2.5, Gemini Flash, etc.) for background dreaming tasks to save costs, while keeping the option to fall back to other models if needed.

Example Configuration (desired)

dreaming:
  enabled: true
  execution:
    model: minimax/minimax-m2.5:free
    fallback:
      - model: google/gemini-2.0-flash-exp
      - model: anthropic/claude-3-haiku

Thank you!

extent analysis

TL;DR

Add an execution field to the memory-core schema to support fallback and cheaper models for DREAMING.

Guidance

  • Update the memory-core schema to include the execution field with subfields for model and fallback to allow users to configure alternative models.
  • Verify the updated schema by checking the allowed fields for the dreaming configuration.
  • Consider adding validation for the fallback field to ensure it contains a list of valid model names.
  • Test the updated configuration with the desired example configuration to ensure it works as expected.

Example

dreaming:
  enabled: true
  execution:
    model: minimax/minimax-m2.5:free
    fallback:
      - model: google/gemini-2.0-flash-exp
      - model: anthropic/claude-3-haiku

Notes

The exact implementation details of the schema update and validation are not specified, so the guidance is focused on the general approach.

Recommendation

Apply workaround: Update the memory-core schema to include the execution field, as this will allow users to configure fallback and cheaper models for DREAMING, reducing costs while maintaining functionality.

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: Add execution field to dreaming config with fallback model support [1 participants]