Summary

Nextcloud Talk (and potentially other chat platforms) intercepts input
beginning with / as its own internal commands. This means the standard
OpenClaw slash-command mechanism (/new, /reset, /status, etc.) is
completely non-functional in Nextcloud Talk channels — the commands never
reach the bot at all.

Disabling commands.text allows text-based workarounds for most commands
(e.g. typing "status" without slash), but there is still no way to reset
a single session's context without restarting the entire Gateway.

Problem to solve

Add a CLI command or gateway RPC method to reset a specific session:

openclaw sessions reset --key "agent:main:nextcloud-talk:group:xxx"

or

openclaw gateway call session.reset '{"sessionKey": "..."}'

Proposed solution

• /new and /reset are intercepted by Nextcloud Talk before reaching OpenClaw
• openclaw gateway restart resets ALL sessions — disruptive in multi-user setups
• Users on affected channels have no way to clear their own context

Current state

• openclaw sessions → ✅ lists sessions
• openclaw sessions cleanup → ✅ maintenance
• openclaw sessions reset → ❌ missing
• openclaw gateway call session.* → ❌ no session management RPCs

Alternatives considered

No response

Impact

Affected channels

• Nextcloud Talk (confirmed)
• Potentially Matrix and other platforms with similar slash-command handling

Evidence/examples

No response

Additional information

No response