Summary

The /reset and /new commands work correctly in direct messages (DMs) but fail to trigger a session reset in group chats. This is a regression - the feature worked correctly on 2026-02-21 but stopped working by 2026-02-25.

Environment

• OpenClaw Version: 2026.2.23
• Previous Working Version: 2026.2.9 (approximate)
• Channel: Feishu
• OS: Ubuntu 22.04.5 LTS
• Node: v22.22.0

Steps to reproduce

Scenario A: Direct Message (Works)

1. Open a DM with the bot
2. Send /reset or /reset @botname
3. Expected: Session closes and new session starts with greeting
4. Actual: Works as expected

Scenario B: Group Chat (Broken )

1. Add bot to a Feishu group chat
2. Send /reset @botname in the group
3. Expected: Bot should start a new session and greet the user
4. Actual: Command is treated as a regular message, no session reset occurs

Expected behavior

Please investigate whether this is an intentional change or a regression. If intentional, please document the new behavior and configuration options. If a regression, please restore the previous behavior where /reset and /new work in group chats.

Actual behavior

When sending /reset in group chat:

• Message is dispatched to existing session instead of triggering reset
• Log shows: dispatch complete (queuedFinal=false, replies=0)
• No "New session started" response
• Subsequent /reset commands are deduplicated: skipping duplicate message om_x100b56xxxxxxxxxxxxxxxxxxxxae7

OpenClaw version

2026.2.23

Operating system

Ubuntu 22.04.5 LTS

Install method

npm

Logs, screenshots, and evidence

### When `/reset` received in group (2026-02-25):

feishu[tiechui]: received message from ou_bddaxxxxxxxxxxxxxxec95875ecf in oc_e3652axxxxxxxxxfb6 (group)
feishu[tiechui]: dispatching to agent (session=agent:main:feishu:group:oc_oc_e3652axxxxxxxxxfb6)
feishu[tiechui]: dispatch complete (queuedFinal=false, replies=0)


### When `/reset` received in DM (works correctly):

feishu[tiechui]: received message from ou_ou_bddaxxxxxxxxxxxxxxec95875ecf (DM)
feishu[tiechui]: dispatching to agent (session=agent:main:main)
[Session reset triggered, new session created]


## Hypothesis

The command routing logic for `/reset` and `/new` may have changed between versions:

1. **DM sessions** (`agent:main:main`): Commands are intercepted and processed before dispatch
2. **Group sessions** (`agent:main:feishu:group:*`): Commands are not being intercepted, instead treated as regular message content

Possible causes:
- Command parsing logic was moved or changed
- Group chat routing takes precedence over command handling
- A new configuration option was introduced that defaults to disabled for groups

Impact and severity

No response

Additional information

• Multiple bots in same group: Each bot should respond to its own @mention
• Use case: Testing multi-agent workflows where each bot needs fresh context