openclaw - 💡(How to fix) Fix Proposal: make resumed session model selection configurable [1 participants]

Official PRs (…)
ON THIS PAGE

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#59750Fetched 2026-04-08 02:40:59
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Participants

Code Example

{
  "model": {
    "resumeStrategy": "session"
  }
}
RAW_BUFFERClick to expand / collapse

Hi, I’d like to suggest a small improvement to model selection for resumed sessions.

Right now, resumed sessions seem to restore the previously saved session model. That is reasonable for continuity, but it can be surprising when the configured default_model is different.

For example:

  • default_model = DeepSeek V3.2
  • resumed session model = DeepArk

Would it make sense to add a setting like:

{
  "model": {
    "resumeStrategy": "session"
  }
}

with values:

  • "session" = keep current behavior, restore saved session model
  • "default" = ignore saved session model on resume and use current default_model

This would preserve backward compatibility while giving users explicit control over whether resumed sessions prioritize continuity or current defaults.

Thanks for considering it.

extent analysis

TL;DR

Adding a resumeStrategy setting to the model configuration can help users control whether resumed sessions prioritize continuity or current defaults.

Guidance

  • Consider introducing a new configuration option resumeStrategy with values "session" and "default" to control the model selection behavior for resumed sessions.
  • Evaluate the impact of changing the default behavior on existing users and decide whether to maintain backward compatibility.
  • Discuss the proposed solution with the development team to ensure it aligns with the project's goals and design principles.
  • Test the new configuration option with different scenarios to ensure it works as expected.

Example

{
  "model": {
    "resumeStrategy": "default"
  }
}

This example shows how the new configuration option could be used to prioritize the current default_model over the saved session model.

Notes

The proposed solution assumes that the default_model is configured separately and that the resumeStrategy setting only affects the model selection for resumed sessions.

Recommendation

Apply workaround by introducing the proposed resumeStrategy setting, as it provides a flexible solution that balances continuity and user control.

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