#Validation error: A conversation must start with a user message. Try again with a conversation that
1 messages · Page 1 of 1 (latest)
That smells like a bare /new regression in 2026.4.26, not a Slack scopes/config issue.
Quick workaround: try sending the reset with a first real user prompt, e.g.
/new hi
or
/new continue from here
instead of a bare /new. That should make the new conversation start with a user-visible message.
Can you paste:
openclaw --version
openclaw status --all
and the relevant log tail around the failed Slack DM? Also mention which model/provider you’re using — especially if it’s Bedrock/Anthropic.
Docs for the normal triage path: https://docs.openclaw.ai/help/faq and https://docs.openclaw.ai/gateway/troubleshooting. If this repros cleanly on exact 2026.4.26, it’s worth filing with those details: https://github.com/openclaw/openclaw/issues
yea that works
Nice — that confirms it’s specifically the bare /new path.
For now, use:
/new hi
or any actual prompt after /new.
Please file this as a regression with:
- exact
openclaw --version - Slack DM to agent
- bare
/newfails /new hiworks- log tail around the failure