fix(telegram): route account-scoped topic agents by codysai001 · Pull Request #91189 · openclaw/openclaw

codysai001 · 2026-06-07T13:56:25Z

Summary

Allow non-default Telegram account topic routes with an explicit topic agentId to dispatch instead of being dropped as unnamed group fallback.
Preserve the guard for non-default account group messages that do not have an explicit topic agent route.
Add regression coverage for account-scoped topic agents and native Telegram reply-root session continuity.

Reviewer replay

Configure a non-default Telegram account group topic route under channels.telegram.accounts.<account-id>.groups.<group-id>.topics.<topic-id> with agentId set and requireMention=false.
Send a message in that Telegram topic.
Verify the gateway logs an inbound message and dispatches a session instead of logging telegram: drop non-default account requires explicit binding.
Remove the topic agentId or test an unconfigured topic on the same non-default account group and verify the fallback drop still happens.

Real behavior proof

Behavior addressed: Account-scoped Telegram topic routes with an explicit topic agentId should dispatch to the configured agent on non-default Telegram accounts. Non-default account group fallback without an explicit topic route should still drop.

Real environment tested: Local OpenClaw gateway rebuilt from this patch on macOS, connected to the existing Gartner Gary non-default Telegram account and the Gartner / Wiki Telegram topic.

Exact steps or command run after the patch:

Applied this patch locally.
Rebuilt OpenClaw and restarted the local gateway.
Retested the existing Gartner / Wiki Telegram topic that had been failing on the non-default account route.
Sent a live smoke prompt to @GartnerGaryBot in that Telegram topic.

Evidence after fix:

Before the fix, the live gateway dropped messages in that topic before dispatch:

telegram: drop non-default account requires explicit binding target=gartner-gary

After the fix, the same live Telegram topic dispatched to the topic agent route:

Inbound message telegram:group:<redacted>:topic:2 -> @GartnerGaryBot

I then sent this live Telegram smoke prompt in the Gartner / Wiki topic:

@GartnerGaryBot post-fix smoke test: reply exactly GARTNER-WIKI-FIXED-OK. Make no file changes.

The bot replied in the same Telegram topic:

GARTNER-WIKI-FIXED-OK

Observed result after fix: The same account-scoped Telegram topic that previously logged drop non-default account requires explicit binding dispatched to @GartnerGaryBot, and the bot replied in the live topic with GARTNER-WIKI-FIXED-OK.

What was not tested: I did not test every Telegram account or every topic route shape in a live environment. The regression suite covers the named-account fallback and explicit topic-agent branches.

Verification

pnpm vitest run extensions/telegram/src/bot-message-context.named-account-dm.test-support.ts extensions/telegram/src/bot-message-context.require-mention.test.ts extensions/telegram/src/bot-message-context.acp-bindings.test.ts
pnpm build
Live Gartner / Wiki topic smoke test replied GARTNER-WIKI-FIXED-OK after the runtime patch was applied locally.

clawsweeper · 2026-06-07T13:58:21Z

Codex review: needs maintainer review before merge. Reviewed June 8, 2026, 5:18 AM ET / 09:18 UTC.

Summary
The branch updates Telegram message-context routing so named non-default account forum topics with a topic-level agentId bypass the fallback drop, and adds regression coverage for that route.

PR surface: Source +33. Total +33 across 2 files.

Reproducibility: yes. source-reproducible: current main passes topicConfig?.agentId into route resolution but then drops every named-account group fallback before the topic route can dispatch. I did not run a local or live Telegram repro in this read-only review.

Review metrics: none identified.

Merge readiness
Overall: 🐚 platinum hermit
Proof: 🦞 diamond lobster
Patch quality: 🐚 platinum hermit
Result: ready for maintainer review.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

none.

Mantis proof suggestion
A maintainer-controlled live Telegram transcript would directly prove the configured-topic dispatch and unconfigured-topic drop split. A maintainer can ask Mantis to capture proof by posting a new PR comment that starts with the OpenClaw Mantis account mention, followed by:

telegram live: verify a non-default Telegram account forum topic with topic agentId dispatches, while an unconfigured topic on the same account still drops.

Risk before merge

[P1] Merging intentionally changes explicitly configured non-default Telegram account forum topics from dropped inbound messages to dispatched messages, so maintainers should accept that compatibility change before landing.

Maintainer options:

Accept topic agentId as explicit binding (recommended)
Land this focused fix if maintainers agree that account-scoped topic agentId is explicit enough configuration for non-default account group dispatch.
Keep the guard closed
Pause or close this PR if maintainers decide non-default account groups must dispatch only through binding-channel routes rather than topic-agent config.

Next step before merge

No automated repair lane is needed; the remaining action is maintainer acceptance and merge handling for a compatibility-sensitive Telegram routing change.

Security
Cleared: No concrete security or supply-chain concern found; the diff only changes Telegram routing/test code and still flows through existing group/topic access checks.

Review details

Best possible solution:

Land the focused guard change once maintainers accept topic agentId as explicit binding for non-default Telegram account topics and normal required checks pass.

Do we have a high-confidence way to reproduce the issue?

Yes, source-reproducible: current main passes topicConfig?.agentId into route resolution but then drops every named-account group fallback before the topic route can dispatch. I did not run a local or live Telegram repro in this read-only review.

Is this the best way to solve the issue?

Yes, this is the best narrow fix: it treats the existing topic agentId route as explicit binding while preserving the non-default account group fallback drop for unconfigured groups.

AGENTS.md: found and applied where relevant.

Codex review notes: model gpt-5.5, reasoning high; reviewed against fc6400ede389.

Label changes

Label changes:

add proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes after-fix live Telegram output from a rebuilt local gateway, with before/after dispatch logs and a same-topic bot reply; private identifiers are redacted.
remove merge-risk: 🚨 session-state: Current PR review merge-risk labels are merge-risk: 🚨 compatibility.

Label justifications:

P1: A configured non-default Telegram account forum topic can drop live inbound messages before dispatch, breaking a real channel workflow.
merge-risk: 🚨 compatibility: The PR intentionally changes existing non-default account topic behavior from drop to dispatch when a topic agentId is configured.
rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🦞 diamond lobster and patch quality is 🐚 platinum hermit.
status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (live_output): The PR body includes after-fix live Telegram output from a rebuilt local gateway, with before/after dispatch logs and a same-topic bot reply; private identifiers are redacted.
proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes after-fix live Telegram output from a rebuilt local gateway, with before/after dispatch logs and a same-topic bot reply; private identifiers are redacted.
mantis: telegram-visible-proof: Mantis should capture Telegram visible proof. This changes visible Telegram topic dispatch and reply behavior that can be demonstrated in a short Telegram live or desktop proof.

Evidence reviewed

PR surface:

Source +33. Total +33 across 2 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	2	36	3	+33
Tests	0	0	0	0
Docs	0	0	0	0
Config	0	0	0	0
Generated	0	0	0	0
Other	0	0	0	0
Total	2	36	3	+33

What I checked:

Current main drops named-account group fallback before topic-agent dispatch: Current main resolves topicConfig?.agentId before routing, but then returns null for any non-default account group route matched by the default fallback. (extensions/telegram/src/bot-message-context.ts:246, fc6400ede389)
Existing route resolver already supports topic agent IDs: resolveTelegramConversationRoute trims a topic agentId, builds a Telegram topic session key for it, and preserves the configured topic agent even when that agent is absent from the current config snapshot. (extensions/telegram/src/conversation-route.ts:77, fc6400ede389)
PR head scopes the bypass to explicit topic routes: The PR adds hasExplicitTopicRoute and keeps the drop for named-account groups when no topic-level agentId is present. (extensions/telegram/src/bot-message-context.ts:262, 194bf6a715b9)
Regression test covers the intended route: The PR adds a named-account forum topic test that expects account atlas to dispatch to topic-agent and keep the existing topic session key shape. (extensions/telegram/src/bot-message-context.named-account-dm.test-support.ts:144, 194bf6a715b9)
Real behavior proof is live-output based: The PR body reports a rebuilt local gateway against a real non-default Telegram account topic, showing the previous drop log, then an inbound dispatch log and same-topic bot reply after the patch. (194bf6a715b9)
Telegram review guidance applied: The Telegram maintainer note requires real Telegram proof for topic behavior and treats group/topic authorization as explicit-config sensitive, which informed the proof and compatibility-risk review. (.agents/maintainer-notes/telegram.md:25, fc6400ede389)

Likely related people:

vincentkoc: Blame on the current named-account fallback guard and topic route resolver points to this author in be617fdd.... (role: introduced current main behavior; confidence: high; commits: be617fdd622a; files: extensions/telegram/src/bot-message-context.ts, extensions/telegram/src/conversation-route.ts)
obviyus: The latest PR head commit removes earlier unrelated forum-session changes while preserving the focused guard change, and the live PR is assigned to this person. (role: recent PR repair author and assigned reviewer; confidence: medium; commits: 194bf6a715b9; files: extensions/telegram/src/bot-message-context.ts, extensions/telegram/src/bot-message-context.named-account-dm.test-support.ts)

What the crustacean ranks mean

🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works

ClawSweeper keeps one durable marker-backed review comment per issue or PR.
Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
Maintainers can also comment @clawsweeper review to request a fresh review only.
Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

Co-authored-by: Codex <codex@openai.com>

obviyus · 2026-06-08T09:21:24Z

Landed via rebase onto main.

Scoped tests: node scripts/run-vitest.mjs extensions/telegram/src/bot-message-context.named-account-dm.test-support.ts extensions/telegram/src/bot-message-context.require-mention.test.ts extensions/telegram/src/bot-message-context.acp-bindings.test.ts extensions/telegram/src/bot-message-context.topic-agentid.test.ts (4 files, 28 tests)
CI: workflow 27127436613 attempt 2 passed after rerunning an unrelated checkout-timeout failure in checks-node-agentic-commands-doctor-plugins-tools
Changelog: not updated; release-note context is in the PR body for this user-facing Telegram routing fix
PR head before merge: 194bf6a715b91c852bc0fa6201d5e20ef723b383
Landed commit: b75d1a0b85b0651ae9d5bd60071bd1f66dd86e0d

Thanks @codysai001!

…26.6.6) (#1040) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [ghcr.io/openclaw/openclaw](https://openclaw.ai) ([source](https://github.com/openclaw/openclaw)) | patch | `2026.6.5` → `2026.6.6` | --- ### Release Notes <details> <summary>openclaw/openclaw (ghcr.io/openclaw/openclaw)</summary> ### [`v2026.6.6`](https://github.com/openclaw/openclaw/blob/HEAD/CHANGELOG.md#202666) [Compare Source](openclaw/openclaw@v2026.6.5...v2026.6.6) ##### Highlights - Security boundaries are substantially tighter across transcripts, sandbox binds, host environment inheritance, MCP stdio, Codex HTTP access, native search policy, elevated sender checks, deleted-agent ACP bypasses, loopback tools, Discord moderation, and Teams group actions; exec approvals now fail closed on timeout. ([#91529](openclaw/openclaw#91529), [#91618](openclaw/openclaw#91618), [#91615](openclaw/openclaw#91615), [#91619](openclaw/openclaw#91619), [#91741](openclaw/openclaw#91741), [#91745](openclaw/openclaw#91745), [#91746](openclaw/openclaw#91746), [#91748](openclaw/openclaw#91748), [#91749](openclaw/openclaw#91749), [#91750](openclaw/openclaw#91750), [#91751](openclaw/openclaw#91751), [#91752](openclaw/openclaw#91752), [#91763](openclaw/openclaw#91763), [#89938](openclaw/openclaw#89938)) Thanks [@joshavant](https://github.com/joshavant), [@pgondhi987](https://github.com/pgondhi987), [@mmaps](https://github.com/mmaps), [@eleqtrizit](https://github.com/eleqtrizit), [@shakkernerd](https://github.com/shakkernerd), and [@drobison00](https://github.com/drobison00). - Telegram delivery is safer and more coherent: account-scoped topics route to the right agent, streamed text survives tool calls, `/compact` works on generic ingress, callback handling uses concrete APIs, draft chunking is shared, durable dispatch dedupe moved into the SDK, and unauthorized DM text stays out of cache and prompt context. ([#91189](openclaw/openclaw#91189), [#88682](openclaw/openclaw#88682), [#89588](openclaw/openclaw#89588), [#90212](openclaw/openclaw#90212), [#91876](openclaw/openclaw#91876), [#91874](openclaw/openclaw#91874), [#91904](openclaw/openclaw#91904), [#91478](openclaw/openclaw#91478), [#91915](openclaw/openclaw#91915)) Thanks [@codysai001](https://github.com/codysai001), [@alexzhu0](https://github.com/alexzhu0), [@joelnishanth](https://github.com/joelnishanth), [@snowzlm](https://github.com/snowzlm), [@obviyus](https://github.com/obviyus), and [@sallyom](https://github.com/sallyom). - iMessage recovery and delivery now cover always-on inbound restart, durable echo markers, block streaming, idle approval discovery, hardened outbound transport, and actionable inbound startup diagnostics. ([#91335](openclaw/openclaw#91335), [#91449](openclaw/openclaw#91449), [#88969](openclaw/openclaw#88969), [#88530](openclaw/openclaw#88530), [#91783](openclaw/openclaw#91783), [#91785](openclaw/openclaw#91785)) Thanks [@omarshahine](https://github.com/omarshahine), [@jmissig](https://github.com/jmissig), and [@colmbrogan](https://github.com/colmbrogan). - Browser and MCP connectivity gained existing-session CDP support, discovered WebSocket validation, default-profile `cdpUrl` handling, safer browser-output boundaries, Streamable HTTP loopback transport, corrected OAuth/SSE authorization handling, and broader schema compatibility. ([#91422](openclaw/openclaw#91422), [#89851](openclaw/openclaw#89851), [#91736](openclaw/openclaw#91736), [#91747](openclaw/openclaw#91747), [#91451](openclaw/openclaw#91451), [#80143](openclaw/openclaw#80143)) Thanks [@pgondhi987](https://github.com/pgondhi987), [@anagnorisis2peripeteia](https://github.com/anagnorisis2peripeteia), [@lifuyue](https://github.com/lifuyue), [@eleqtrizit](https://github.com/eleqtrizit), [@LiuwqGit](https://github.com/LiuwqGit), and [@HemantSudarshan](https://github.com/HemantSudarshan). - Control UI startup and first-reply latency are lower through cached model metadata, removal of the startup catalog wait, lazy slash-command loading, and first-event tracing with slow-reply diagnostics. ([#91531](openclaw/openclaw#91531), [#91538](openclaw/openclaw#91538), [#91568](openclaw/openclaw#91568), [#91583](openclaw/openclaw#91583), [#91598](openclaw/openclaw#91598)) - Provider support expands with OpenRouter OAuth onboarding and Claude Fable 5 adaptive thinking, while Codex sessions keep correct compaction ownership, local models skip guardian review, dynamic tool progress normalizes cleanly, and Gemma 4 reasoning replay is preserved. ([#91830](openclaw/openclaw#91830), [#91882](openclaw/openclaw#91882), [#91590](openclaw/openclaw#91590), [#88630](openclaw/openclaw#88630), [#88768](openclaw/openclaw#88768), [#91696](openclaw/openclaw#91696)) Thanks [@Patrick-Erichsen](https://github.com/Patrick-Erichsen), [@joshavant](https://github.com/joshavant), [@bdjben](https://github.com/bdjben), and [@Coder-Wangyankun](https://github.com/Coder-Wangyankun). ##### Changes - CLI progress: emit Claude CLI commentary progress events and bridge inter-tool commentary into channel progress without exposing internal protocol scaffolding. ([#89834](openclaw/openclaw#89834), [#90883](openclaw/openclaw#90883)) Thanks [@anagnorisis2peripeteia](https://github.com/anagnorisis2peripeteia). - Observability: allow trusted diagnostics channels to capture tool input/output content, add first-assistant-event traces, and warn on slow initial replies. ([#91256](openclaw/openclaw#91256), [#91568](openclaw/openclaw#91568), [#91583](openclaw/openclaw#91583)) Thanks [@amknight](https://github.com/amknight). - Plugins/ClawHub: dogfood reusable package publishing, let dry runs skip publish approval, allow declared installed trusted hooks, report managed plugin version drift, and warn instead of failing on retired Skill Workshop configuration. ([#91574](openclaw/openclaw#91574), [#91591](openclaw/openclaw#91591), [#90004](openclaw/openclaw#90004), [#90927](openclaw/openclaw#90927), [#90838](openclaw/openclaw#90838)) Thanks [@Patrick-Erichsen](https://github.com/Patrick-Erichsen), [@brokemac79](https://github.com/brokemac79), and [@lonexreb](https://github.com/lonexreb). - Memory/providers: move the local llama.cpp runtime into its provider plugin, batch embeddings across files, persist the agent model catalog cache, and keep QMD JSON search one-shot while filtering stale REM recall previews. ([#91324](openclaw/openclaw#91324), [#89138](openclaw/openclaw#89138), [#90457](openclaw/openclaw#90457), [#91837](openclaw/openclaw#91837), [#91851](openclaw/openclaw#91851)) Thanks [@osolmaz](https://github.com/osolmaz), [@mushuiyu886](https://github.com/mushuiyu886), [@ai-hpc](https://github.com/ai-hpc), and [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Channels/mobile: add the QQBot group mention toggle, improve iPad and iPhone control surfaces, and expose the active connection host in the TUI footer. ([#91423](openclaw/openclaw#91423), [#91557](openclaw/openclaw#91557), [#89909](openclaw/openclaw#89909)) Thanks [@cxyhhhhh](https://github.com/cxyhhhhh), [@Solvely-Colin](https://github.com/Solvely-Colin), and [@baskduf](https://github.com/baskduf). - Performance: prewarm TUI runtime plugins, deduplicate plugin auto-enable fanout, trim dense text-delta snapshots, and reuse prepared startup model metadata. ([#90782](openclaw/openclaw#90782), [#89978](openclaw/openclaw#89978), [#91580](openclaw/openclaw#91580), [#91531](openclaw/openclaw#91531)) Thanks [@RomneyDa](https://github.com/RomneyDa) and [@ai-hpc](https://github.com/ai-hpc). ##### Fixes - Agent/session recovery: drop stale approval follow-ups after session rebind, remove drained reply-queue items by identity, recover stale main and visible replies, preserve Codex context-engine compaction ownership, lower the default compaction timeout to 180 seconds while respecting explicit configuration, and keep provider-failure terminal lifecycle state correct. ([#85679](openclaw/openclaw#85679), [#91450](openclaw/openclaw#91450), [#91566](openclaw/openclaw#91566), [#91840](openclaw/openclaw#91840), [#91590](openclaw/openclaw#91590), [#91361](openclaw/openclaw#91361), [#91895](openclaw/openclaw#91895)) Thanks [@openperf](https://github.com/openperf), [@yetval](https://github.com/yetval), [@joshavant](https://github.com/joshavant), [@wangmiao0668000666](https://github.com/wangmiao0668000666), and [@TurboTheTurtle](https://github.com/TurboTheTurtle). - User-visible content boundaries: suppress Codex/Harmony protocol artifacts, neutralize browser and LanceDB memory media directives, redact transcript images, and preserve native `/compact` replies through source suppression. ([#89151](openclaw/openclaw#89151), [#91422](openclaw/openclaw#91422), [#91425](openclaw/openclaw#91425), [#91529](openclaw/openclaw#91529), [#90212](openclaw/openclaw#90212)) Thanks [@joelnishanth](https://github.com/joelnishanth), [@pgondhi987](https://github.com/pgondhi987), [@joshavant](https://github.com/joshavant), and [@snowzlm](https://github.com/snowzlm). - Channel delivery: keep WhatsApp captured replies attached to the successor controller after restart, retry Feishu rate limits, preserve Mattermost thread replies, canonicalize LINE webhook paths, restore Discord reply hydration and runtime timeout exports, and show OpenAI Realtime WebRTC assistant transcripts. ([#85823](openclaw/openclaw#85823), [#89659](openclaw/openclaw#89659), [#91684](openclaw/openclaw#91684), [#91649](openclaw/openclaw#91649), [#90263](openclaw/openclaw#90263), [#91686](openclaw/openclaw#91686), [#90426](openclaw/openclaw#90426)) Thanks [@itsuzef](https://github.com/itsuzef), [@ladygege](https://github.com/ladygege), [@jacobtomlinson](https://github.com/jacobtomlinson), [@fuller-stack-dev](https://github.com/fuller-stack-dev), and [@shushushv](https://github.com/shushushv). - Cron: cancel active task runs cleanly, preserve terminal timeout/cancel state, and recover no-deliver tool warnings instead of silently losing the outcome. ([#90666](openclaw/openclaw#90666), [#90678](openclaw/openclaw#90678)) Thanks [@ai-hpc](https://github.com/ai-hpc). - Gateway/config/auth: share the approval runtime socket token, replace arrays explicitly in `config.patch`, skip the deleted-agent guard only for valid ACP harness sessions, surface headless LaunchAgent state, verify SQLite auth migration before cleanup, and arm QMD startup maintenance. ([#87105](openclaw/openclaw#87105), [#91551](openclaw/openclaw#91551), [#91219](openclaw/openclaw#91219), [#91614](openclaw/openclaw#91614), [#91740](openclaw/openclaw#91740), [#91978](openclaw/openclaw#91978)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev) and [@scotthuang](https://github.com/scotthuang). - Providers/Codex: clarify quota errors, restore the Codex synthetic usage line, canonicalize Codex protocol assets, require API-key auth for realtime voice, normalize ACP model refs, preserve Gemma 4 `reasoning_content`, and avoid guardian review for local models. ([#91390](openclaw/openclaw#91390), [#91709](openclaw/openclaw#91709), [#91507](openclaw/openclaw#91507), [#91567](openclaw/openclaw#91567), [#88630](openclaw/openclaw#88630), [#91696](openclaw/openclaw#91696)) Thanks [@hxy91819](https://github.com/hxy91819), [@brokemac79](https://github.com/brokemac79), [@RomneyDa](https://github.com/RomneyDa), [@joshavant](https://github.com/joshavant), and [@Coder-Wangyankun](https://github.com/Coder-Wangyankun). - Updates/builds: recover package Gateway restarts after refresh failure, expose plugin convergence repair, fall back to Corepack in PATH-less pnpm environments, seed the correct Docker store packages, and keep ClawHub dry-run and publish paths reusable. ([#91581](openclaw/openclaw#91581), [#91599](openclaw/openclaw#91599), [#91547](openclaw/openclaw#91547), [#91591](openclaw/openclaw#91591)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev), [@sallyom](https://github.com/sallyom), and [@Patrick-Erichsen](https://github.com/Patrick-Erichsen). - UI: require explicit user intent before opening chat sessions and drain restored chat queues after session switches. ([#91480](openclaw/openclaw#91480)) Thanks [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Android: avoid the `dataSync` foreground-service type for persistent nodes. ([#80082](openclaw/openclaw#80082)) Thanks [@davelutztx](https://github.com/davelutztx). - Native hooks: bound relay lifetimes so abandoned native hook connections cannot linger indefinitely. ([#91550](openclaw/openclaw#91550)) Thanks [@joshavant](https://github.com/joshavant). </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.erwanleboucher.dev/eleboucher/homelab/pulls/1040

openclaw-barnacle Bot added channel: telegram Channel integration: telegram size: S triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. labels Jun 7, 2026

openclaw-barnacle Bot added proof: supplied External PR includes structured after-fix real behavior proof. and removed triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. labels Jun 7, 2026

openclaw-barnacle Bot removed the proof: sufficient ClawSweeper judged the real behavior proof convincing. label Jun 7, 2026

openclaw-barnacle Bot added size: XS and removed size: S labels Jun 8, 2026

obviyus self-assigned this Jun 8, 2026

codysai001 and others added 3 commits June 8, 2026 09:09

fix(telegram): route account-scoped topic agents

6776fe9

Co-authored-by: Codex <codex@openai.com>

fix(telegram): satisfy topic reply lint

bcc21fa

Co-authored-by: Codex <codex@openai.com>

fix(telegram): keep forum topic sessions stable

194bf6a

obviyus force-pushed the codex/telegram-topic-agent-routes branch from 71c6d83 to 194bf6a Compare June 8, 2026 09:09

openclaw-barnacle Bot removed the proof: sufficient ClawSweeper judged the real behavior proof convincing. label Jun 8, 2026

clawsweeper Bot added proof: sufficient ClawSweeper judged the real behavior proof convincing. and removed merge-risk: 🚨 session-state 🚨 May lose, corrupt, stale, or mis-associate session, agent, or context state. labels Jun 8, 2026

obviyus merged commit b75d1a0 into openclaw:main Jun 8, 2026
285 of 288 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(telegram): route account-scoped topic agents#91189

fix(telegram): route account-scoped topic agents#91189
obviyus merged 3 commits into
openclaw:mainfrom
codysai001:codex/telegram-topic-agent-routes

codysai001 commented Jun 7, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented Jun 7, 2026 •

edited

Loading

Uh oh!

Uh oh!

obviyus commented Jun 8, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

codysai001 commented Jun 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Reviewer replay

Real behavior proof

Verification

Uh oh!

clawsweeper Bot commented Jun 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

obviyus commented Jun 8, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

codysai001 commented Jun 7, 2026 •

edited

Loading

clawsweeper Bot commented Jun 7, 2026 •

edited

Loading