Telegram: fix named-account DM topic session keys by vincentkoc · Pull Request #48773 · openclaw/openclaw

vincentkoc · 2026-03-17T06:11:44Z

Summary

Problem: Telegram named-account DM topics could route normal messages to the per-account session while native /status still targeted agent:main:main:thread:..., creating a phantom empty session.
Why it matters: /status would show 0 usage/context for a live thread even when the real session had token data.
What changed: extracted a shared Telegram base-session-key resolver and used it in inbound message context building, native command routing, and Telegram session-state lookup.
What did NOT change (scope boundary): no session-store migration, no cross-channel routing changes, no changes to default-account Telegram DM behavior.

Change Type (select all)

Scope (select all touched areas)

Linked Issue/PR

User-visible / Behavior Changes

Telegram named-account DM topics now resolve /status and related session lookups against the same canonical session key as inbound message handling.
This avoids phantom agent:main:main:thread:... sessions winning over the real per-account Telegram session.

Security Impact (required)

New permissions/capabilities? (Yes/No) No
Secrets/tokens handling changed? (Yes/No) No
New/changed network calls? (Yes/No) No
Command/tool execution surface changed? (Yes/No) No
Data access scope changed? (Yes/No) No
If any Yes, explain risk + mitigation:

Repro + Verification

Environment

OS: macOS
Runtime/container: Node 22 / Vitest channel config
Model/provider: N/A
Integration/channel (if any): Telegram
Relevant config (redacted): non-default Telegram account DM fallback with DM topics

Steps

Configure a non-default Telegram account without an explicit DM binding.
Use a Telegram DM topic so inbound traffic lands on a thread session.
Run /status in that topic.

Expected

/status resolves the same canonical per-account Telegram thread session used by normal inbound message handling.

Actual

Before this change, native command routing could target agent:main:main:thread:... while normal traffic used agent:main:telegram:<account>:direct:...:thread:....

Evidence

Failing test/log before + passing after
Trace/log snippets
Screenshot/recording
Perf numbers (if relevant)

Human Verification (required)

What you personally verified (not just CI), and how:

Verified scenarios: named-account DM fallback key selection, DM topic thread suffixing, existing named-account DM message-context coverage.
Edge cases checked: default account still keeps agent:main:main; named-account group traffic still does not use the DM fallback path.
What you did not verify: full GitHub CI matrix and live Telegram roundtrip against a real bot.

Review Conversations

I replied to or resolved every bot review conversation I addressed in this PR.
I left unresolved only the conversations that still need reviewer or maintainer judgment.

If a bot review conversation is addressed by this PR, resolve that conversation yourself. Do not leave bot review conversation cleanup for maintainers.

Compatibility / Migration

Backward compatible? (Yes/No) Yes
Config/env changes? (Yes/No) No
Migration needed? (Yes/No) No
If yes, exact upgrade steps:

Failure Recovery (if this breaks)

How to disable/revert this change quickly: revert this PR or restore the previous route.sessionKey call sites in Telegram routing.
Files/config to restore: extensions/telegram/src/conversation-route.ts, extensions/telegram/src/bot-message-context.ts, extensions/telegram/src/bot-native-commands.ts, extensions/telegram/src/bot-handlers.ts
Known bad symptoms reviewers should watch for: Telegram named-account DM topics resolving to the wrong session key again, or default-account DMs unexpectedly leaving agent:main:main.

Risks and Mitigations

Risk: another Telegram code path may still read route.sessionKey directly when it should use the normalized named-account DM base key.
- Mitigation: centralize the fallback logic in resolveTelegramConversationBaseSessionKey and add targeted regression coverage for the helper and message-context path.

greptile-apps · 2026-03-17T07:45:39Z

Greptile Summary

This PR fixes a session-key mismatch for Telegram named-account DM topics by extracting a shared resolveTelegramConversationBaseSessionKey helper in conversation-route.ts and using it consistently across bot-message-context.ts, bot-native-commands.ts (/status), and the resolveTelegramSessionState lookup in bot-handlers.ts. Previously, native commands like /status fell back to the raw route.sessionKey (agent:main:main), creating a phantom empty session while actual inbound traffic ran on agent:main:telegram:<account>:direct:<chatId>.

Key changes:

New resolveTelegramConversationBaseSessionKey helper centralizes the named-account DM fallback logic (accountId !== DEFAULT_ACCOUNT_ID && matchedBy === "default" + not a group → build per-account dmScope: "per-account-channel-peer" key).
bot-message-context.ts drops the 22-line inline equivalent and uses the new helper; unused imports (buildAgentSessionKey, resolveTelegramDirectPeerId) are cleaned up.
/status command path and session-state lookup are aligned with the inbound message session key.
Test mock in bot-message-context.named-account-dm.test.ts is improved: the old mock replaced the entire "../../../src/channels/session.js" module; the new one spreads actual from "openclaw/plugin-sdk/channel-runtime" and only overrides recordInboundSession.
Two new test suites cover the helper in isolation and the message-context named-account path end-to-end.

Known remaining gaps (acknowledged in PR risk section):

The Telegram reaction handler (bot-handlers.ts:875) still uses resolveAgentRoute + route.sessionKey directly without senderId, so reaction system events will still target the wrong session for named-account DMs.
The plugin-command handler in bot-native-commands.ts:861 passes sessionKeyForInternalHooks: route.sessionKey (raw), which may record hook events on the wrong session for named-account DMs. Both are reasonable candidates for a follow-up PR.

Confidence Score: 4/5

Safe to merge; the targeted fix is correct and well-tested, with two acknowledged residual code paths left for follow-up.
The core fix (extracting and using resolveTelegramConversationBaseSessionKey) is logically sound and directly mirrors the old inline logic. Tests cover the helper in isolation, the message-context path end-to-end, DM topic thread suffixing, identity-link canonicalization, and cross-account isolation. The score stops at 4 rather than 5 because two call sites in bot-handlers.ts (reaction handler) and bot-native-commands.ts (plugin-command sessionKeyForInternalHooks) still read route.sessionKey directly and were deliberately left out of this PR's scope — the PR itself notes this risk.
extensions/telegram/src/bot-handlers.ts (reaction handler at line 875) and extensions/telegram/src/bot-native-commands.ts (plugin-command path at line 861) both contain residual route.sessionKey usages that could still produce incorrect session routing for named-account DMs.

Comments Outside Diff (2)

extensions/telegram/src/bot-handlers.ts, line 875 (link)

Residual raw route.sessionKey in reaction handler

This reaction handler still reads route.sessionKey directly and also uses resolveAgentRoute (rather than resolveTelegramConversationRoute), so it will route system events to agent:main:main instead of agent:main:telegram:<account>:direct:<chatId> when a named-account DM receives a reaction.

The PR's own risk section calls out: "another Telegram code path may still read route.sessionKey directly" — this line is exactly that case. The reaction handler doesn't have a senderId available from the reaction update, so migrating it requires a small refactor (use resolveTelegramConversationRoute with senderId obtained from the reaction's user field, then call resolveTelegramConversationBaseSessionKey).

This is intentionally out of scope for the current PR, but worth a follow-up ticket to keep the pattern consistent across all Telegram event handlers.

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/telegram/src/bot-handlers.ts
Line: 875

Comment:
**Residual raw `route.sessionKey` in reaction handler**

This reaction handler still reads `route.sessionKey` directly and also uses `resolveAgentRoute` (rather than `resolveTelegramConversationRoute`), so it will route system events to `agent:main:main` instead of `agent:main:telegram:<account>:direct:<chatId>` when a named-account DM receives a reaction.

The PR's own risk section calls out: _"another Telegram code path may still read `route.sessionKey` directly"_ — this line is exactly that case. The reaction handler doesn't have a `senderId` available from the reaction update, so migrating it requires a small refactor (use `resolveTelegramConversationRoute` with `senderId` obtained from the reaction's `user` field, then call `resolveTelegramConversationBaseSessionKey`).

This is intentionally out of scope for the current PR, but worth a follow-up ticket to keep the pattern consistent across all Telegram event handlers.

How can I resolve this? If you propose a fix, please make it concise.

extensions/telegram/src/bot-native-commands.ts, line 861 (link)

sessionKeyForInternalHooks still uses raw route.sessionKey

For plugin command execution, sessionKeyForInternalHooks is set to the raw route.sessionKey rather than the normalized base session key from resolveTelegramConversationBaseSessionKey. For a named-account DM topic, this will point at agent:main:main instead of the correct per-account session key.

The surrounding /status command path (line 656) was fixed in this PR; the plugin-command path just above was not. Depending on what sessionKeyForInternalHooks gates (e.g. hook recording, sub-agent announce routing), this may silently accumulate events on the wrong session.

Consider applying the same resolveTelegramConversationBaseSessionKey call here, or tracking this as a follow-up alongside the reaction-handler gap noted above.

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/telegram/src/bot-native-commands.ts
Line: 861

Comment:
**`sessionKeyForInternalHooks` still uses raw `route.sessionKey`**

For plugin command execution, `sessionKeyForInternalHooks` is set to the raw `route.sessionKey` rather than the normalized base session key from `resolveTelegramConversationBaseSessionKey`. For a named-account DM topic, this will point at `agent:main:main` instead of the correct per-account session key.

The surrounding `/status` command path (line 656) was fixed in this PR; the plugin-command path just above was not. Depending on what `sessionKeyForInternalHooks` gates (e.g. hook recording, sub-agent announce routing), this may silently accumulate events on the wrong session.

Consider applying the same `resolveTelegramConversationBaseSessionKey` call here, or tracking this as a follow-up alongside the reaction-handler gap noted above.

How can I resolve this? If you propose a fix, please make it concise.

Prompt To Fix All With AI

This is a comment left during a code review.
Path: extensions/telegram/src/bot-handlers.ts
Line: 875

Comment:
**Residual raw `route.sessionKey` in reaction handler**

This reaction handler still reads `route.sessionKey` directly and also uses `resolveAgentRoute` (rather than `resolveTelegramConversationRoute`), so it will route system events to `agent:main:main` instead of `agent:main:telegram:<account>:direct:<chatId>` when a named-account DM receives a reaction.

The PR's own risk section calls out: _"another Telegram code path may still read `route.sessionKey` directly"_ — this line is exactly that case. The reaction handler doesn't have a `senderId` available from the reaction update, so migrating it requires a small refactor (use `resolveTelegramConversationRoute` with `senderId` obtained from the reaction's `user` field, then call `resolveTelegramConversationBaseSessionKey`).

This is intentionally out of scope for the current PR, but worth a follow-up ticket to keep the pattern consistent across all Telegram event handlers.

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: extensions/telegram/src/bot-native-commands.ts
Line: 861

Comment:
**`sessionKeyForInternalHooks` still uses raw `route.sessionKey`**

For plugin command execution, `sessionKeyForInternalHooks` is set to the raw `route.sessionKey` rather than the normalized base session key from `resolveTelegramConversationBaseSessionKey`. For a named-account DM topic, this will point at `agent:main:main` instead of the correct per-account session key.

The surrounding `/status` command path (line 656) was fixed in this PR; the plugin-command path just above was not. Depending on what `sessionKeyForInternalHooks` gates (e.g. hook recording, sub-agent announce routing), this may silently accumulate events on the wrong session.

Consider applying the same `resolveTelegramConversationBaseSessionKey` call here, or tracking this as a follow-up alongside the reaction-handler gap noted above.

How can I resolve this? If you propose a fix, please make it concise.

_{Last reviewed commit: 1a02e13}

(cherry picked from commit 1eb810a)

@scoootscooob

* refactor(slack): share setup wizard base * refactor(discord): share setup wizard base * refactor(signal): reuse shared setup security * refactor(imessage): reuse shared setup security * refactor(setup): reuse patched adapters across channels * refactor(imessage): share setup status base * refactor(slack): share token credential setup * refactor(setup): share env-aware patched adapters * refactor(discord): use shared plugin base * refactor(outbound): share base session helpers * refactor(whatsapp): reuse login tool implementation * refactor(providers): reuse simple api-key catalog helper * refactor(plugins): share bundle path list helpers * refactor(slack): reuse shared action adapter * refactor(tts): share provider readiness checks * refactor(plugins): share claiming hook loop * refactor(plugins): share install target flow * refactor(status): share scan helper state * refactor(usage): share legacy pi auth token lookup * refactor(device): share missing-scope helper * refactor(config): share schema lookup helpers * fix(plugin-sdk): restore core export boundary * build: tighten lazy runtime boundaries * fix(gateway): surface env override keys in exec approvals * Agents: move bootstrap warnings out of system prompt (openclaw#48753) Merged via squash. Prepared head SHA: dc1d4d0 Co-authored-by: scoootscooob <167050519+scoootscooob@users.noreply.github.com> Reviewed-by: @scoootscooob * refactor: dedupe channel entrypoints and test bridges * style: fix rebase formatting drift * fix: resolve rebase type fallout in channel setup seams * fix(macos): block canvas symlink escapes * refactor: bundle lazy runtime surfaces * fix: remove discord setup rebase marker * docs(gateway): clarify URL allowlist semantics * docs(changelog): restore 2026.2.27 heading * fix: unblock full gate * fix: stabilize full gate * test: cover invalid main job store load * build(test): ignore vitest scratch root * refactor: dedupe bundled plugin entrypoints * docs: add context engine documentation Add dedicated docs page for the pluggable context engine system: - Full lifecycle explanation (ingest, assemble, compact, afterTurn) - Legacy engine behavior documentation - Plugin engine authoring guide with code examples - ContextEngine interface reference table - ownsCompaction semantics - Subagent lifecycle hooks (prepareSubagentSpawn, onSubagentEnded) - systemPromptAddition mechanism - Relationship to compaction, memory plugins, and session pruning - Configuration reference and tips Also: - Add context-engine to docs nav (Agents > Fundamentals, after Context) - Add /context-engine redirect - Cross-link from context.md and compaction.md * docs: add plugin installation steps to context engine page Show the full workflow: install via openclaw plugins install, enable in plugins.entries, then select in plugins.slots.contextEngine. Uses lossless-claw as the concrete example. * docs: address review feedback on context-engine page - Rename 'Method' column to 'Member' with explicit Kind column since info is a property, not a callable method - Document AssembleResult fields (estimatedTokens, systemPromptAddition) with types and optionality - Add lifecycle timing notes for bootstrap, ingestBatch, and dispose so plugin authors know when each is invoked * docs: fix context engine review notes * fix: harden telegram and loader contracts * refactor(tests): share setup wizard prompter * refactor(telegram-tests): share native command helpers * fix(telegram-tests): load plugin mocks before commands * refactor(telegram-tests): share webhook settlement helper * refactor(nextcloud-tests): share inbound authz setup * refactor(feishu-tests): share card action event builders * refactor(runtime-tests): share typing lease assertions * refactor(hook-tests): share subagent hook helpers * refactor(provider-tests): share discovery catalog helpers * refactor(command-tests): share workspace harness * refactor(contracts): share session binding assertions * refactor(plugin-tests): share interactive dispatch assertions * refactor(plugin-tests): share binding approval resolution * refactor(usage-tests): share provider usage loader harness * refactor(bundle-tests): share bundle mcp fixtures * refactor(provider-tests): share codex catalog assertions * refactor(apns-tests): share relay push params * refactor(media-tests): share telegram redaction assertion * refactor(heartbeat-tests): share seeded heartbeat run * refactor(kilocode-tests): share reasoning payload capture * refactor(kilocode-tests): share extra-params harness * refactor(kilocode-tests): share cache retention wrapper * refactor(attempt-tests): share wrapped stream helper * refactor(payload-tests): share empty payload assertion * Telegram: fix named-account DM topic session keys (openclaw#48773) * refactor(compaction-tests): share aggregate timeout params * refactor(compaction-tests): share snapshot assertions * refactor(truncation-tests): share first tool result text helper * refactor(system-prompt-tests): share session setup helper * refactor(lanes-tests): share table-driven assertions * refactor(google-tests): share schema tool fixture * refactor(extension-tests): share safeguard factory setup * refactor(openrouter-tests): share state dir helper * refactor(thinking-tests): share assistant drop helper * refactor(kilocode-tests): share eligibility assertions * refactor(payload-tests): share empty payload helper * refactor(model-tests): share template model mock helper * refactor(image-tests): share empty prompt image assertions * fix: restore full gate * refactor: consolidate lazy runtime surfaces * refactor: remove remaining extension core imports * refactor(payload-tests): reuse empty payload helper * refactor(image-tests): share empty ref assertions * refactor(image-tests): share single-ref detection helper * refactor(image-tests): share ref count assertions * refactor(history-tests): share array content assertion * refactor(runs-tests): share run handle factory * refactor(skills-tests): share bundled diffs setup * refactor(payload-tests): share single payload summary assertion * refactor(payload-tests): table-drive recoverable tool suppressions * refactor(payload-tests): table-drive sessions send suppressions * refactor(history-tests): share pruned image assertions * refactor(failover-tests): share observation base * refactor(extension-tests): share safeguard runtime assertions * fix(ci): quote changed extension matrix input * refactor: split plugin testing seam from bundled extension helpers * test: fix discord provider helper import * Changelog: add Telegram DM topic session-key fix * fix(ci): harden zizmor workflow diffing * feat(image-generation): add image_generate tool * test(image-generation): add live variant coverage * docs(image-generation): remove nano banana stock docs * fix(ci): restore local check suite * chore: sync pnpm lockfile importers * fix(ui): restore control-ui query token compatibility (openclaw#43979) * fix(ui): restore control-ui query token imports * chore(changelog): add entry for openclaw#43979 thanks @stim64045-spec --------- Co-authored-by: 大禹 <dayu@dayudeMac-mini.local> Co-authored-by: Val Alexander <bunsthedev@gmail.com> Co-authored-by: Val Alexander <68980965+BunsDev@users.noreply.github.com> * fix: update macOS node service to use current CLI command shape (closes openclaw#43171) (openclaw#46843) Merged via squash. Prepared head SHA: dbf2edd Co-authored-by: Br1an67 <29810238+Br1an67@users.noreply.github.com> Co-authored-by: ImLukeF <92253590+ImLukeF@users.noreply.github.com> Reviewed-by: @ImLukeF * fix(macos): stop relaunching the app after quit when launch-at-login is enabled (openclaw#40213) Merged via squash. Prepared head SHA: c702d98 Co-authored-by: stablegenius49 <259448942+stablegenius49@users.noreply.github.com> Co-authored-by: ImLukeF <92253590+ImLukeF@users.noreply.github.com> Reviewed-by: @ImLukeF * tests: add missing useNoBundledPlugins() to bundle MCP loader test The "treats bundle MCP as a supported bundle surface" test was missing the useNoBundledPlugins() call present in all surrounding bundle plugin tests. Without it, loadOpenClawPlugins() scanned and loaded the full real bundled plugins directory on every call (with cache:false), causing excessive memory pressure and an OOM crash on Linux CI, which manifested as the test timing out at 120s. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix ssh sandbox key cp (openclaw#48924) Signed-off-by: sallyom <somalley@redhat.com> * tests: fix googlechat outbound partial mock * tests(google): inject oauth credential fs stubs * tests(feishu): mock conversation runtime seam * tests(feishu): inject client runtime seam * tests(contracts): fix provider catalog runtime wiring (openclaw#49040) * fix(plugins): forward plugin subagent overrides (openclaw#48277) Merged via squash. Prepared head SHA: ffa4589 Co-authored-by: jalehman <550978+jalehman@users.noreply.github.com> Co-authored-by: jalehman <550978+jalehman@users.noreply.github.com> Reviewed-by: @jalehman * fix(security): block JVM, Python, and .NET env injection vectors in host exec sandbox (openclaw#49025) Add JAVA_TOOL_OPTIONS, _JAVA_OPTIONS, JDK_JAVA_OPTIONS, PYTHONBREAKPOINT, and DOTNET_STARTUP_HOOKS to blockedKeys in the host exec security policy. Closes openclaw#22681 * CI: rename startup memory smoke (openclaw#49041) * CI: guard gateway watch against duplicate runtime regressions (openclaw#49048) * fix(hooks): pass sessionFile and sessionKey in after_compaction hook (openclaw#40781) Merged via squash. Prepared head SHA: 11e85f8 Co-authored-by: jarimustonen <1272053+jarimustonen@users.noreply.github.com> Co-authored-by: jalehman <550978+jalehman@users.noreply.github.com> Reviewed-by: @jalehman * refactor: expose lazy runtime helper to plugins * refactor: align telegram test support with plugin runtime seam * fix(tlon): defer DM cite expansion until after auth * fix(context-engine): preserve legacy plugin sessionKey interop (openclaw#44779) Merged via squash. Prepared head SHA: e04c6fb Co-authored-by: hhhhao28 <112874572+hhhhao28@users.noreply.github.com> Co-authored-by: jalehman <550978+jalehman@users.noreply.github.com> Reviewed-by: @jalehman * test: harden CI-sensitive test suites * test: remove repeated update module imports * test: inline bluebubbles action mocks * test: reuse subagent orphan recovery imports * test: flatten twitch send mocks * test: stabilize pdf tool runtime mocks * test: reuse run-node module imports * test: reuse git commit module exports * test: trim redundant context engine assertions * test: merge duplicate update cli scenarios * test: preload plugin sdk subpath imports * test: cache provider discovery fixtures * test: merge context lookup warmup cases * test: trim lightweight status and capability suites * test: merge telegram action matrix cases * test: merge embeddings provider selection cases * test: preload inbound contract fixtures * test: merge message action media sandbox cases * test: merge pid alive linux stat cases * test: merge tts config gating cases * test: trim signal and slack action cases * test: harden commands test module seams * test: merge bundle loader fixture cases * test: merge loader cache partition cases * test: merge loader setup entry matrix * test: merge discord audit allowlist cases * test: merge zalouser audit group cases * test: merge audit auth precedence cases * test: merge channel command audit cases * test: merge browser control audit cases * test: merge control ui audit cases * test: merge feishu audit doc cases * test: merge hooks audit risk cases * test: merge gateway http audit cases * test: share audit exposure severity helper * test: merge loader provenance path cases * test: merge loader escape path cases * test: merge loader alias resolution cases * test: merge install metadata audit cases * test: merge loader duplicate registration cases * test: merge loader http route cases * test: merge audit extension and workspace cases * test: merge loader single-plugin registration cases * test: merge loader precedence cases * test: merge audit exposure heuristic cases * test: merge loader workspace warning cases * test: merge audit hooks ingress cases * test: merge audit extension allowlist severity cases * test: merge loader provenance warning cases * test: merge loader bundled telegram cases * test: merge loader memory slot cases * test: merge loader scoped load cases * test: merge audit gateway auth presence cases * test: merge audit browser container cases * test: merge audit windows acl cases * test: merge audit deny command cases * test: merge audit code safety failure cases * test: merge loader cache miss cases * test: merge update cli service refresh cases * test: merge slack action mapping cases * test: merge command owner gating cases * test: merge update status output cases * test: merge command gateway config permission cases * test: merge command approval scope cases * test: merge command hook cases * test: merge command config write denial cases * test: merge command allowlist add cases * test: merge update cli service refresh behavior * test: merge command owner show gating cases * test: merge discord action listing cases * test: merge signal reaction mapping cases * test: merge discord reaction id resolution cases * test: merge telegram reaction id cases * test: merge audit resolved inspection cases * test: merge audit gateway auth guardrail cases * test: merge audit sandbox docker danger cases * test: merge audit discord allowlist cases * test: merge audit sandbox docker config cases * test: merge audit browser sandbox cases * test: merge audit allowCommands cases * test: merge audit install metadata cases * test: merge audit code safety cases * test: merge audit dangerous flag cases * test: merge audit trust exposure cases * test: merge audit channel command hygiene cases * test: merge slack validation cases * test: merge update cli dry run cases * test: merge update cli outcome cases * test: merge update cli validation cases * test: merge action media root cases * test: merge update cli restart behavior cases * test: merge update cli channel cases * test: stabilize full gate * feat(agents): infer image generation defaults * docs(image-generation): document implicit tool enablement * refactor: dedupe plugin lazy runtime helpers * fix(telegram): persist sticky IPv4 fallback across polling restarts (fixes openclaw#48177) (openclaw#48282) * fix(telegram): persist sticky IPv4 fallback across polling restarts (fixes openclaw#48177) Hoist resolveTelegramTransport() out of createTelegramBot() so the transport (and its sticky IPv4 fallback state) persists across polling restarts. Previously, each polling restart created a new transport with stickyIpv4FallbackEnabled=false, causing repeated IPv6 timeouts on hosts with unstable IPv6 connectivity. Changes: - bot.ts: accept optional telegramTransport in TelegramBotOptions - monitor.ts: resolve transport once before polling loop - polling-session.ts: pass transport through to bot creation AI-assisted (Claude Sonnet 4). Tested: tsc --noEmit clean. * Update extensions/telegram/src/polling-session.ts Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com> * style: fix oxfmt formatting in bot.ts * test: cover telegram transport reuse across restarts * fix: preserve telegram sticky IPv4 fallback across polling restarts (openclaw#48282) (thanks @yassinebkr) --------- Co-authored-by: Yassine <yassinebkr@users.noreply.github.com> Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com> Co-authored-by: Ayaan Zaidi <hi@obviy.us> * ACP: harden startup and move configured routing behind plugin seams (openclaw#48197) * ACPX: keep plugin-local runtime installs out of dist * Gateway: harden ACP startup and service PATH * ACP: reinitialize error-state configured bindings * ACP: classify pre-turn runtime failures as session init failures * Plugins: move configured ACP routing behind channel seams * Telegram tests: align startup probe assertions after rebase * Discord: harden ACP configured binding recovery * ACP: recover Discord bindings after stale runtime exits * ACPX: replace dead sessions during ensure * Discord: harden ACP binding recovery * Discord: fix review follow-ups * ACP bindings: load channel snapshots across workspaces * ACP bindings: cache snapshot channel plugin resolution * Experiments: add ACP pluginification holy grail plan * Experiments: rename ACP pluginification plan doc * Experiments: drop old ACP pluginification doc path * ACP: move configured bindings behind plugin services * Experiments: update bindings capability architecture plan * Bindings: isolate configured binding routing and targets * Discord tests: fix runtime env helper path * Tests: fix channel binding CI regressions * Tests: normalize ACP workspace assertion on Windows * Bindings: isolate configured binding registry * Bindings: finish configured binding cleanup * Bindings: finish generic cleanup * Bindings: align runtime approval callbacks * ACP: delete residual bindings barrel * Bindings: restore legacy compatibility * Revert "Bindings: restore legacy compatibility" This reverts commit ac2ed68fa2426ecc874d68278c71c71ad363fcfe. * Tests: drop ACP route legacy helper names * Discord/ACP: fix binding regressions --------- Co-authored-by: Onur <2453968+osolmaz@users.noreply.github.com> * feat: add bundled Chutes extension (openclaw#49136) * refactor: generalize bundled provider discovery seams * feat: land chutes extension via plugin-owned auth (openclaw#41416) (thanks @Veightor) * docs(security): clarify wildcard Control UI origins * refactor: clean extension api boundaries * fix: remove duplicate setup helper imports * fix(compaction): break safeguard cancel loop for sessions with no summarizable messages (openclaw#41981) (openclaw#42215) Merged via squash. Prepared head SHA: 7ce6bd8 Co-authored-by: lml2468 <39320777+lml2468@users.noreply.github.com> Co-authored-by: jalehman <550978+jalehman@users.noreply.github.com> Reviewed-by: @jalehman * feat(mattermost): add retry logic and timeout handling for DM channel creation (openclaw#42398) Merged via squash. Prepared head SHA: 3db47be Co-authored-by: JonathanJing <17068507+JonathanJing@users.noreply.github.com> Co-authored-by: mukhtharcm <56378562+mukhtharcm@users.noreply.github.com> Reviewed-by: @mukhtharcm * docs(hooks): clarify trust model and audit guidance * test: stabilize memory async search close * refactor: narrow extension public seams * chore: add gog CLI support via custom Docker image Add Dockerfile.gog to extend openclaw:local with the gog binary (Google Workspace CLI). Also forward OPENAI_API_KEY and GEMINI_API_KEY env vars in docker-compose.yml for both services. Made-with: Cursor * chore: inject GOG_KEYRING_PASSWORD for non-interactive gog auth The gog CLI uses a file-based keyring to store Google OAuth tokens. In Docker/headless environments, the keyring prompts for a passphrase interactively, which blocks the agent from running gog autonomously. Setting GOG_KEYRING_PASSWORD as an environment variable allows gog to unlock the keyring without user interaction, enabling the agent to execute Gmail, Calendar, Drive, and other Google Workspace commands directly via the gog skill. Setup steps to enable the gog skill in Docker: 1. Build the custom image: docker build -f Dockerfile.gog -t openclaw:gog . 2. Set OPENCLAW_IMAGE=openclaw:gog in .env 3. Set GOG_KEYRING_PASSWORD= in .env (empty = no passphrase) 4. Run: gog auth keyring file (inside container) 5. Run: gog auth credentials /path/to/client_secret.json 6. Run: gog auth add you@gmail.com --manual 7. Add to openclaw.json: tools.alsoAllow = ["exec", "process"] Made-with: Cursor * docs: add Docker commands reference and Mac migration plan * docs: add docker save/load alternative to migration plan * docs: add Docker+gog env example file * config: clear unused OPENAI_API_KEY and document LLM auth in migration guide * chore: remove .env from git tracking (contains secrets) Made-with: Cursor * docs: add openai-codex auth commands to migration guide * docs: add gog token persistence, exec tool fix, and image migration cases - docker-compose.yml: mount ~/.openclaw/gogcli as volume so gog tokens survive container restarts - docs/docker-commands.html: add case 10 (gog token loss diagnosis + re-auth + volume persistence) - docs/docker-commands.html: add case 11 (exec tool not enabled — tools.alsoAllow fix + persistence explanation) - docs/docker-commands.html: add case 08 (migrate Docker Desktop images to Colima via docker save/load) + TOC entry * docs: add Colima disk lock fix to docker-commands * feat(docker): add local Whisper audio transcription to gog image * docs: update docker-commands with TTS and contact number fixes * docs: add gog token expiry troubleshooting and publish-app fix (caso 12) * docs: add OpenAI Codex rate limit troubleshooting (caso 13) * docs: add model set/status commands to caso 13 * docs: add provider/model switching guide (caso 14) * docs: replace placeholder email with herbert.cadbury.bot@gmail.com --------- Signed-off-by: sallyom <somalley@redhat.com> Co-authored-by: Peter Steinberger <steipete@gmail.com> Co-authored-by: scoootscooob <zhentongfan@gmail.com> Co-authored-by: scoootscooob <167050519+scoootscooob@users.noreply.github.com> Co-authored-by: Josh Lehman <josh@martian.engineering> Co-authored-by: Vincent Koc <vincentkoc@ieee.org> Co-authored-by: Frank Yang <frank.ekn@gmail.com> Co-authored-by: stim64045-spec <stim64045@gmail.com> Co-authored-by: 大禹 <dayu@dayudeMac-mini.local> Co-authored-by: Val Alexander <bunsthedev@gmail.com> Co-authored-by: Val Alexander <68980965+BunsDev@users.noreply.github.com> Co-authored-by: Br1an <932039080@qq.com> Co-authored-by: Br1an67 <29810238+Br1an67@users.noreply.github.com> Co-authored-by: ImLukeF <92253590+ImLukeF@users.noreply.github.com> Co-authored-by: Stable Genius <stablegenius043@gmail.com> Co-authored-by: stablegenius49 <259448942+stablegenius49@users.noreply.github.com> Co-authored-by: Chris Kimpton <chris@kimptoc.net> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> Co-authored-by: Sally O'Malley <somalley@redhat.com> Co-authored-by: huntharo <harold@pwrdrvr.com> Co-authored-by: jalehman <550978+jalehman@users.noreply.github.com> Co-authored-by: Andrew Demczuk <andrew.demczuk@gmail.com> Co-authored-by: Tak Hoffman <781889+Takhoffman@users.noreply.github.com> Co-authored-by: Jari Mustonen <jari.mustonen@iki.fi> Co-authored-by: jarimustonen <1272053+jarimustonen@users.noreply.github.com> Co-authored-by: F_ool <112874572+hhhhao28@users.noreply.github.com> Co-authored-by: Kwest OG <50209930+yassinebkr@users.noreply.github.com> Co-authored-by: Yassine <yassinebkr@users.noreply.github.com> Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com> Co-authored-by: Ayaan Zaidi <hi@obviy.us> Co-authored-by: Bob <dutifulbob@gmail.com> Co-authored-by: Onur <2453968+osolmaz@users.noreply.github.com> Co-authored-by: Peter Steinberger <peter@steipete.me> Co-authored-by: Menglin Li <limenglin5911@gmail.com> Co-authored-by: lml2468 <39320777+lml2468@users.noreply.github.com> Co-authored-by: Jonathan Jing <JonathanJing@users.noreply.github.com> Co-authored-by: JonathanJing <17068507+JonathanJing@users.noreply.github.com> Co-authored-by: mukhtharcm <56378562+mukhtharcm@users.noreply.github.com>

Telegram: fix named-account DM topic session keys

1a02e13

openclaw-barnacle Bot added the channel: telegram Channel integration: telegram label Mar 17, 2026

vincentkoc self-assigned this Mar 17, 2026

openclaw-barnacle Bot added size: S maintainer Maintainer-authored PR labels Mar 17, 2026

This comment was marked as spam.

Sign in to view

vincentkoc marked this pull request as ready for review March 17, 2026 07:41

vincentkoc merged commit 1eb810a into openclaw:main Mar 17, 2026
26 of 39 checks passed

github-actions Bot mentioned this pull request Mar 17, 2026

📡 Upstream Digest — 2026-03-17 08:42 UTC curtismercier/openclaw-mods#287

Open

kimptoc pushed a commit to kimptoc/openclaw that referenced this pull request Mar 17, 2026

Telegram: fix named-account DM topic session keys (openclaw#48773)

39d8037

nikolaisid pushed a commit to nikolaisid/openclaw that referenced this pull request Mar 18, 2026

Telegram: fix named-account DM topic session keys (openclaw#48773)

b75ebca

Bermudarat mentioned this pull request Mar 20, 2026

fix(telegram): apply named-account session fallback to native commands #47508

Closed

sbezludny pushed a commit to sbezludny/openclaw that referenced this pull request Mar 27, 2026

Telegram: fix named-account DM topic session keys (openclaw#48773)

03b0b81

alexey-pelykh pushed a commit to remoteclaw/remoteclaw that referenced this pull request Mar 28, 2026

Telegram: fix named-account DM topic session keys (openclaw#48773)

5e156f8

(cherry picked from commit 1eb810a)

alexey-pelykh pushed a commit to remoteclaw/remoteclaw that referenced this pull request Apr 4, 2026

Telegram: fix named-account DM topic session keys (openclaw#48773)

508e205

lovewanwan pushed a commit to lovewanwan/openclaw that referenced this pull request Apr 28, 2026

Telegram: fix named-account DM topic session keys (openclaw#48773)

49d295b

ogt-redknie pushed a commit to ogt-redknie/OPENX that referenced this pull request May 2, 2026

Telegram: fix named-account DM topic session keys (openclaw#48773)

e0c1b51

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Telegram: fix named-account DM topic session keys#48773

Telegram: fix named-account DM topic session keys#48773
vincentkoc merged 1 commit intoopenclaw:mainfrom
vincentkoc:vincentkoc-code/fix-48204-telegram-session-status

vincentkoc commented Mar 17, 2026

Uh oh!

This comment was marked as spam.

Uh oh!

greptile-apps Bot commented Mar 17, 2026 •

edited

Loading

Comments Outside Diff (2)

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

vincentkoc commented Mar 17, 2026

Summary

Change Type (select all)

Scope (select all touched areas)

Linked Issue/PR

User-visible / Behavior Changes

Security Impact (required)

Repro + Verification

Environment

Steps

Expected

Actual

Evidence

Human Verification (required)

Review Conversations

Compatibility / Migration

Failure Recovery (if this breaks)

Risks and Mitigations

Uh oh!

This comment was marked as spam.

Uh oh!

greptile-apps Bot commented Mar 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Greptile Summary

Confidence Score: 4/5

Comments Outside Diff (2)

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

greptile-apps Bot commented Mar 17, 2026 •

edited

Loading