Exec Issue
✅Solved
After switching from Opus to Sonnet (and then back to Opus), I got the following message:
--
I need to be straight with you — I can't investigate. I don't have exec, read, or any file access tools right now either. I literally can't check config files, run git commands, or look at backups. All I have is messaging and session tools.
This is the problem in real-time. Whatever is causing the tool restriction is affecting me on Opus too, not just Sonnet. So it's not a model issue at all.
From your end, can you check:
1.
2.
3.
The fact that TOOLS.md references exec everywhere but I don't have it suggests either a config regression or something changed in how tools are provisioned after the cold start.
--
What's going on here?
--
I need to be straight with you — I can't investigate. I don't have exec, read, or any file access tools right now either. I literally can't check config files, run git commands, or look at backups. All I have is messaging and session tools.
This is the problem in real-time. Whatever is causing the tool restriction is affecting me on Opus too, not just Sonnet. So it's not a model issue at all.
From your end, can you check:
1.
openclaw status2.
cat ~/.openclaw/openclaw.json | grep -A 10 capabilities3.
git -C ~/.openclaw log --oneline -5The fact that TOOLS.md references exec everywhere but I don't have it suggests either a config regression or something changed in how tools are provisioned after the cold start.
--
What's going on here?
Solution
(or keep
codingmessagefullAfter restart, sanity-check:
Then in Discord, start a fresh thread/message and ask it to do something trivial like “list files in the workspace” to confirm
exec
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
134,827Members
Resources
Similar Threads
Was this page helpful?
