Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

When using multiple Telegram accounts with per-agent bindings, resolveAgentRoute correctly identifies the target agent, but the session key is built using the default agent (main) instead of the resolved agent. This causes the non-default agent to load the wrong workspace, wrong identity files, and wrong session store.

Environment

• OpenClaw version: 2026.3.28 (f9b1079)
• OS: macOS (Apple Silicon, Mac Studio M4 Max)
• Node: 25.8.1
• Install method: npm global (npm install -g openclaw@latest)
• Channel: Telegram (two separate bot accounts)

Configuration

Two Telegram accounts (default and second-ana) with explicit bindings:

{
  agents: {
    list: [
      { id: "main", default: true, workspace: "~/.openclaw/workspace" },
      { id: "second-ana", workspace: "~/.openclaw/workspace-second-ana" }
    ]
  },
  bindings: [
    { agentId: "main", match: { accountId: "default", channel: "telegram", peer: { id: "*", kind: "direct" } } },
    { agentId: "second-ana", match: { accountId: "second-ana", channel: "telegram", peer: { id: "*", kind: "direct" } } }
  ],
  channels: {
    telegram: {
      accounts: {
        default: { botToken: "..." },
        "second-ana": { tokenFile: "..." }
      }
    }
  }
}

Steps to reproduce

1. Configure two Telegram bot accounts with separate agent bindings as shown above
2. Send a direct message to the second-ana bot
3. Observe routing logs and session key

Expected behavior

Routing resolves second-ana → session key should be agent:second-ana:main (or agent:second-ana:telegram:...)

Session file should be stored under ~/.openclaw/agents/second-ana/sessions/

Agent should load workspace ~/.openclaw/workspace-second-ana/ and its IDENTITY.md, SOUL.md, AGENTS.md

Actual behavior

Routing correctly resolves second-ana:

[routing] resolveAgentRoute: channel=telegram accountId=second-ana peer=direct:xxx8131xxx guildId=none teamId=none bindings=2
[routing] binding: agentId=second-ana accountPattern=second-ana peer=direct:* guildId=none teamId=none roles=0

But the session key is built with main:

sessionKey=agent:main:telegram:second-ana:direct:xxx8131xxx
sessionFile=//.openclaw/agents/main/sessions/d04966ce-9060-492f-a315-96002e950fe2.jsonl

The agent stream also shows agent=main:

[ws] → event agent run=... agent=main session=telegram:second-ana:direct:xxx8131xxx stream=lifecycle phase=start

As a result, the second-ana agent loads main's workspace, identity, and system prompt instead of its own.

OpenClaw version

2026.3.28 (f9b1079)

Operating system

macOS (Apple Silicon, Mac Studio M4 Max)

Install method

npm global (npm install -g openclaw@latest)

Model

ollama local

Provider / routing chain

Telegram (two separate bot accounts)

Additional provider/model setup details

What I've Tried

• Deleting the stale session from main's session store → session is immediately recreated under main on next message
• Changing session.dmScope from per-account-channel-peer to per-channel-peer to default → no effect
• Removing session.dmScope entirely → no effect
• Verified openclaw agents list --bindings shows correct routing rules for all agents
• Verified openclaw sandbox explain --agent second-ana resolves correctly
• Verified ~/.openclaw/agents/second-ana/sessions/ exists and is writable (remains empty — sessions never land there)
• Ran openclaw gateway run --verbose to confirm routing vs session key mismatch in real time
• Force-reinstalled openclaw@latest via npm → same version, same behavior

Analysis

The routing subsystem (resolveAgentRoute) works correctly — it matches the binding and identifies second-ana. But somewhere between route resolution and session key construction, the resolved agent ID is lost and the default agent (main) is used instead. The accountId (second-ana) appears in the session key as a path component rather than being used to select the agent prefix.

The session key format agent:main:telegram:second-ana:direct:* suggests the key builder treats second-ana as the Telegram account identifier within the main agent's namespace, rather than routing to a separate agent.

Logs, screenshots, and evidence

## Verbose Log Excerpt


21:20:57 [routing] resolveAgentRoute: channel=telegram accountId=second-ana peer=direct:xxx8131xxx guildId=none teamId=none bindings=2
21:20:57 [routing] binding: agentId=second-ana accountPattern=second-ana peer=direct:* guildId=none teamId=none roles=0
21:20:57 telegram inbound: chatId=xxx8131xxx from=telegram:xxx8131xxx len=92
21:20:57 preflightCompaction check: sessionKey=agent:main:telegram:second-ana:direct:xxx8131xxx
21:20:57 [agent/embedded] embedded run start: provider=ollama model=qwen3.5:35b-a3b-32k
21:20:57 [diagnostic] session state: sessionKey=agent:main:telegram:second-ana:direct:xxx8131xxx
21:20:57 [agent/embedded] [context-diag] pre-prompt: sessionKey=agent:main:telegram:second-ana:direct:xxx8131xxx systemPromptChars=37639 sessionFile=//.openclaw/agents/main/sessions/...
21:20:57 [ws] → event agent agent=main session=telegram:second-ana:direct:xxx8131xxx stream=lifecycle phase=start

Impact and severity

No response

Additional information

No response