openclaw - 💡(How to fix) Fix Bug: Config hot-reload silently drops per-agent workspace field

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…

Error Message

  • No warning or error — silent data loss
RAW_BUFFERClick to expand / collapse

Problem

When a config change triggers a hot-reload, the gateway rewrites agents.list without preserving the per-agent workspace field. This silently breaks multi-agent setups.

Reproduction

  1. Configure two agents with distinct workspaces: main → "/.openclaw/workspace" ubh → "/projets/ubh" rail → "~/projets/rail-pk-overlay"

  2. Trigger a hot-reload (e.g. change agents.defaults.model.primary)

  3. Gateway logs show agents.list was rewritten: [reload] config hot reload applied (agents.defaults.model.primary, ...)

  4. Per-agent workspaces are now gone: { id: "ubh" } // workspace dropped silently { id: "rail-pk" } // workspace dropped silently

Impact

  • Agents load wrong AGENTS.md/SOUL.md/USER.md (identity confusion)
  • No warning or error — silent data loss

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