[codex] Fix main-session web UI reply routing to Telegram by BeeSting50 · Pull Request #29328 · openclaw/openclaw

BeeSting50 · 2026-02-28T02:25:39Z

Title

Reply routing fails when session.dmScope=main and replies are sent from chat.send (Web Control UI): replies stay in web history and are not delivered to Telegram.

Severity Assessment

Medium. Message delivery silently fails on a supported configuration (session.dmScope=main) and can cause operators to believe users received responses when they did not.

Impact

When users send Telegram messages that are unified into the main session, replying from the web Control UI can keep the assistant response only in session history, without delivering it back to Telegram.

Affected Component

src/gateway/server-methods/chat.ts (chat.send context construction)
src/auto-reply/reply/dispatch-from-config.ts (origin routing decision path)

Technical Reproduction

Configure session.dmScope to main.
Send a Telegram DM to OpenClaw so the message lands in the main session.
Open the Web Control UI and reply in that same session.
Observe the reply appears in web session history but is not delivered to Telegram.

Root cause:
chat.send always set OriginatingChannel to internal webchat, which prevented dispatch-from-config from routing final replies to the stored external session delivery context.

Demonstrated Impact

In runtime logs during reproduction, UI-originated runs executed with messageChannel=webchat, and no Telegram outbound send occurred for that reply path. User-observed behavior matched this: response visible in session history only, not in Telegram.

Environment

OpenClaw version tested: 2026.2.26
Platform: macOS (Darwin)
Channel under test: Telegram (DM)
Session mode: session.dmScope=main

Remediation Advice

In chat.send, inherit routable origin metadata from session delivery fields (deliveryContext / lastChannel) when available, instead of forcing internal webchat origin.
Preserve OriginatingChannel, OriginatingTo, AccountId, and MessageThreadId for downstream route-reply logic.
Keep regression tests for:
- mixed Provider/Surface origin routing behavior
- chat.send origin inheritance from session delivery context

Validation

pnpm test src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/server-methods/chat.directive-tags.test.ts

greptile-apps · 2026-02-28T02:29:08Z

Greptile Summary

Fixes message delivery routing when replies are sent from the Web Control UI to Telegram messages unified in the main session. The fix correctly inherits routing metadata (OriginatingChannel, OriginatingTo, AccountId, MessageThreadId) from session delivery context in chat.send, and updates the routing decision logic in dispatch-from-config.ts to prefer Provider over Surface for determining the current surface. The changes are well-tested with new test cases covering the main scenarios and edge cases. The implementation follows existing patterns in the codebase for field-by-field fallback between deliveryContext and last* fields.

Confidence Score: 4/5

This PR is safe to merge with low risk. The fix addresses a clear bug in message routing without breaking existing functionality.
The implementation is sound and well-tested. The logic correctly inherits routing metadata from session delivery context and updates the routing decision to prefer Provider over Surface. The changes follow existing patterns in the codebase. Minor point deduction because there's a theoretical edge case where partial deliveryContext population could lead to inconsistent routing metadata (mixing channel from deliveryContext with to from last* fields), but this is unlikely in normal operation if deliveryContext is set atomically.
No files require special attention - all changes are straightforward and well-tested

_{Last reviewed commit: 11e8e47}

masatohoshino · 2026-02-28T11:29:33Z

Additional field report (real-world, Telegram-only operator)

Summary

I can reproduce reply-routing drift even when I never send replies from Control UI (I reply 100% from Telegram).
Control UI may be open, but no UI-side reply action is used.

Environment

OpenClaw: 2026.2.26
Channel: Telegram DM
Web Control UI: open concurrently at times
Date observed: 2026-02-28 (UTC)

What I observed

User-visible symptom: assistant outputs are visible in session/history, but some are not delivered to Telegram.
This happened after restart windows around:
- 2026-02-28 09:56:53 UTC
- 2026-02-28 10:05:45 UTC
- 2026-02-28 10:21:51 UTC
- 2026-02-28 10:25:22 UTC

Hard evidence (same incident window)

Window: 2026-02-28 10:26:00–10:32:00 UTC

Assistant messages in session transcript: 10
Outbound log lines with channel=telegram: 2
Telegram API errors (4xx/5xx) in that window: none found

Relevant user messages in transcript:

2026-02-28T10:28:03.236Z: "Messages are not appearing on Telegram. Please send the email."
2026-02-28T10:48:59.330Z: "Okay, but messages are not appearing on Telegram."

Why this may extend scope of current fix

PR #29328 focuses on chat.send from Web UI.
In my case, no UI reply action was used, but drift still occurred.
So there may be another path where route target/origin metadata is overwritten or not restored correctly when webchat is connected and session is unified.

Request

Could maintainers confirm whether there are other non-chat.send paths that can mutate/override OriginatingChannel / deliveryContext / lastChannel in unified sessions (agent:main:main)?
I can provide sanitized timeline IDs/log snippets if needed.

…#31573)

Takhoffman · 2026-03-02T13:54:25Z

PR #29328 - [codex] Fix main-session web UI reply routing to Telegram (#29328)

Merged via squash.

Merge commit: 050e928
Verified: pnpm test src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/server-methods/chat.directive-tags.test.ts; pnpm exec oxfmt --check src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/server-methods/chat.directive-tags.test.ts src/auto-reply/reply/dispatch-from-config.ts src/gateway/server-methods/chat.ts CHANGELOG.md
Changes made:
- Rebased PR onto current main.
- Added Feishu-specific regression coverage for routing metadata inheritance and route dispatch.
- Updated chat.send route eligibility to preserve non-webchat origin channels when delivery context is present.
- Added changelog entry for [Bug]: Webchat UI sends messages to wrong session when continuing a Feishu conversation #31573 user-visible fix.
Why these changes were made:
- Original PR fixed the routing path but lacked Feishu-specific proof for [Bug]: Webchat UI sends messages to wrong session when continuing a Feishu conversation #31573 and needed a stricter origin-channel gate to avoid dropping plugin-channel delivery context.
Changelog: CHANGELOG.md updated=true required=true opt_out=false

Thanks @BeeSting50!

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7bbb3bea54

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector · 2026-03-02T13:57:45Z

src/gateway/server-methods/chat.ts

+        OriginatingChannel: originatingChannel,
+        OriginatingTo: originatingTo,


Surface route delivery failures from chat.send

Setting OriginatingChannel/OriginatingTo here makes chat.send go through cross-channel routeReply delivery, but that path does not throw on send failure (it logs and returns ok: false/queuedFinal: false), and chat.send still marks the run as successful. In environments where the target channel is unavailable or the stored route is stale, the operator gets an "ok" completion while Telegram/Feishu receives nothing. Please treat failed routed finals as a failed run (or explicitly fallback) before broadcasting success.

Useful? React with 👍 / 👎.

@BeeSting50

…9328) thanks @BeeSting50 Verified: - pnpm test src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/server-methods/chat.directive-tags.test.ts - pnpm exec oxfmt --check src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/server-methods/chat.directive-tags.test.ts src/auto-reply/reply/dispatch-from-config.ts src/gateway/server-methods/chat.ts CHANGELOG.md - CI note: non-required check "check" failed on unrelated src/slack/monitor/events/messages.ts TS errors outside this PR scope. Co-authored-by: BeeSting50 <[email protected]> Co-authored-by: Tak Hoffman <[email protected]>

@BeeSting50

…anks @BeeSting50 Verified: - pnpm test src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/server-methods/chat.directive-tags.test.ts - pnpm exec oxfmt --check src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/server-methods/chat.directive-tags.test.ts src/auto-reply/reply/dispatch-from-config.ts src/gateway/server-methods/chat.ts CHANGELOG.md - CI note: non-required check "check" failed on unrelated src/slack/monitor/events/messages.ts TS errors outside this PR scope. Co-authored-by: BeeSting50 <[email protected]> Co-authored-by: Tak Hoffman <[email protected]>

@BeeSting50

…9328) thanks @BeeSting50 Verified: - pnpm test src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/server-methods/chat.directive-tags.test.ts - pnpm exec oxfmt --check src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/server-methods/chat.directive-tags.test.ts src/auto-reply/reply/dispatch-from-config.ts src/gateway/server-methods/chat.ts CHANGELOG.md - CI note: non-required check "check" failed on unrelated src/slack/monitor/events/messages.ts TS errors outside this PR scope. Co-authored-by: BeeSting50 <[email protected]> Co-authored-by: Tak Hoffman <[email protected]>

@BeeSting50

…9328) thanks @BeeSting50 Verified: - pnpm test src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/server-methods/chat.directive-tags.test.ts - pnpm exec oxfmt --check src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/server-methods/chat.directive-tags.test.ts src/auto-reply/reply/dispatch-from-config.ts src/gateway/server-methods/chat.ts CHANGELOG.md - CI note: non-required check "check" failed on unrelated src/slack/monitor/events/messages.ts TS errors outside this PR scope. Co-authored-by: BeeSting50 <[email protected]> Co-authored-by: Tak Hoffman <[email protected]>

@BeeSting50

…9328) thanks @BeeSting50 Verified: - pnpm test src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/server-methods/chat.directive-tags.test.ts - pnpm exec oxfmt --check src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/server-methods/chat.directive-tags.test.ts src/auto-reply/reply/dispatch-from-config.ts src/gateway/server-methods/chat.ts CHANGELOG.md - CI note: non-required check "check" failed on unrelated src/slack/monitor/events/messages.ts TS errors outside this PR scope. Co-authored-by: BeeSting50 <[email protected]> Co-authored-by: Tak Hoffman <[email protected]>

@BeeSting50

…9328) thanks @BeeSting50 Verified: - pnpm test src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/server-methods/chat.directive-tags.test.ts - pnpm exec oxfmt --check src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/server-methods/chat.directive-tags.test.ts src/auto-reply/reply/dispatch-from-config.ts src/gateway/server-methods/chat.ts CHANGELOG.md - CI note: non-required check "check" failed on unrelated src/slack/monitor/events/messages.ts TS errors outside this PR scope. Co-authored-by: BeeSting50 <[email protected]> Co-authored-by: Tak Hoffman <[email protected]>

@BeeSting50

…9328) thanks @BeeSting50 Verified: - pnpm test src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/server-methods/chat.directive-tags.test.ts - pnpm exec oxfmt --check src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/server-methods/chat.directive-tags.test.ts src/auto-reply/reply/dispatch-from-config.ts src/gateway/server-methods/chat.ts CHANGELOG.md - CI note: non-required check "check" failed on unrelated src/slack/monitor/events/messages.ts TS errors outside this PR scope. Co-authored-by: BeeSting50 <[email protected]> Co-authored-by: Tak Hoffman <[email protected]>

@BeeSting50

…9328) thanks @BeeSting50 Verified: - pnpm test src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/server-methods/chat.directive-tags.test.ts - pnpm exec oxfmt --check src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/server-methods/chat.directive-tags.test.ts src/auto-reply/reply/dispatch-from-config.ts src/gateway/server-methods/chat.ts CHANGELOG.md - CI note: non-required check "check" failed on unrelated src/slack/monitor/events/messages.ts TS errors outside this PR scope. Co-authored-by: BeeSting50 <[email protected]> Co-authored-by: Tak Hoffman <[email protected]> (cherry picked from commit 050e928)

@BeeSting50

…9328) thanks @BeeSting50 Verified: - pnpm test src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/server-methods/chat.directive-tags.test.ts - pnpm exec oxfmt --check src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/server-methods/chat.directive-tags.test.ts src/auto-reply/reply/dispatch-from-config.ts src/gateway/server-methods/chat.ts CHANGELOG.md - CI note: non-required check "check" failed on unrelated src/slack/monitor/events/messages.ts TS errors outside this PR scope. Co-authored-by: BeeSting50 <[email protected]> Co-authored-by: Tak Hoffman <[email protected]> (cherry picked from commit 050e928)

@BeeSting50

…9328) thanks @BeeSting50 Verified: - pnpm test src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/server-methods/chat.directive-tags.test.ts - pnpm exec oxfmt --check src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/server-methods/chat.directive-tags.test.ts src/auto-reply/reply/dispatch-from-config.ts src/gateway/server-methods/chat.ts CHANGELOG.md - CI note: non-required check "check" failed on unrelated src/slack/monitor/events/messages.ts TS errors outside this PR scope. Co-authored-by: BeeSting50 <[email protected]> Co-authored-by: Tak Hoffman <[email protected]>

openclaw-barnacle bot added app: web-ui App: web-ui gateway Gateway runtime size: S labels Feb 28, 2026

masatohoshino mentioned this pull request Feb 28, 2026

Bug Report: Reply routing fails when session.dmScope is main #29301

Closed

BeeSting50 closed this Mar 1, 2026

BeeSting50 deleted the codex/issue-29301-main-routing branch March 1, 2026 03:01

BeeSting50 restored the codex/issue-29301-main-routing branch March 2, 2026 03:48

BeeSting50 reopened this Mar 2, 2026

BeeSting50 and others added 2 commits March 2, 2026 07:45

Gateway: preserve originating channel for chat.send replies

d26c715

fix(webchat): preserve feishu session routing for chat.send (openclaw…

7bbb3be

…#31573)

Takhoffman force-pushed the codex/issue-29301-main-routing branch from 11e8e47 to 7bbb3be Compare March 2, 2026 13:48

Takhoffman merged commit 050e928 into openclaw:main Mar 2, 2026
19 of 21 checks passed

Takhoffman mentioned this pull request Mar 2, 2026

[Bug]: Webchat UI sends messages to wrong session when continuing a Feishu conversation #31573

Closed

chatgpt-codex-connector bot reviewed Mar 2, 2026

View reviewed changes

BestJoester mentioned this pull request Mar 3, 2026

[Bug]: chat.send inherits OriginatingChannel from session delivery context, causing duplicate delivery in dmScope=main sessions #33619

Closed

Yuandiaodiaodiao mentioned this pull request Mar 3, 2026

fix(routing): prevent duplicate delivery in dmScope=main sessions #33629

Closed

6 tasks

alexey-pelykh mentioned this pull request Mar 10, 2026

Cherry-pick: Channel fixes — Feishu routing, Slack typing, voice-call, Telegram UI remoteclaw/remoteclaw#730

Closed

4 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

[codex] Fix main-session web UI reply routing to Telegram#29328

[codex] Fix main-session web UI reply routing to Telegram#29328
Takhoffman merged 2 commits intoopenclaw:mainfrom
BeeSting50:codex/issue-29301-main-routing

BeeSting50 commented Feb 28, 2026

Uh oh!

greptile-apps bot commented Feb 28, 2026 •

edited

Loading

Uh oh!

masatohoshino commented Feb 28, 2026

Uh oh!

Uh oh!

Takhoffman commented Mar 2, 2026

Uh oh!

chatgpt-codex-connector bot left a comment

Uh oh!

chatgpt-codex-connector bot Mar 2, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

		OriginatingChannel: originatingChannel,
		OriginatingTo: originatingTo,

Uh oh!

Conversation

BeeSting50 commented Feb 28, 2026

Title

Severity Assessment

Impact

Affected Component

Technical Reproduction

Demonstrated Impact

Environment

Remediation Advice

Validation

Uh oh!

greptile-apps bot commented Feb 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Greptile Summary

Confidence Score: 4/5

Uh oh!

masatohoshino commented Feb 28, 2026

Summary

Environment

What I observed

Hard evidence (same incident window)

Why this may extend scope of current fix

Request

Uh oh!

Uh oh!

Takhoffman commented Mar 2, 2026

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector bot Mar 2, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

greptile-apps bot commented Feb 28, 2026 •

edited

Loading