fix(telegram): preserve inbound debounce order by osolmaz · Pull Request #52998 · openclaw/openclaw

osolmaz · 2026-03-23T16:21:00Z

Summary

Problem: Telegram inbound debounce buffered a same-chat message without reserving its execution slot, so a later message for the same chat could overtake the timer-backed flush and receive the earlier reply out of order.
Why it matters: after a long debounced turn, replies could appear shifted by one in Telegram, matching the user-visible desync reported in Message desync after long agent output (responses shifted by one) #52982.
What changed: reserve per-key flush order inside createInboundDebouncer(...), serialize later same-key work behind that reservation, and add both a shared debouncer regression and a Telegram middleware-level regression.
What did NOT change (scope boundary): this does not change queue/followup routing, dispatcher semantics, or unrelated group-mention behavior.

Change Type (select all)

Scope (select all touched areas)

Linked Issue/PR

User-visible / Behavior Changes

Telegram same-chat debounced messages now keep reply order even when the first run is still active when the second debounce window fires.

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: local Node 22 / pnpm workspace
Model/provider: N/A
Integration/channel (if any): Telegram inbound debounce path
Relevant config (redacted): messages.inbound.debounceMs=4321, Telegram DM policy open for test harness

Steps

Send Telegram message A in a debounced chat and let its debounce timer fire.
Keep A's reply generation active so its run has started but not finished.
Send message B in the same chat and let B's debounce timer fire.

Expected

Message B stays queued behind message A and replies are delivered in A, then B order.

Actual

Before this change, B could start and deliver before A because the buffered A flush had not reserved same-key execution order.
After this change, both the shared debouncer regression and Telegram regression keep A ahead of B.

Evidence

Attach at least one:

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:
- pnpm test -- src/auto-reply/inbound.test.ts -t "createInboundDebouncer"
- pnpm test -- extensions/telegram/src/bot.create-telegram-bot.test.ts -t "preserves same-chat reply order when a debounced run is still active"
- pnpm test -- extensions/telegram/src/bot.create-telegram-bot.test.ts
- scripts/committer "Telegram: preserve inbound debounce order" ... (pnpm check passed inside the wrapper)
Edge cases checked:
- timer-backed buffered flush already started
- later same-key non-debounced work stays behind the pending buffered flush
- Telegram sequentialize + debounce integration keeps first/second reply order intact
What you did not verify:
- full cross-channel manual repro outside Telegram
- pnpm test -- src/auto-reply/inbound.test.ts currently still has unrelated existing failures in resolveGroupRequireMention on current main, so verification stayed scoped to the createInboundDebouncer slice

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.

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 commit 0f2b99fa03
Files/config to restore:
- src/auto-reply/inbound-debounce.ts
- src/auto-reply/inbound.test.ts
- extensions/telegram/src/bot.create-telegram-bot.test.ts
Known bad symptoms reviewers should watch for:
- buffered same-chat turns starting concurrently again
- Telegram replies for adjacent debounced turns arriving in reverse order

Risks and Mitigations

Risk:
- Reserving same-key execution order could accidentally serialize unrelated buffered work for too long if key scoping is too broad.
- Mitigation:
- The reservation is strictly per debounce key, and the new shared regression covers the exact timer-backed overtake case.

aisle-research-bot · 2026-03-23T16:21:06Z

🔒 Aisle Security Analysis

We found 1 potential security issue(s) in this PR:

#	Severity	Title
1	🔵 Low	Follow-up queue can become stuck when enqueued with restartIfIdle=false (potential DoS)

1. 🔵 Follow-up queue can become stuck when enqueued with restartIfIdle=false (potential DoS)

Property	Value
Severity	Low
CWE	CWE-400
Location	`src/auto-reply/reply/agent-runner.ts:237-250`

Description

The follow-up message queue can be left idle after items are enqueued, causing messages to accumulate indefinitely and delaying processing.

In runReplyAgent, when activeRunQueueAction === "enqueue-followup", the code enqueues a follow-up run with restartIfIdle=false, meaning enqueueFollowupRun() will not call kickFollowupDrainIfIdle() even if the queue is not draining.

Drain kickoff is then conditioned on a liveness check:

Drain is only started via finalizeWithFollowup(...) when !isRunActive?.()
isRunActive is optional (can be undefined), and its current implementation (isEmbeddedPiRunActive) only checks presence in an in-memory map (ACTIVE_EMBEDDED_RUNS.has(sessionId)), not whether the run is actually making progress.

If the active run becomes stuck (e.g., leaked handle, deadlock, missed cleanup) but isRunActive() continues to return true, the queue may never be drained, leading to unbounded queue growth and prolonged delays (availability/DoS).

Vulnerable code:

enqueueFollowupRun(
  queueKey,
  followupRun,
  resolvedQueue,
  "message-id",
  queuedRunFollowupTurn,
  false,
);
// ...
if (!isRunActive?.()) {
  finalizeWithFollowup(undefined, queueKey, queuedRunFollowupTurn);
}

Recommendation

Ensure enqueuing follow-ups always results in a drain kickoff even when the “active run” liveness signal is stale.

Options:

Kick the drain when idle even in the enqueue-followup path (preferably with a guard to avoid concurrent drains), e.g. keep restartIfIdle=true and rely on beginQueueDrain(...) to prevent duplicates.
Add a failsafe: if the queue is non-draining for >N ms, force a drain regardless of isRunActive().
Strengthen isRunActive semantics to reflect true liveness (e.g., heartbeat timestamp / progress counter) instead of just map membership.

Example change (safe default kick when idle):

enqueueFollowupRun(
  queueKey,
  followupRun,
  resolvedQueue,
  "message-id",
  queuedRunFollowupTurn,
  true, // restartIfIdle
);

If concurrent drains are a concern, enforce a single-drain invariant inside kickFollowupDrainIfIdle/scheduleFollowupDrain using the queue's draining flag (or similar lock) rather than disabling restarts at enqueue time.

Analyzed PR: #52998 at commit af20938

_{Last updated on: 2026-03-23T18:37:08Z}

greptile-apps · 2026-03-23T16:24:08Z

Greptile Summary

This PR fixes a race condition in the Telegram inbound debounce path where a buffered message (message A) could be overtaken by a later message (message B) for the same chat when A's debounce timer fired while A's reply was still generating.

What changed:

src/auto-reply/inbound-debounce.ts: Introduces a keyChains map that serializes per-key task execution. Each new DebounceBuffer immediately enqueues a task in keyChains that waits on an internal buffer.ready promise before flushing. When the debounce timer (or flushKey) fires it releases buffer.ready, unblocking that reserved slot — meaning any subsequent same-key work was already queued behind it in keyChains and cannot overtake it. The releaseBuffer guard (readyReleased flag) makes repeated flushBuffer calls idempotent.
src/auto-reply/inbound.test.ts: Adds a unit regression that manually intercepts the timer callback, starts flush fix: add @lid format support and allowFrom wildcard handling #1, verifies flush Login fails with 'WebSocket Error (socket hang up)' ECONNRESET #2 stays queued, then releases the gate and asserts correct completion order.
extensions/telegram/src/bot.create-telegram-bot.test.ts: Adds an integration regression that exercises the full Telegram middleware stack (including an in-process sequentialize shim) and asserts sendMessage is called in the correct order for same-chat consecutive messages.
CHANGELOG.md: One-line entry referencing the fix and Message desync after long agent output (responses shifted by one) #52982.

The approach correctly serializes debounced key execution without touching queue/followup routing, dispatcher semantics, or unrelated group-mention behavior.

Confidence Score: 5/5

This PR is safe to merge; the fix is narrowly scoped to per-key debounce serialization, is idempotent under repeated flush calls, and is covered by two targeted regression tests that verify the exact overtake scenario.
The implementation is logically sound: the keyChains chain is correctly seeded when the buffer is created (before any await), the readyReleased guard prevents double-release, and the temporary task: Promise.resolve() placeholder is overwritten synchronously before any event-loop yield so flushBuffer can never observe the stale value. Both tests exercise the precise race being fixed and have visible failure guards (expect(timerIndex).toBeGreaterThanOrEqual(0)). No existing serialization contracts or unrelated paths are touched.
No files require special attention.

_{Reviews (1): Last reviewed commit: "Telegram: preserve inbound debounce orde..." | Re-trigger Greptile}

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0f2b99fa03

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

src/auto-reply/inbound-debounce.ts

vincentkoc · 2026-03-23T16:49:59Z

Added e5fe793635 on top of this PR to cover the remaining followup-side race as well:

refresh the stored followup drain callback from the newest run before idle-drain restarts
add the queue regression in src/auto-reply/reply/reply-flow.test.ts

Validation rerun on the combined branch:

pnpm test -- src/auto-reply/inbound.test.ts -t "createInboundDebouncer"
pnpm test -- src/auto-reply/reply/reply-flow.test.ts extensions/telegram/src/bot.create-telegram-bot.test.ts
pnpm build

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e5fe793635

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

src/auto-reply/reply/agent-runner.ts

vincentkoc · 2026-03-23T17:08:22Z

Addressed the follow-up review points in ba18c98394:

keep the stronger per-key debounce chain only when a keyed buffer/chain is already active, so debounceMs: 0 does not serialize unrelated same-key turns by default
guard onError so handler failures cannot break the keyed chain
refresh the remembered followup drain callback without auto-starting a drain while an active run is still in flight

Revalidated with:

pnpm test -- src/auto-reply/inbound.test.ts -t "createInboundDebouncer"
pnpm test -- src/auto-reply/reply/reply-flow.test.ts extensions/telegram/src/bot.create-telegram-bot.test.ts
pnpm build

jacobtomlinson

A few things worth addressing before this lands:

canTrackKey() accounting is incorrect (src/auto-reply/inbound-debounce.ts)

Math.max(buffers.size, keyChains.size) < maxTrackedKeys

This underestimates tracked state — a key flushed from buffers but still live in keyChains won't be counted by the buffers branch, and vice versa. The cap can be exceeded by up to ~2×. More critically, when the cap is hit the fallback calls runFlush([item]) directly with no keyed-chain enqueue — so an item for an already-active key can race with in-flight work for that key. This is a correctness gap for active keys, not just a soft limit issue. Fix: use the union size or buffers.size + keyChains.size as a conservative bound; also consider whether the bypass path should still append to an existing active chain even at cap.

runFlush exception swallowing — The double-catch is intentional to keep keyed-chain liveness, but enqueue() always resolves successfully regardless of flush outcome. Worth an explicit comment documenting this is deliberate, so future readers don't assume callers can detect a dropped flush.

Redundant readyReleased guards — enqueueReservedKeyTask has its own local readyReleased closure variable; DebounceBuffer also has a readyReleased field. releaseBuffer() only touches buffer.readyReleased; the closure guard is a separate copy. They don't conflict, but the dual bookkeeping is confusing — a short comment would help.

The serialization approach itself looks sound — slot reserved before any await, guard is idempotent, no observable race between reservation and flush. Test coverage on ordering, overtake, and drain lifecycle is solid.

steipete · 2026-03-23T18:11:33Z

Landed via temp rebase onto main.

Gate: pnpm check && pnpm build && OPENCLAW_TEST_PROFILE=low OPENCLAW_TEST_SERIAL_GATEWAY=1 pnpm test
Land commit: af20938
Merge commit: 1b69d9e

Thanks @osolmaz!

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: af209382fe

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-03-23T18:20:29Z

src/auto-reply/inbound-debounce.ts

+    if (!canTrackKey(key)) {
+      // When the debounce map is saturated, fall back to immediate keyed work
+      // instead of buffering, but still preserve same-key ordering.
+      await enqueueKeyTask(key, async () => {
+        await runFlush([item]);


Do not disable inbound debounce after 2,048 active keys

Once createInboundDebouncer() hits the new default maxTrackedKeys limit, this branch stops buffering new keys and runs them immediately instead. Because maxTrackedKeys now defaults to 2,048 at construction time and the built-in wrapper in src/channels/inbound-debounce-policy.ts:30-49 does not expose any override, large Slack/Telegram/Teams fan-in deployments will silently stop honoring messages.inbound.debounceMs for every conversation beyond that threshold. That is a new behavior regression from the previously uncapped implementation, and it can fan out exactly the burst of agent runs that inbound debouncing is meant to absorb.

Useful? React with 👍 / 👎.

…osolmaz

…osolmaz)

…osolmaz

…osolmaz)

…osolmaz

…osolmaz)

…osolmaz

…osolmaz)

…osolmaz

…osolmaz)

…osolmaz

…osolmaz)

@frankekn

…claw#105) * fix(web-search): mark DuckDuckGo experimental * docs(tools): update DuckDuckGo Search for landed plugin code - Mark as experimental (not just unofficial) - Add region and safeSearch tool parameters (from DDG schema) - Add plugin config example for region/safeSearch defaults - Document auto-detection order (100 = last) - Note SafeSearch defaults to moderate - Verified against extensions/duckduckgo/src/ * fix(agents): deny local MEDIA paths for MCP results * Usage: include reset and deleted session archives (openclaw#43215) Merged via squash. Prepared head SHA: 49ed6c2 Co-authored-by: rcrick <[email protected]> Co-authored-by: frankekn <[email protected]> Reviewed-by: @frankekn * docs(tools): soften DDG wording (scrapes -> pulls/gathers) * fix(build): add stable memory-cli dist entry (openclaw#51759) Co-authored-by: oliviareid-svg <[email protected]> Co-authored-by: Frank <[email protected]> * refactor!: drop legacy CLAWDBOT env compatibility * refactor!: remove moltbot state-dir migration fallback * fix(gateway): preserve async hook ingress provenance * fix(ci): write dist build stamp after builds * perf: trim vitest hot imports and refresh manifests * fix(security): unwrap time dispatch wrappers * fix(plugin-sdk): fall back to src root alias files * fix(ci): skip docs-only preflight pnpm audit * docs(changelog): note time exec approval fix * docs: refresh plugin-sdk api baseline * fix(runtime): make dist-runtime staging idempotent * fix(media): bound remote error-body snippet reads * fix(gateway): gate internal command persistence mutations * fix: restrict remote marketplace plugin sources * fix(runtime): skip peer resolution for bundled plugin deps * docs(agents): prefer current test model examples * fix(exec): escape invisible approval filler chars * test(models): refresh example model fixtures * fix(security): unify dispatch wrapper approval hardening * fix(security): harden explicit-proxy SSRF pinning * fix: gate synology chat reply name matching * docs: clarify sessions_spawn ACP vs subagent policies * refactor(exec): split wrapper resolution modules * refactor(exec): make dispatch wrapper semantics spec-driven * refactor(exec): share wrapper trust planning * refactor(exec): rename wrapper plans for trust semantics * fix: include .npmrc in onboard docker build * test: trim docker live auth mounts * Docs: refresh config baseline for Synology Chat * refactor: clarify synology delivery identity names * refactor: centralize synology dangerous name matching * refactor: narrow synology legacy name lookup * refactor: audit synology dangerous name matching * refactor: dedupe synology config schema * fix: normalize scoped vitest filter paths * fix(voice-call): harden webhook pre-auth guards * fix(synology-chat): fail closed shared webhook paths * docs: credit nexrin in synology changelog * test: fix base vitest thread regressions * test: finish base vitest thread fixture fixes * test(voice-call): accept oversize webhook socket resets * test: honor env auth in gateway live probes * fix: harden plugin docker e2e * Docs: align MiniMax examples with M2.7 * fix(ci): restore stale guardrails and baselines * Test: isolate qr dashboard integration suite * Gateway: resolve fallback plugin context lazily * fix: bind bootstrap setup codes to node profile * fix(tlon): unify settings reconciliation semantics * refactor(synology-chat): type startup webhook path policy * docs(synology-chat): clarify multi-account webhook paths * refactor: unify minimax model and failover live policies * docs: sync minimax m2.7 references * fix: harden Windows Parallels smoke installs * docs: reorder unreleased changelog by user impact * refactor: remove embedded runner cwd mutation * Infra: support shell carrier allow-always approvals * refactor: centralize bootstrap profile handling * refactor: reuse canonical setup bootstrap profile * fix(plugin-sdk): resolve hashed diagnostic events chunks * fix(plugin-sdk): normalize hashed diagnostic event exports * test: fix ci env-sensitive assertions * fix(gateway): fail closed on unresolved discovery endpoints * feat: add slash plugin installs * fix(media): block remote-host file URLs in loaders * fix(media): harden secondary local path seams * test: harden no-isolate reply teardown * docs(changelog): add Windows media security fix * refactor(gateway): centralize discovery target handling * test: narrow live transcript scaffolding strip * test: fix ci docs drift and bun qr exit handling * fix(browser): enforce node browser proxy allowProfiles * refactor(media): share local file access guards * test: stabilize ci test harnesses * test: harden no-isolate test module resets * fix(plugins): preserve live hook registry during gateway runs * test: fix channel summary registry setup * test: harden isolated test mocks * chore(plugins): remove opik investigation checkpoints * ACPX: align pinned runtime version (openclaw#52730) * ACPX: align pinned runtime version * ACPX: drop version example from help text * test: stop leaking image workspace temp dirs * fix(android): gate canvas bridge to trusted pages (openclaw#52722) * fix(android): gate canvas bridge to trusted pages * fix(changelog): note android canvas bridge gating * Update apps/android/app/src/main/java/ai/openclaw/app/node/CanvasActionTrust.kt Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com> * fix(android): snapshot canvas URL on UI thread --------- Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com> * test: isolate base vitest thread blockers * fix: sync agent and autoreply e2e updates * test: harden no-isolate mocked module resets * docs: reorder unreleased changelog * fix(changelog): note windows media path guardrails (openclaw#52738) * fix: alphabetize web search provider listings * docs: clarify unreleased breaking changes * test: harden ci isolated mocks * fix: align websocket stream fallback types * test: finish no-isolate suite hardening * style: format image-generation runtime tests * fix(memory-core): register memory tools independently to prevent coupled failure (openclaw#52668) Merged via admin squash because current required CI failures are inherited from base and match latest `main` failures outside this PR's `memory-core` surface. Prepared head SHA: df7f968 Co-authored-by: artwalker <[email protected]> Reviewed-by: @frankekn * fix(status): recompute fallback context window (openclaw#51795) * fix(status): recompute fallback context window * fix(status): keep live context token caps on fallback * fix(status): preserve fallback runtime context windows * fix(status): preserve configured fallback context caps * fix(status): keep provider-aware transcript context lookups * fix(status): preserve explicit fallback context caps * fix(status): clamp fallback configured context caps * fix(status): keep raw runtime slash ids * fix(status): refresh plugin-sdk api baseline * fix(status): preserve fallback context lookup * test(status): refresh plugin-sdk api baseline * fix(status): keep runtime slash-id context lookup --------- Co-authored-by: create <[email protected]> Co-authored-by: Frank Yang <[email protected]> Co-authored-by: RichardCao <[email protected]> * fix(telegram): make buttons schema optional in message tool The Telegram plugin injects a `buttons` property into the message tool schema via `createMessageToolButtonsSchema()`, but without wrapping it in `Type.Optional()`. This causes TypeBox to include `buttons` in the JSON Schema `required` array. In isolated sessions (e.g. cron jobs) where no `currentChannel` is set, all plugin schemas are merged into the message tool. When the LLM calls the message tool without a `buttons` parameter, AJV validation fails with: `buttons: must have required property 'buttons'`. Wrap the buttons schema in `Type.Optional()` so it is not required. * fix: keep message-tool buttons optional for Telegram and Mattermost (openclaw#52589) (thanks @tylerliu612) * test: update codex test fixtures to gpt-5.4 * fix: repair runtime seams after rebase * fix: restore Telegram topic announce delivery (openclaw#51688) (thanks @mvanhorn) When `replyLike.text` or `replyLike.caption` is an unexpected non-string value (edge case from some Telegram API responses), the reply body was coerced to "[object Object]" via string concatenation. Add a `typeof === "string"` guard to gracefully fall back to empty string, matching the existing pattern used for `quoteText` in the same function. Co-authored-by: Penchan <[email protected]> * docs: sync generated release baselines * test: isolate pi embedded model thread fixtures * fix: restore provider runtime lazy boundary * fix: preserve Telegram reply context text (openclaw#50500) (thanks @p3nchan) * fix: guard Telegram reply context text (openclaw#50500) (thanks @p3nchan) * fix: preserve Telegram reply caption fallback (openclaw#50500) (thanks @p3nchan) --------- Co-authored-by: Ayaan Zaidi <[email protected]> * fix: harden gateway SIGTERM shutdown (openclaw#51242) (thanks @juliabush) * fix: increase shutdown timeout to avoid SIGTERM hang * fix(telegram): abort polling fetch on shutdown to prevent SIGTERM hang * fix(gateway): enforce hard exit on shutdown timeout for SIGTERM * fix: tighten gateway shutdown watchdog * fix: harden gateway SIGTERM shutdown (openclaw#51242) (thanks @juliabush) --------- Co-authored-by: Ayaan Zaidi <[email protected]> * build: prepare 2026.3.22-beta.1 * fix: restore provider runtime lazy boundary * test: add parallels npm update smoke * test: split pi embedded model thread fixtures * fix: stop browser server tests from launching real chrome * test: stabilize live provider docker probes * fix: restart windows gateway after npm update * test: isolate server-context browser harness imports * test: inject model runtime hooks for thread-safe tests * test: snapshot ci timeout investigation * test: target gemini 3.1 flash alias * test: stabilize trigger handling and hook e2e tests * build: prepare 2026.3.22 * test: harden channel suite isolation * test: inject thread-safe deps for agent tools * test: raise timeout for slow provider auth normalization * ci: stabilize windows and bun unit lanes * test: inject thread-safe gateway and ACP seams * test: isolate pi model and reset-model thread fixtures * build: prepare 2026.3.23 * test: inject image-tool provider deps for raw threads * test: stabilize e2e module isolation * test: decouple vitest config checks from ambient env * fix: harden parallels smoke agent invocation * test: avoid repo-root perf profile artifacts * test: inject thread-safe base seams * fix: document Telegram asDocument alias (openclaw#52461) (thanks @bakhtiersizhaev) * feat(telegram): add asDocument param to message tool Adds `asDocument` as a user-facing alias for the existing `forceDocument` parameter in the message tool. When set to `true`, media files (images, videos, GIFs) are sent via `sendDocument` instead of `sendPhoto`/ `sendVideo`/`sendAnimation`, preserving the original file quality without Telegram compression. This is useful when agents need to deliver high-resolution images or uncompressed files to users via Telegram. `asDocument` is intentionally an alias rather than a replacement — the existing `forceDocument` continues to work unchanged. Changes: - src/agents/tools/message-tool.ts: add asDocument to send schema - src/agents/tools/telegram-actions.ts: OR asDocument into forceDocument - src/infra/outbound/message-action-runner.ts: same OR logic for outbound path - extensions/telegram/src/channel-actions.ts: read and forward asDocument - src/channels/plugins/actions/actions.test.ts: add test case * fix: restore channel-actions.ts to main version (rebase conflict fix) * fix(test): match asDocument test payload to actual params structure * fix(telegram): preserve forceDocument alias semantics * fix: document Telegram asDocument alias (openclaw#52461) (thanks @bakhtiersizhaev) --------- Co-authored-by: Бахтиер Сижаев <[email protected]> Co-authored-by: Ayaan Zaidi <[email protected]> * fix: refactor deepseek bundled plugin (openclaw#48762) (thanks @07akioni) * fix: declare typebox runtime dep for mattermost plugin * test: reset line webhook mocks between cases * test: split attempt spawn-workspace thread fixtures * test: remove replaced spawn-workspace monolith * refactor: isolate attempt context engine thread helpers * CI: remove npm release preview workflow (openclaw#52825) * CI: remove npm release preview workflow * Docs: align release maintainer skill with manual publish * Docs: expand release maintainer skill flow * test: stabilize gateway thread harness * test: fix status plugin pagination expectation * test: harden channel suite isolation * build: sync lockfile for mattermost plugin * fix: ensure env proxy dispatcher before MiniMax and OpenAI Codex OAuth flows (openclaw#52228) Verified: - pnpm install --frozen-lockfile - NPM_CONFIG_CACHE=/tmp/openclaw-npm-cache-52228 pnpm build - pnpm check - pnpm test:macmini (failed on inherited pre-existing plugin contract test: src/plugins/contracts/registry.contract.test.ts missing deepseek in bundled provider contract registry outside this PR surface) Co-authored-by: openperf <[email protected]> Co-authored-by: Tak Hoffman <[email protected]> * fix: restore ci gates * test: stabilize channel ci gate * docs: refresh generated config baseline * release: verify control-ui assets are included in npm tarball * release-check: include stderr/stdout when npm pack fails * release: add changelog for control UI tarball check * fix: keep session transcript pointers fresh after compaction (openclaw#50688) Co-authored-by: Frank Yang <[email protected]> * fix(msteams): isolate probe test env credentials * release: automate macOS publishing (openclaw#52853) * release: automate macOS publishing * release: keep mac appcast in openclaw repo * release: add preflight-only release workflow runs * release: keep appcast updates manual * release: generate signed appcast as workflow artifact * release: require preflight before publish * release: require mac app for every release * docs: clarify every release ships mac app * release: document Sparkle feed and SHA rules * release: keep publish flow tag-based * release: stabilize mac appcast flow * release: document local mac fallback * Update CHANGELOG.md * Improve PR template regression prompts * fix(agents): preserve anthropic thinking block order (openclaw#52961) * fix(release): ship bundled plugins in pack artifacts * fix(config): keep built-in channels out of plugin allowlists (openclaw#52964) * fix(config): keep built-in channels out of plugin allowlists * docs(changelog): note doctor whatsapp allowlist fix * docs(changelog): move doctor whatsapp fix to top * Update CHANGELOG.md * fix(config): keep built-in auto-enable idempotent * fix(release): preserve shipped channel surfaces in npm tar (openclaw#52913) * fix(channels): ship official channel catalog (openclaw#52838) * fix(release): keep shipped bundles in npm tar (openclaw#52838) * build(release): fix rebased release-check helpers (openclaw#52838) * fix(gateway): harden supervised lock and browser attach readiness * fix(matrix): avoid duplicate runtime api exports * fix(gateway): avoid probe false negatives after connect * docs(changelog): note release and matrix fixes * fix(plugins): unblock Discord/Slack message tool sends and Feishu media (openclaw#52991) * fix(plugins): unblock Discord and Slack message tool payloads * docs(changelog): note Discord Slack and Feishu message fixes * fix(channels): preserve external catalog overrides (openclaw#52988) * fix(channels): preserve external catalog overrides * fix(channels): clarify catalog precedence * fix(channels): respect overridden install specs * fix(gateway): require admin for agent session reset * fix(voice-call): stabilize plivo v2 replay keys * fix(gateway): require auth for canvas routes * fix(clawhub): resolve auth token for skill browsing (openclaw#53017) * fix(clawhub): resolve auth token for skill browsing * docs(changelog): note clawhub skill auth fix * fix(release): raise npm pack size budget * Tests: fix fresh-main regressions (openclaw#53011) * Tests: fix fresh-main regressions * Tests: avoid chat notice cache priming --------- Co-authored-by: Vincent Koc <[email protected]> * fix(config): ignore stale plugin allow entries * fix(browser): reuse running loopback browser after probe miss * fix(clawhub): honor macOS auth config path (openclaw#53034) * docs: fix nav ordering, missing pages, and stale model references - Sort providers alphabetically in docs.json nav - Sort channels alphabetically in docs.json nav (slack before synology-chat) - Add install/migrating-matrix to Maintenance nav section (was orphaned) - Remove zh-CN/plugins/architecture from nav (file does not exist) - Add Voice Call to channels index page - Add missing providers to providers index (DeepSeek, GitHub Copilot, OpenCode Go, Synthetic) - Sort providers index alphabetically - Update stale claude-3-5-sonnet model reference to claude-sonnet-4-6 in webhook docs * fix(clawhub): preserve XDG auth path on macOS * Agents: fix runtime web_search provider selection (openclaw#53020) Co-authored-by: Vincent Koc <[email protected]> * docs: fix CLI command tree, SDK import path, and tool group listing - Remove non-existent 'secrets migrate' from CLI command tree - Add actual secrets subcommands: audit, configure, apply - Add missing plugin subcommands: inspect, uninstall, update, marketplace list - Fix plugins info -> inspect (actual command name) - Add message send and broadcast subcommands to command tree - Remove misleading deprecated import from sdk-overview - Add sessions_yield and subagents to group:sessions tool group docs - Fix formatting * fix(gateway): guard openrouter auto pricing recursion (openclaw#53055) * test: refresh thread-safe agent fixtures * Release: fix npm release preflight under pnpm (openclaw#52985) Co-authored-by: Vincent Koc <[email protected]> * docs(changelog): add channel catalog override note (openclaw#52988) (openclaw#53059) * fix: harden update dev switch and refresh changelog * fix(mistral): repair max-token defaults and doctor migration (openclaw#53054) * fix(mistral): repair max-token defaults and doctor migration * fix(mistral): add missing small-model repair cap * fix(plugins): enable bundled Brave web search plugin by default (openclaw#52072) Brave is a bundled web search plugin but was missing from BUNDLED_ENABLED_BY_DEFAULT, causing it to be filtered out during provider resolution. This made web_search unavailable even when plugins.entries.brave.enabled was configured. Fixes openclaw#51937 Co-authored-by: Ubuntu <[email protected]> Co-authored-by: Vincent Koc <[email protected]> * fix(release): fail empty control ui tarballs * Revert "fix(plugins): enable bundled Brave web search plugin by default (openclaw#52072)" This reverts commit 0ea3c4d. * Telegram: preserve inbound debounce order * Telegram: fix fire-and-forget debounce order * fix(reply): refresh followup drain callbacks * Update CHANGELOG.md * fix(reply): preserve no-debounce inbound concurrency * fix(reply): clear idle followup callbacks * fix(inbound): bound tracked debounce keys * fix: preserve debounce and followup ordering (openclaw#52998) (thanks @osolmaz) * fix(discord): reply on native command auth failures (openclaw#53072) * docs(changelog): add missing recent fixes * fix: bound tracked debounce key accounting * fix packaged control ui asset lookup (openclaw#53081) * fix(cli): preserve posix default git dir * build: prepare 2026.3.23-beta.1 * test: harden canvas host undici isolation * docs(changelog): credit web search runtime fix * fix(openai-codex): bootstrap proxy on oauth refresh (openclaw#53078) Verified: - pnpm install --frozen-lockfile - pnpm exec vitest run extensions/openai/openai-codex-provider.runtime.test.ts extensions/openai/openai-provider.test.ts * release: harden preflight workflows (openclaw#53087) * release: harden preflight-only workflows * release: require main for publish runs * release: select xcode for macos workflow * release: retry flaky macos preflight steps * ci: shard bun test lane * Fix Control UI operator.read scope handling (openclaw#53110) Preserve Control UI scopes through the device-auth bypass path, normalize implied operator device-auth scopes, ignore cached under-scoped operator tokens, and degrade read-backed main pages gracefully when a connection truly lacks operator.read. Co-authored-by: Val Alexander <[email protected]> * build: prepare 2026.3.23 * fix(agents): prefer runtime snapshot for skill secrets * docs(changelog): note skill secretref runtime fix * fix(memory): bootstrap lancedb runtime on demand (openclaw#53111) Bootstrap LanceDB into plugin runtime state on first use for packaged/global installs, keep @lancedb/lancedb plugin-local, and add regression coverage for bundled, cached, retry, and Nix fail-fast runtime paths. Co-authored-by: Val Alexander <[email protected]> * build: finalize 2026.3.23 release * release: upload macos preflight artifacts (openclaw#53105) * release: upload macos preflight artifacts * release: speed up macos preflight * release: use xlarge macos runner * release: skip dmg path in macos preflight * fix(subagents): recheck timed-out announce waits (openclaw#53127) Recheck timed-out subagent announce waits against the latest runtime snapshot before announcing timeout, and keep that recheck best-effort so transient gateway failures do not suppress the announcement. Co-authored-by: Val Alexander <[email protected]> * docs(feishu): replace botName with name in config examples (openclaw#52753) Merged via squash. Prepared head SHA: 5237726 Co-authored-by: haroldfabla2-hue <[email protected]> Co-authored-by: altaywtf <[email protected]> Reviewed-by: @altaywtf * fix(plugins): accept clawhub uninstall specs * test(auth): align device scope expectations (openclaw#53151) * fix: prevent delivery-mirror re-delivery and raise Slack chunk limit (openclaw#45489) Merged via squash. Prepared head SHA: c7664c7 Co-authored-by: theo674 <[email protected]> Co-authored-by: altaywtf <[email protected]> Reviewed-by: @altaywtf * Infra: tighten shell-wrapper positional-argv allowlist matching (openclaw#53133) * Infra: tighten shell carrier allowlist matching * fix(security): tighten shell carrier allowlist matcher * fix: generalize api_error detection for fallback model triggering (openclaw#49611) Co-authored-by: Ayush Ojha <[email protected]> Co-authored-by: altaywtf <[email protected]> * feat(modelstudio): add standard (pay-as-you-go) DashScope endpoints for Qwen (openclaw#43878) Add Standard API Key auth methods for China (dashscope.aliyuncs.com) and Global/Intl (dashscope-intl.aliyuncs.com) pay-as-you-go endpoints alongside the existing Coding Plan (subscription) endpoints. Also updates group label to 'Qwen (Alibaba Cloud Model Studio)' and fixes glm-4.7 -> glm-5 in Coding Plan note messages. Co-authored-by: wenmeng zhou <[email protected]> * Release: privatize macOS publish flow (openclaw#53166) * fix(diagnostics): redact credentials from cache-trace diagnostic output Refs openclaw#53103 * Release: document manual macOS asset upload (openclaw#53178) * Release: document manual macOS asset upload * Release: document macOS smoke-test mode * docs(changelog): reorder release highlights * test(whatsapp): stabilize login coverage in shared workers * test(whatsapp): preserve session exports in login coverage * test(whatsapp): preserve media test module exports * test(whatsapp): preserve harness session exports * fix(ci): stabilize whatsapp extension checks * test: make update-cli checkout path assertion platform-safe * fix(auth): prevent stale auth store reverts (openclaw#53211) * Doctor: prune stale plugin allowlist and entry refs (openclaw#53187) Signed-off-by: sallyom <[email protected]> * test: stabilize test isolation * test: update command coverage * test: expand gemini live transcript stripping * test: fix update-cli default path assertion * chore(sre:PLA-920): adopt upstream sync changes * fix(sre:PLA-920): align branch with adopted upstream tree * build(sre:PLA-920): refresh dist artifacts * test(sre:PLA-920): align incident-format expectations --------- Signed-off-by: sallyom <[email protected]> Co-authored-by: Vincent Koc <[email protected]> Co-authored-by: Peter Steinberger <[email protected]> Co-authored-by: Rick_Xu <[email protected]> Co-authored-by: rcrick <[email protected]> Co-authored-by: frankekn <[email protected]> Co-authored-by: oliviareid-svg <[email protected]> Co-authored-by: oliviareid-svg <[email protected]> Co-authored-by: Frank <[email protected]> Co-authored-by: scoootscooob <[email protected]> Co-authored-by: ruochen <[email protected]> Co-authored-by: Onur Solmaz <[email protected]> Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com> Co-authored-by: Frank Yang <[email protected]> Co-authored-by: artwalker <[email protected]> Co-authored-by: RichardCao <[email protected]> Co-authored-by: create <[email protected]> Co-authored-by: RichardCao <[email protected]> Co-authored-by: liuyang <[email protected]> Co-authored-by: Ayaan Zaidi <[email protected]> Co-authored-by: Matt Van Horn <[email protected]> Co-authored-by: Penchan <[email protected]> Co-authored-by: Penchan <[email protected]> Co-authored-by: Julia Bush <[email protected]> Co-authored-by: Bakhtier Sizhaev <[email protected]> Co-authored-by: Бахтиер Сижаев <[email protected]> Co-authored-by: wangchunyue <[email protected]> Co-authored-by: Tak Hoffman <[email protected]> Co-authored-by: evann <[email protected]> Co-authored-by: Robin Waslander <[email protected]> Co-authored-by: Sathvik Veerapaneni <[email protected]> Co-authored-by: Nimrod Gutman <[email protected]> Co-authored-by: Luke <[email protected]> Co-authored-by: scoootscooob <[email protected]> Co-authored-by: Jamil Zakirov <[email protected]> Co-authored-by: TheRipper <[email protected]> Co-authored-by: Quinn H. <[email protected]> Co-authored-by: Ubuntu <[email protected]> Co-authored-by: Val Alexander <[email protected]> Co-authored-by: betoblair <[email protected]> Co-authored-by: haroldfabla2-hue <[email protected]> Co-authored-by: altaywtf <[email protected]> Co-authored-by: Altay <[email protected]> Co-authored-by: theo674 <[email protected]> Co-authored-by: theo674 <[email protected]> Co-authored-by: Ayush Ojha <[email protected]> Co-authored-by: Ayush Ojha <[email protected]> Co-authored-by: George Zhang <[email protected]> Co-authored-by: wenmeng zhou <[email protected]> Co-authored-by: Onur <[email protected]> Co-authored-by: Sally O'Malley <[email protected]>

…osolmaz

…osolmaz) (cherry picked from commit 1b69d9e)

openclaw-barnacle bot added the channel: telegram Channel integration: telegram label Mar 23, 2026

chatgpt-codex-connector bot reviewed Mar 23, 2026

View reviewed changes

src/auto-reply/inbound-debounce.ts Outdated Show resolved Hide resolved

openclaw-barnacle bot added size: M maintainer Maintainer-authored PR labels Mar 23, 2026

vincentkoc self-assigned this Mar 23, 2026

vincentkoc mentioned this pull request Mar 23, 2026

fix(reply): preserve debounced followup ordering #53001

Closed

chatgpt-codex-connector bot reviewed Mar 23, 2026

View reviewed changes

src/auto-reply/reply/agent-runner.ts Outdated Show resolved Hide resolved

openclaw-barnacle bot added size: L and removed size: M labels Mar 23, 2026

osolmaz and others added 7 commits March 23, 2026 10:59

Telegram: preserve inbound debounce order

a6144dd

Telegram: fix fire-and-forget debounce order

c9c6e51

fix(reply): refresh followup drain callbacks

be698c5

Update CHANGELOG.md

3b6125a

fix(reply): preserve no-debounce inbound concurrency

3ac2b9e

fix(reply): clear idle followup callbacks

aedde5a

fix(inbound): bound tracked debounce keys

1168c3b

jacobtomlinson reviewed Mar 23, 2026

View reviewed changes

fix: preserve debounce and followup ordering (#52998) (thanks @osolmaz)

af20938

steipete force-pushed the codex/telegram-inbound-desync branch from f9fbcab to af20938 Compare March 23, 2026 18:11

steipete merged commit 1b69d9e into main Mar 23, 2026
7 checks passed

steipete deleted the codex/telegram-inbound-desync branch March 23, 2026 18:11

chatgpt-codex-connector bot reviewed Mar 23, 2026

View reviewed changes

github-actions bot mentioned this pull request Mar 23, 2026

📡 Upstream Digest — 2026-03-23 18:42 UTC curtismercier/openclaw-mods#344

Open

alexey-pelykh mentioned this pull request Mar 23, 2026

Cherry-pick: Inbound debounce + reply/followup ordering (8 commits) remoteclaw/remoteclaw#1856

Closed

4 tasks

iclem pushed a commit to iclem/openclaw that referenced this pull request Mar 23, 2026

fix: preserve debounce and followup ordering (openclaw#52998) (thanks @…

9422a1c

…osolmaz)

alexey-pelykh mentioned this pull request Mar 23, 2026

Cherry-pick: Auto-reply and conversation handling (1/2) (50 commits) remoteclaw/remoteclaw#1896

Closed

hzq001 pushed a commit to hzq001/openclaw that referenced this pull request Mar 24, 2026

fix: preserve debounce and followup ordering (openclaw#52998) (thanks @…

343e5fe

…osolmaz)

furaul pushed a commit to furaul/openclaw that referenced this pull request Mar 24, 2026

fix: preserve debounce and followup ordering (openclaw#52998) (thanks @…

1716824

…osolmaz)

Arry8 pushed a commit to Arry8/openclaw that referenced this pull request Mar 25, 2026

fix: preserve debounce and followup ordering (openclaw#52998) (thanks @…

6147a32

…osolmaz)

netandreus pushed a commit to netandreus/openclaw that referenced this pull request Mar 25, 2026

fix: preserve debounce and followup ordering (openclaw#52998) (thanks @…

a7366dc

…osolmaz)

npmisantosh pushed a commit to npmisantosh/openclaw that referenced this pull request Mar 25, 2026

fix: preserve debounce and followup ordering (openclaw#52998) (thanks @…

dfdb0eb

…osolmaz)

Interstellar-code pushed a commit to Interstellar-code/operator1 that referenced this pull request Apr 2, 2026

fix: preserve debounce and followup ordering (openclaw#52998) (thanks @…

d704422

…osolmaz) (cherry picked from commit 1b69d9e)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(telegram): preserve inbound debounce order#52998

fix(telegram): preserve inbound debounce order#52998
steipete merged 8 commits intomainfrom
codex/telegram-inbound-desync

osolmaz commented Mar 23, 2026

Uh oh!

aisle-research-bot bot commented Mar 23, 2026 •

edited

Loading

Uh oh!

greptile-apps bot commented Mar 23, 2026

Uh oh!

chatgpt-codex-connector bot left a comment

Uh oh!

Uh oh!

vincentkoc commented Mar 23, 2026

Uh oh!

chatgpt-codex-connector bot left a comment

Uh oh!

Uh oh!

vincentkoc commented Mar 23, 2026

Uh oh!

jacobtomlinson left a comment

Uh oh!

Uh oh!

steipete commented Mar 23, 2026

Uh oh!

chatgpt-codex-connector bot left a comment

Uh oh!

chatgpt-codex-connector bot Mar 23, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Conversation

osolmaz commented Mar 23, 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!

aisle-research-bot bot commented Mar 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔒 Aisle Security Analysis

1. 🔵 Follow-up queue can become stuck when enqueued with restartIfIdle=false (potential DoS)

Description

Recommendation

Uh oh!

greptile-apps bot commented Mar 23, 2026

Greptile Summary

Confidence Score: 5/5

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

vincentkoc commented Mar 23, 2026

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

vincentkoc commented Mar 23, 2026

Uh oh!

jacobtomlinson left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

steipete commented Mar 23, 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 23, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

aisle-research-bot bot commented Mar 23, 2026 •

edited

Loading