openclaw - 💡(How to fix) Fix [Bug]: Active Memory silently skips Telegram DM sessions due to unrecognized thread session key format [1 participants]

[Bug]: Active Memory silently skips Telegram DM sessions due to unrecognized thread session key format

Bug Description

The Active Memory plugin silently skips all Telegram DM sessions when topic-based threading is enabled. No memory is ever injected, no transcripts are persisted, and no errors or warnings appear in the gateway log. The plugin loads successfully and shows as loaded in the plugin table, but never actually executes the blocking memory sub-agent for Telegram sessions.

Root Cause

The resolveChatType() function in extensions/active-memory/index.js cannot classify Telegram thread-format session keys.

Telegram DMs with topic threading produce session keys like:

agent:main:main:thread:{chatId}:{topicId}

The function checks for these patterns (lines ~462-478):

1. :group: — no match
2. :channel: — no match
3. :direct: or :dm: — no match
4. 3-part agent session (agent:{name}:{key}) — fails because the key has 6 parts
5. webchat provider — no match (we're telegram)

When no pattern matches, resolveChatType() returns undefined. This causes:

• isAllowedChatType() → returns false (line ~484)
• Active memory silently skips (line ~1195), with zero log output

The Telegram thread session key format was intentionally introduced in PR #1597 (tracked in #7352) for topic-aware Telegram DMs, but the active-memory plugin was never updated to recognize it.

Evidence

Session key: agent:main:main:thread:488228716:531403

Gateway log: Plugin loads successfully:

ready (5 plugins: acpx, active-memory, memory-core, memory-wiki, telegram; 15.1s)
active-memory: loaded (stock:active-memory/index.js)

Gateway log: Zero active-memory runtime execution. No "blocking memory sub-agent", no "active-memory returned NONE", no timeout, no error. Complete silence on every turn.

Source code trace:

• resolveChatType("agent:main:main:thread:488228716:531403") → undefined
• isAllowedChatType() → false (line ~484: if (!chatType) return false)
• Guard at line ~1195 skips the session immediately

Config (validated with openclaw config validate):

"active-memory": {
  "enabled": true,
  "config": {
    "agents": ["main"],
    "allowedChatTypes": ["direct", "group"],
    "queryMode": "full",
    "promptStyle": "contextual",
    "timeoutMs": 25000,
    "maxSummaryChars": 600,
    "logging": true,
    "persistTranscripts": true,
    "transcriptDir": "active-memory"
  }
}

Reproduction Steps

1. Configure OpenClaw with Telegram channel and allowedChatTypes: ["direct"]
2. Send a DM to the Telegram bot (with topics enabled, which creates thread-format session keys)
3. Observe the session key format: agent:main:main:thread:{chatId}:{topicId}
4. Send messages that should trigger memory recall
5. Check gateway logs — zero active-memory activity
6. Check transcript directory — empty

Related Issues

• #65159 — Same symptom (configured and loaded but not triggering), reported for Discord DM. Reporter suspects "chat type mismatch" but hasn't identified root cause.
• #65775 — allowedChatTypes silently strips "explicit" sessions. Same pattern of resolveChatType dropping unrecognized types.
• #65517 — Active-memory blocks event loop and starves Telegram polling (separate but related Telegram interaction).
• #7352 — Documents the thread-format session key as intentional behavior for Telegram DM topics.

Proposed Fix

Add :thread: pattern recognition to resolveChatType(). Telegram thread sessions should resolve to "direct" since they are direct messages with topic threading enabled.

Suggested addition to the session key pattern checks:

// After existing :group: / :channel: / :direct: / :dm: checks
if (sessionKey.includes(":thread:")) return "direct";

Alternatively, for a more robust fix that handles future session key formats: if the provider is known and the channel is non-empty, but no specific pattern matched, fall back to "direct" rather than returning undefined. This ensures new session key formats don't silently break active memory.

Environment

• OpenClaw: 2026.4.21
• Channel: Telegram (bot: @LovingKyprisBot)
• Active Memory: enabled, queryMode: full, promptStyle: contextual
• OS: Linux 6.17.12-300.fc43.x86_64 (Fedora)