CONFIG • OpenClaw Nugget of the Day
Featured: @wangpuv
When onboarding silently changes your tools profile
Sometimes onboarding adds a restrictive tools profile (e.g. messaging-only). Great for safety, confusing when you suddenly can’t read files.
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