openclaw - 💡(How to fix) Fix bug telegran [1 comments, 2 participants]

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

🐛 Bug: extractDeliveryInfo ignores agentId — cross-agent topic routing fails

Description

extractDeliveryInfo() always reads from main/sessions.json regardless of which agent's session key is being queried. This breaks sessions_send between agents when targeting topic-scoped sessions.

Steps to Reproduce

1. Have two agents: main and leonardo
2. Leonardo joins a supergroup topic (e.g. Topic 17)
3. Entry is stored in ~/.openclaw/agents/leonardo/sessions/sessions.json
4. Main tries sessions_send to agent:leonardo:telegram:group:-1003913872387:topic:17
5. extractDeliveryInfo queries main's store — entry not found
6. Delivery fails with "bot not in group" or "Unknown target"

Expected vs Actual

• Expected: deliveryContext resolved correctly from leonardo's store
• Actual: deliveryContext = {channel: null, to: null, threadId: 17} from main store

Environment

• OpenClaw: 2026.5.7
• macOS, node v25.8.2
• Telegram channel with supergroup topics

Root cause (observed)

resolveStorePath() called WITHOUT opts?.agentId → hardcoded to "main"

File: sessions-*.js line ~89

const store = loadSessionStore(resolveStorePath(getRuntimeConfig().session?.store));
// agentId parameter missing — always uses "main"

### Steps to reproduce

resolveStorePath is called WITHOUT opts?.agentId, so it defaults to "main" regardless of the session key's agent prefix.

### Expected behavior

NOT_ENOUGH_INFO.

### Actual behavior

NOT_ENOUGH_INFO.

### OpenClaw version

OpenClaw version: 2026.5.7

### Operating system

macOS Darwin 25.4.0 (ARM64)

### Install method

Node.js v25.8.2

### Model

mini max 2,7

### Provider / routing chain

Channel: Telegram with supergroup topics enabled

### Additional provider/model setup details

_No response_

### Logs, screenshots, and evidence

```shell

Impact and severity

No response

Additional information

No response