openclaw - 💡(How to fix) Fix [Bug]: Missing daily memory file read logs ENOENT noise [1 pull requests]

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Reading an optional first-run daily memory file before it exists emits a scary read failed: ENOENT tool error and raw params in logs.

Steps to reproduce

1. Run an agent/tool flow that attempts to read a date-only daily memory file before that file has been created.
2. The read tool receives a path shaped like memory/2026-05-15.md.
3. Observe the tool failure log showing read failed: ENOENT for the missing workspace memory file.

Expected behavior

Missing date-only daily memory files are optional first-run state, so reading one before it exists should return quiet not-found context instead of logging a generic tool failure.

Actual behavior

The read tool failure is logged as read failed: ENOENT, including raw read params, even though the missing daily memory file is harmless optional state.

OpenClaw version

NOT_ENOUGH_INFO

Operating system

NOT_ENOUGH_INFO

Install method

NOT_ENOUGH_INFO

Model

NOT_ENOUGH_INFO

Provider / routing chain

NOT_ENOUGH_INFO

Additional provider/model setup details

NOT_ENOUGH_INFO

Logs, screenshots, and evidence

Trace/proof:
- gateway-dev.log:1632
  "[tools] read failed: ENOENT: no such file or directory, access '[redacted workspace path]/memory/2026-05-15.md' raw_params={\"path\":\"memory/2026-05-15.md\"}"

Impact and severity

Affected: Agent/tool flows that try to read daily memory before the file exists. Severity: Low; the failure is usually harmless but pollutes logs and can confuse the agent or user. Frequency: 7 observed lines matching read failed: ENOENT in the captured evidence. Consequence: Optional first-run memory state appears as a failed tool read.

Additional information

No existing issue or PR was found with live GitHub searches for missing daily memory ENOENT read failed or memory/2026 ENOENT.