Troubleshooting
Bot Not Responding
- Check the token —
grep BOT_TOKEN .envshould show your token - Check channel registered —
sqlite3 store/messages.db "SELECT * FROM registered_groups" - Check service running —
launchctl list | grep nanoclaw - Check logs —
tail -f logs/actioner.log - For non-main channels — messages must start with
@Actioner
Bot Responds to @mentions Only
Default for non-main channels. To change:
- Register the channel as main (
--is-main --no-trigger-required) - Or set
requiresTrigger: falseon the group
Discord: Can't Read Messages
Enable Message Content Intent:
- Discord Developer Portal > your app > Bot tab
- Under Privileged Gateway Intents, enable Message Content Intent
- Restart

Research Not Returning Results
- Check container —
docker psshould show a running container - Check summaries —
ls groups/global/summaries/ - Check container tools —
docker run --rm --entrypoint bash nanoclaw-agent:latest -c 'sigma --version'
Detection Rules Failing Validation
Validation runs inside the container. Check:
bash
docker run --rm --entrypoint bash nanoclaw-agent:latest -c 'sigma --version && yarac --help | head -1'If tools are missing, rebuild: cd container && bash build.sh
Duplicate Bot Responses
Usually means two processes are running. Check:
bash
ps aux | grep 'node.*dist/index'Kill duplicates. Only one should be running.
Can't Get Channel ID (Discord)
- User Settings > Advanced > Enable Developer Mode
- Right-click the channel name in the sidebar
- Click Copy Channel ID