openclaw - 💡(How to fix) Fix Dreaming light phase should ingest workspace file creation events, not just memory/*.md

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…

The dreaming light phase only ingests from memory/*.md daily notes and session transcripts. It does not detect or ingest workspace file creation events (e.g., new scripts in tools/, new config files, new data files).

Root Cause

When an agent builds a tool during a session (e.g., creates tools/scanner.py), that knowledge lives only in the session transcript. After compaction, the agent loses awareness of the tool because:

Fix Action

Workaround

We added a "compound learning" rule to agent constitutions requiring them to manually register new tools in a capabilities.db SQLite database. This works but depends on the agent following the rule.

RAW_BUFFERClick to expand / collapse

Summary

The dreaming light phase only ingests from memory/*.md daily notes and session transcripts. It does not detect or ingest workspace file creation events (e.g., new scripts in tools/, new config files, new data files).

Impact

When an agent builds a tool during a session (e.g., creates tools/scanner.py), that knowledge lives only in the session transcript. After compaction, the agent loses awareness of the tool because:

  1. Dreaming never ingests "new file created" as a signal
  2. The tool's existence is never a promotion candidate
  3. memory_search can find it in transcripts, but only if the agent knows to search for it

This creates a chicken-and-egg problem: agents can't search for capabilities they don't know they forgot.

Suggested Approach

The light phase could watch for new files in configurable workspace paths (e.g., tools/, scripts/) and ingest file creation events as short-term signals. These would then be eligible for deep phase promotion into MEMORY.md.

Alternatively, a workspace.watchPaths config could feed file-change events into the recall store with a baseline score.

Workaround

We added a "compound learning" rule to agent constitutions requiring them to manually register new tools in a capabilities.db SQLite database. This works but depends on the agent following the rule.

Environment

  • OpenClaw 2026.5.22
  • 9 agents, some with 150+ scripts in tools/ that are invisible to memory

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