openclaw - 💡(How to fix) Fix [Bug]: files in ../workspace not used/read

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…

Hello everyone,

I've been working with local AI models for a while now and eventually came across OpenCLAW. The early versions were completely restriction-free. I could simply write "install language support" in the Telegram chat, and 10 minutes later, OpenCLAW understood the language via Telegram.

After reinstalling OpenCLAW a month ago, many more restrictions were implemented into the system, so OpenCLAW can no longer access files by default or execute code, etc. Is this due to the OpenCLAW version or does the LLM lack fundamental tools?

For example, trying to read almost every file in $OSROOTDIR/workspaces doesn't trigger any response from OpenCLAW.

There are also inconsistencies with the filenames: different models create various files - sometimes memory.txt, whereas the actual "memory file" is MEMORY.md. The same applies to USER.md and other MD files.

System Information:

  • Operating System: Debian 13
  • OpenCLAW version: v2026.5.12

Root Cause

Hello everyone,

I've been working with local AI models for a while now and eventually came across OpenCLAW. The early versions were completely restriction-free. I could simply write "install language support" in the Telegram chat, and 10 minutes later, OpenCLAW understood the language via Telegram.

After reinstalling OpenCLAW a month ago, many more restrictions were implemented into the system, so OpenCLAW can no longer access files by default or execute code, etc. Is this due to the OpenCLAW version or does the LLM lack fundamental tools?

For example, trying to read almost every file in $OSROOTDIR/workspaces doesn't trigger any response from OpenCLAW.

There are also inconsistencies with the filenames: different models create various files - sometimes memory.txt, whereas the actual "memory file" is MEMORY.md. The same applies to USER.md and other MD files.

System Information:

  • Operating System: Debian 13
  • OpenCLAW version: v2026.5.12
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Hello everyone,

I've been working with local AI models for a while now and eventually came across OpenCLAW. The early versions were completely restriction-free. I could simply write "install language support" in the Telegram chat, and 10 minutes later, OpenCLAW understood the language via Telegram.

After reinstalling OpenCLAW a month ago, many more restrictions were implemented into the system, so OpenCLAW can no longer access files by default or execute code, etc. Is this due to the OpenCLAW version or does the LLM lack fundamental tools?

For example, trying to read almost every file in $OSROOTDIR/workspaces doesn't trigger any response from OpenCLAW.

There are also inconsistencies with the filenames: different models create various files - sometimes memory.txt, whereas the actual "memory file" is MEMORY.md. The same applies to USER.md and other MD files.

System Information:

  • Operating System: Debian 13
  • OpenCLAW version: v2026.5.12

Steps to reproduce

I dont know if other installation ignore memoryfiles too ?!

Expected behavior

Openclaw from Jan 2026 worked

Actual behavior

No memory file was read when starting a chat or any request

OpenClaw version

v2026.5.12

Operating system

Debain 13

Install method

Script from Website

Model

various, qwem3:8B, in|excluding K and M versions, all gemma4 models and others

Provider / routing chain

own ollama server on RTX2060 8GB VRAM, 64GB RAM

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

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…

FAQ

Expected behavior

Openclaw from Jan 2026 worked

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: files in ../workspace not used/read