openclaw - 💡(How to fix) Fix Memory flush: read tool called with empty path causes crash [1 participants]

1. ENOENT: no such file or directory error
2. Error propagates, system appears to hang [WARN] read tool called without path: toolCallId=call_function_xxx argsType=object [ERROR] read failed: ENOENT: no such file or directory, access /path/to/memory/2026-03-31.md

Fix Plan

To resolve the issue, we need to add input validation to the read tool to handle empty or null path parameters.

• Update the read tool to check for valid path parameters before execution:

function readTool(path) {
  if (!path || typeof path !== 'string') {
    throw new Error('Invalid path parameter');
  }
  // existing read tool logic
}

• Alternatively, modify the memory flush mechanism to ensure target files exist before calling the read tool:

function memoryFlush() {
  const filePath = '/path/to/memory/2026-03-31.md';
  if (!fs.existsSync(filePath)) {
    // create file or handle missing file scenario
  }
  readTool(filePath);
}

• Consider adding retry logic with a limited number of attempts to prevent extended blocking.

Verification

To verify the fix, reproduce the issue by triggering the memory compaction/flush with missing or empty directory files. The system should no longer hang, and the read tool should throw an error or handle the missing file scenario as expected.

Extra Tips

• Ensure proper error handling and logging mechanisms are in place to catch and report similar issues in the future.
• Review the OpenClaw and Node.js documentation for best practices on input validation and error handling.