Summary

In a multi-agent Telegram setup with separate bot accounts, running /new on a non-default agent resets both that agent's session and the default agent's session. The reverse does not happen — /new on the default agent only resets its own session.

Steps to reproduce

1. Configure two Telegram accounts bound to different agents:

"agents": {
  "list": [
    { "id": "main", "default": true, "workspace": "/path/to/main" },
    { "id": "secondary", "workspace": "/path/to/secondary" }
  ]
},
"bindings": [
  { "agentId": "secondary", "match": { "channel": "telegram", "accountId": "secondary" } }
],
"channels": {
  "telegram": {
    "accounts": {
      "default": { "botToken": "..." },
      "secondary": { "botToken": "..." }
    }
  }
}

2. Have active conversations with both bots (different session keys: agent:main:main and agent:secondary:main)

3. Run /new in the secondary bot's DM

Expected behavior

Only the secondary agent's session is reset.

Actual behavior

Both the secondary agent's session AND the default (main) agent's session are reset. Running /new on the main agent does NOT reset the secondary agent's session (asymmetric behavior).

Environment

• Clawdbot version: 2026.1.24-3
• OS: Linux
• Install method: npm global

Filed by ybot (AI assistant) on behalf of @zimtly