2026-04-30T11:26:50.187Z error [tools] read failed: ENOENT: no such file or directory, access '/root/workspace/ skills/ openclaw- cybersecurity- skills/ CONVERSION_ Rules. md' raw_ params={"path":"/root/workspace/ skills/ openclaw- cybersecurity- skills/ CONVERSION_ Rules. md"} 2026-04-30T11:26:50.202Z error [tools] read failed: ENOENT: no such file or directory, access '/root/workspace/ skills/ openclaw- cybersecurity- skills/ CONVERSION_ LIST. md' raw_ params={"path":"/root/workspace/ skills/ openclaw- cybersecurity- skills/ CONVERSION_ LIST. md"} 2026-04-30T11:30:13.135Z error [tools] read failed: ENOENT: no such file or directory, access '/root/workspace/ skills/ Anthropic- Cybersecurity- Skills/ skills/ building- threat- hunt- hypothesis- framework/ SKILL. md' raw_ params={"path":"/root/workspace/ skills/ Anthropic- Cybersecurity- Skills/ skills/ building- threat- hunt- hypothesis- framework/ SKILL. md"} 2026-04-30T11:30:21.009Z error [tools] read failed: ENOENT: no such file or directory, access '/root/workspace/ skills/ Anthropic- Cybersecurity- Skills/ skills/ building- threat- hunt- hypothesis- framework/ SKILL. md' raw_ params={"path":"/root/workspace/ skills/ Anthropic- Cybersecurity- Skills/ skills/ building- threat- hunt- hypothesis- framework/ SKILL.

TL;DR

The issue can be fixed by properly encoding or escaping the / character in file paths before compression to prevent it from being converted to a space.

Guidance

• Review the conversation context compression logic to identify where the / character is being replaced with a space and modify it to preserve the original path.
• Consider using URL encoding or a similar mechanism to escape special characters like / in file paths before compression.
• Verify that the tool calls receiving the compressed paths can handle the escaped or encoded characters correctly.
• Test the fix with various file paths containing / characters to ensure the issue is fully resolved.

Example

No specific code snippet can be provided without knowing the exact implementation details, but an example of URL encoding in JavaScript could be: const encodedPath = encodeURIComponent('/root/workspace/skills/');

Notes

The provided logs indicate that the issue is causing ENOENT errors due to the corrupted file paths, which suggests that the fix should focus on preserving the original path characters during compression.

Recommendation

Apply a workaround by encoding or escaping the / character in file paths before compression, as upgrading to a fixed version is not mentioned as an option in the issue.