CONFIG • OpenClaw quick fix
Featured: @wangpuv
Agent suddenly can’t read files
File access often breaks when onboarding switches tools.profile to a restrictive mode such as messaging-only.
In simple words: Make a safe copy if the step could change your setup, try the smallest check, then confirm OpenClaw is back to normal before doing more. The source link and commands stay below for people who want the technical detail.
Checklist
Inspect openclaw.json: does tools.profile exist and is it too restrictive?
Run a tiny file-read test (known file) to confirm tool access end-to-end.
Restart the gateway and re-test — many ‘it’s broken’ states are stale runtime state.
Success looks like
• You should be able to read a known file and see its contents in the response.
• After restarting, gateway/tool access should behave consistently across runs (no intermittent denial).
Source: X post · link