feat(routing): route replies to originating channel#328
Closed
jalehman wants to merge 4 commits intoopenclaw:mainfrom
Closed
feat(routing): route replies to originating channel#328jalehman wants to merge 4 commits intoopenclaw:mainfrom
jalehman wants to merge 4 commits intoopenclaw:mainfrom
Conversation
6d71dd4 to
8eb617e
Compare
9f45660 to
4784399
Compare
4784399 to
f60dce2
Compare
Implement reply routing based on OriginatingChannel/OriginatingTo fields. This ensures replies go back to the provider where the message originated instead of using the session's lastChannel. Changes: - Add OriginatingChannel/OriginatingTo fields to MsgContext (templating.ts) - Add originatingChannel/originatingTo fields to FollowupRun (queue.ts) - Create route-reply.ts with provider-agnostic router - Update all providers (Telegram, Slack, Discord, Signal, iMessage) to pass originating channel info - Update reply.ts to pass originating channel to followupRun - Update followup-runner.ts to use route-reply for originating channels This addresses the issue where messages from one provider (e.g., Slack) would receive replies on a different provider (e.g., Telegram) because the queue used the last active dispatcher instead of the originating one.
When OriginatingChannel matches Surface (same provider), use normal dispatcher. Only route via routeReply() when they differ, ensuring cross-provider messages (e.g., Telegram queued while Slack active) get routed back to their origin.
When queued messages come from different providers (Slack + Telegram), process them individually instead of collecting into a single prompt. This ensures each reply routes back to its originating provider. - Add hasCrossProviderItems() to detect multi-provider queues - Skip collect mode when cross-provider detected - Preserve originatingChannel/originatingTo when collecting same-provider
f60dce2 to
75e4b07
Compare
Contributor
|
Thank you - I did refactor the whole logic. Apologies, it's been a few wild days. |
dgarson
added a commit
to dgarson/clawdbot
that referenced
this pull request
Feb 9, 2026
* feat(ui): add error boundary component with retry & friendly messages - New error-boundary.ts component with renderError/renderErrorIf helpers - Custom element <error-boundary> with auto-retry and exponential backoff - friendlyError() maps raw errors to user-friendly messages + suggestions - Supports severity levels (danger/warning/info), compact mode, dismiss - Collapsible technical details section - ARIA compliance with role=alert and aria-live - Replaces all inline callout danger patterns across 23 view files - Consistent error UX across agents, channels, sessions, config, etc. * Web: reset retry timers on error changes (openclaw#273) * UI: reset auto-retry timers on error changes
dgarson
added a commit
to dgarson/clawdbot
that referenced
this pull request
Feb 9, 2026
* feat: tool journal/diagnostics * feat: journal fixes * feat(ui): add error boundary component with retry & friendly messages - New error-boundary.ts component with renderError/renderErrorIf helpers - Custom element <error-boundary> with auto-retry and exponential backoff - friendlyError() maps raw errors to user-friendly messages + suggestions - Supports severity levels (danger/warning/info), compact mode, dismiss - Collapsible technical details section - ARIA compliance with role=alert and aria-live - Replaces all inline callout danger patterns across 23 view files - Consistent error UX across agents, channels, sessions, config, etc. * Web: reset retry timers on error changes (openclaw#273) * Gateway: unify exec approvals with tool approval flow (openclaw#319) * Gateway: unify exec approvals * Gateway: guard exec approval resolves * Feat/pr review monitor (openclaw#313) * minor fixes * feat: monitor AI PR review comments * PR review monitor: add pagination config (openclaw#324) * Codex/review branch changes and identify issues (openclaw#325) * minor fixes * feat: monitor AI PR review comments * PR review monitor: add pagination config * UI: reset auto-retry timers on error changes (openclaw#328) * feat(ui): add error boundary component with retry & friendly messages - New error-boundary.ts component with renderError/renderErrorIf helpers - Custom element <error-boundary> with auto-retry and exponential backoff - friendlyError() maps raw errors to user-friendly messages + suggestions - Supports severity levels (danger/warning/info), compact mode, dismiss - Collapsible technical details section - ARIA compliance with role=alert and aria-live - Replaces all inline callout danger patterns across 23 view files - Consistent error UX across agents, channels, sessions, config, etc. * Web: reset retry timers on error changes (openclaw#273) * UI: reset auto-retry timers on error changes * Add execution layer runtime parity gap analysis (openclaw#280) * Add execution layer runtime parity gap analysis Comprehensive analysis of Pi Runtime vs Claude Agent SDK feature gaps in the unified execution layer, with 20 prioritized next steps. https://claude.ai/code/session_017oEzmayzdirGAKmSw2ryQZ * Meridia: wire multi-factor scoring into capture hook * merge/minor fixes for ui/* * Meridia: add per-capture graph fanout queue with retries * Meridia: enforce sanitization before persistence and fanout * Meridia: complete Tier2 vector probing and Postgres vector support --------- Co-authored-by: Claude <[email protected]> * Codex/review branch changes and identify issues (openclaw#325) * minor fixes * feat: monitor AI PR review comments * PR review monitor: add pagination config * Work queue: add heartbeat leases (openclaw#329) * fix: duplicate lines on main * Tools: clarify work_item refs and workstream (openclaw#332) Co-authored-by: Claude Opus 4.6 <[email protected]> * Config: clarify agents.list placement, accept agents.list in web import, and document guidance (openclaw#331) * Config: clarify agents.list validation * Web: tighten agents list import validation * Sessions: align label limits (openclaw#333) * Work queue: add work item refs support (openclaw#312) * Tests: update migration count * Tools: accept refs in work_item tool * Work queue: link Codex tasks to PRs (post GitHub comments) (openclaw#337) * Work queue: link codex tasks to PRs * Work queue: skip branchPrefix-only PR lookup * Claude/runtime orchestrator tools eu d uu (openclaw#327) * feat(agents): add runtime tool-approval orchestrator with approvals.tools config - Add approvals.tools config types + zod schema (enabled, mode, timeoutMs, policy, routing, classifier) - Create tool-approval orchestrator module (decision engine, param redaction, gateway integration) - Integrate orchestrator into before-tool-call wrapper path (runs after plugin hooks, before execution) - Add ToolApprovalBlockedError with stable machine-readable error shape - Add 90 tests covering all mode/decision/risk branches - Backward-compatible: no behavior change when approvals.tools is missing or disabled * feat: upgrade /approve and Discord handler to canonical tool approvals - /approve now queries tool.approvals.get for canonical records and resolves via tool.approval.resolve (with requestHash); falls back to legacy exec.approval.resolve when no canonical record is found - Discord handler listens for tool.approval.requested/resolved events and renders generic tool approval embeds for non-exec tools - resolveApproval prefers tool.approval.resolve when requestHash is cached, keeping legacy exec path for backward compatibility - Updated command description to 'tool approval requests' - Added shouldHandleToolApproval for canonical event filtering - Extended tests with canonical, legacy-fallback, and gateway-error scenarios * refactor: rename .clawdbrain → .openclaw and fix repo/domain references - Settings dir: ~/.clawdbrain → ~/.openclaw - Repo references: openclaw/clawdbrain → dgarson/clawdbrain - Domain: clawdbrain.bot → openclaw.ai - CLI command: clawdbrain login → openclaw login - 48 files changed across src/, docs/, apps/web/, ui/ * cron timeout fixes * feat(agents): wire tool approval context from config into tool creation path - Inject approvals.tools config into wrapToolWithBeforeToolCallHook context - Populate channel field from messageProvider via resolveGatewayMessageChannel - Wire callGatewayTool as the gateway call adapter for approval requests - Approval context is only constructed when approvals.tools exists and is enabled * fix: address review gaps in tool approval handler - Exec dedup: store canonical request for exec tools and defer embed creation by 200ms so the legacy mirror gets first shot; if the mirror never arrives, fall back to a generic tool embed (future-proofs against legacy event removal) - Extract sendToolApprovalEmbed to eliminate code duplication - Add buildApprovalCustomId / parseApprovalData generic aliases (same wire format, clearer naming for non-exec tool code paths) - Add alias identity tests * fix: minor tool approval request fixes * auto-reply/approval integration fix * include exec approval doc * fix: agent-runner-execution integration into auto-reply, executor/kernel fixes * more work on agent runner and memory/heartbeta integration * lots of tests resulting from unification of exec kernel; refactored * Redact arrays in approval helper * lancedb fixes * more fixes/test updates * fix: minor problem * fix: restore proper non-throwing session label truncation --------- Co-authored-by: Claude <[email protected]> * Tool approval/protocol cleanup (openclaw#334) * infra: consolidate tool approval types and clean protocol schema * infra: bridge tool approval routing config into forwarder * agents: enrich tool approval decision engine with config resolution and reason codes * test: update tool approval tests for protocol and decision engine changes * infra: consolidate tool approval types and clean protocol schema * infra: bridge tool approval routing config into forwarder * agents: enrich tool approval decision engine with config resolution and reason codes * test: update tool approval tests for protocol and decision engine changes * chore: conflict resolution * chore: checkou tfrom main * Codex/map paramssummary to exec command field (openclaw#342) * infra: consolidate tool approval types and clean protocol schema * infra: bridge tool approval routing config into forwarder * agents: enrich tool approval decision engine with config resolution and reason codes * test: update tool approval tests for protocol and decision engine changes * infra: consolidate tool approval types and clean protocol schema * infra: bridge tool approval routing config into forwarder * agents: enrich tool approval decision engine with config resolution and reason codes * test: update tool approval tests for protocol and decision engine changes * chore: conflict resolution * chore: checkou tfrom main * Tool approvals: preserve exec command * Codex/add web inbox for tool approvals (openclaw#339) * Web: add tool approval inbox support * Web: fallback approval resolution * Web: fall back to agent approvals when IDs differ (openclaw#263) * memclawd: scaffold phase 0 service foundation (openclaw#330) * memclawd: apply oxfmt * Memclawd: add client samples and align pipeline config * Codex/implement work item refs system d2mkjz (openclaw#344) * Tools: clarify work_item refs and workstream * Tests: update migration count --------- Co-authored-by: Claude Opus 4.6 <[email protected]> * Codex/review branch changes and identify issues kuj3uy (openclaw#343) * Tests: update migration count * Tools: accept refs in work_item tool * Work queue: add refs reindex command * Work queue: align refs migration and add refs-reindex CLI (openclaw#345) * Tests: update migration count * Work queue: move refs backfill to 004 migration --------- Co-authored-by: Claude Opus 4.6 <[email protected]> --------- Co-authored-by: Claude <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
When multiple messaging providers (Telegram, Slack, WhatsApp, etc.) share the
mainsession, replies now route back to the originating channel instead of usinglastChannel.Problem
Previously, if you:
lastChannel)Solution
Track
OriginatingChannelandOriginatingToper-message and route replies accordingly.Changes
src/auto-reply/templating.ts- AddedOriginatingChannel/OriginatingTotoMsgContextsrc/auto-reply/reply/route-reply.ts(new) - Provider-agnostic reply routersrc/auto-reply/reply/dispatch-from-config.ts- Route to originating channel when cross-providersrc/auto-reply/reply/queue.ts- Track originating channel in followup queueOriginatingChannel/OriginatingToBehavior
routeReply()to originating channelTesting