fix(heartbeat): suppress no-op system event replies by pfrederiksen · Pull Request #73785 · openclaw/openclaw

pfrederiksen · 2026-04-28T20:08:48Z

Summary

add centralized no-op sentinel detection for silent heartbeat/system-event replies
suppress exact HEARTBEAT_OK, NO_REPLY, NO_NEW_AUDIO, and SESSION_WATCHDOG_OK outputs before delivery
keep meaningful relayable exec summaries deliverable without moving cron events out of heartbeat-mode ack suppression
preserve newer heartbeat prefix/model-selection behavior after rebasing onto current origin/main

Real behavior proof

Behavior or issue addressed: Heartbeat/system-event handoffs could visibly deliver no-op sentinel replies such as exact HEARTBEAT_OK, while still needing to deliver meaningful exec/system-event summaries.
Real environment tested: Local OpenClaw checkout for PR fix(heartbeat): suppress no-op system event replies #73785 on Linux/Node 22 after rebasing onto current origin/main at 3de97057d0.
Exact steps or command run after this patch: Ran node --import tsx tmp/pr73785-runtime-proof.mjs from the patched checkout. The script imported the patched runHeartbeatOnce, used the real in-process system-event queue, registered the channel plugin send path with outbound capture, seeded a real file-backed session store, and exercised both cron-event and exec-event paths.

Evidence after fix: Terminal output copied from the after-fix proof command:

{
  "cron": {
    "name": "cron",
    "result": {
      "status": "ran",
      "durationMs": 27
    },
    "provider": "cron-event",
    "sent": []
  },
  "exec": {
    "name": "exec",
    "result": {
      "status": "ran",
      "durationMs": 1257
    },
    "provider": "exec-event",
    "sent": [
      {
        "to": "[email protected]",
        "text": "Command completed: uploaded report.txt"
      }
    ]
  }
}

Observed result after fix: A cron-event reply of HEARTBEAT_OK Watchdog clean stayed in heartbeat-mode short-ack suppression and produced no outbound send. A meaningful exec-event reply still crossed the send boundary as Command completed: uploaded report.txt.
What was not tested: No real WhatsApp or Telegram message was sent; the proof used a dummy WhatsApp group id and captured the outbound send locally to avoid test noise in real channels.

Validation

CI=true pnpm exec oxfmt --check src/agents/model-runtime-policy.test.ts extensions/telegram/src/polling-session.ts src/auto-reply/tokens.ts src/infra/heartbeat-runner.ts src/infra/heartbeat-runner.respects-ackmaxchars-heartbeat-acks.test.ts
CI=true pnpm exec oxlint src/agents/model-runtime-policy.test.ts extensions/telegram/src/polling-session.ts src/auto-reply/tokens.ts src/infra/heartbeat-runner.ts src/infra/heartbeat-runner.respects-ackmaxchars-heartbeat-acks.test.ts
CI=true pnpm exec vitest run --config test/vitest/vitest.infra.config.ts src/infra/heartbeat-runner.respects-ackmaxchars-heartbeat-acks.test.ts — 16/16 passed
CI=true pnpm check:test-types
git diff --check

greptile-apps · 2026-04-28T20:11:04Z

Greptile Summary

This PR refactors heartbeat reply suppression by centralizing no-op token detection into isNoOpSentinelReplyText in tokens.ts, then applying it early in normalizeHeartbeatReply before further token stripping. The previous exec-completion exception (!hasExecCompletion in shouldSkipMain and the execFallbackText fallback) is replaced by simply treating system events with the "message" strip mode, so that HEARTBEAT_OK/NO_REPLY/etc. replies are suppressed even for exec events while meaningful summaries are still delivered.

Confidence Score: 5/5

Safe to merge — logic is straightforward, well-tested, and the behavioral change is intentional and correctly implemented.

No P0 or P1 issues found. The sentinel detection is correctly gated, the early-return path in normalizeHeartbeatReply is sound, the removal of the old execFallbackText workaround is clean, and three new test cases validate all key scenarios.

No files require special attention.

_{Reviews (1): Last reviewed commit: "fix(heartbeat): suppress no-op system ev..." | Re-trigger Greptile}

clawsweeper · 2026-04-28T20:49:45Z

Codex review: needs maintainer review before merge. Reviewed July 3, 2026, 4:57 PM ET / 20:57 UTC.

Summary
The PR adds no-op sentinel detection for heartbeat/system-event replies, applies it in heartbeat normalization and exec fallback handling, adds heartbeat regression tests, and includes small Telegram and run-node type fixes.

PR surface: Source +48, Tests +133, Other +1. Total +182 across 5 files.

Reproducibility: yes. from source inspection: current main can strip a pure heartbeat token and then restore it through relayable exec fallback. I did not run a live current-main repro in this read-only pass.

Review metrics: 1 noteworthy metric.

Live mergeability: mergeable=CONFLICTING, mergeStateStatus=DIRTY. Maintainers need a refreshed branch before the exact heartbeat delivery merge result can be reviewed or landed.

Root-cause cluster
Relationship: fixed_by_candidate
Canonical: #73149
Summary: This PR is the candidate fix for the broad cron/heartbeat no-op sentinel leakage report; the open route-matched fallback PR is adjacent message-delivery work, not a replacement.

Members:

canonical: Cron/heartbeat no-op runs can leak visible messages despite silence/no-op semantics #73149 - The PR body uses closing syntax for the broad cron/heartbeat no-op leakage report and directly implements its requested runtime-level suppression.
same_root_cause: [Bug]: relayable exec completion heartbeat leaks HEARTBEAT_OK as user-visible alert #78197 - This closed report isolates relayable exec completion leaking HEARTBEAT_OK through the same fallback behavior changed here.
partial_overlap: fix(heartbeat): suppress fallback after route-matched message tool #84975 - That open PR changes fallback suppression after route-matched message-tool delivery, but it does not add exact no-op sentinel suppression.
adjacent_distinct: fix(heartbeat): align response tool prompts #76458 - That merged heartbeat response-tool prompt fix overlaps the area but explicitly did not replace this no-op sentinel suppression work.
partial_overlap: Control UI leaks internal async completion / heartbeat system messages into chat #72918 - That closed report describes broader internal async/heartbeat text leaking into chat, while this PR is sentinel-specific.

Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

Merge readiness
Overall: 🦐 gold shrimp
Proof: 🦞 diamond lobster ✨ media proof bonus
Patch quality: 🦐 gold shrimp
Result: needs maintainer review before merge.

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

Rank-up moves:

Refresh the branch onto current main while preserving both sentinel suppression and current placeholder-only suppression.
Rerun focused heartbeat regression tests and exact merge-head checks after the refresh.

Risk before merge

[P1] Live GitHub reports the PR as conflicting, so maintainers cannot review or land the exact merge result yet.
[P1] The conflict is in central heartbeat delivery suppression logic; a bad refresh could re-deliver no-op sentinels, drop meaningful exec summaries, or lose current main's internal-placeholder-only suppression.

Maintainer options:

Refresh and validate the heartbeat merge head (recommended)
Resolve the current heartbeat-runner conflict while preserving sentinel suppression and current placeholder suppression, then rerun focused heartbeat tests and exact merge-head checks.
Pause for a heartbeat owner
If nobody can safely refresh central delivery logic, leave the PR paused rather than landing stale message-delivery behavior.

Next step before merge

[P2] Manual review is needed because the remaining blocker is conflict resolution and exact merge-head validation in central heartbeat delivery logic.

Security
Cleared: No concrete security or supply-chain concern was found; the diff does not change dependencies, workflows, secrets handling, package resolution, or privileged execution paths.

Review details

Best possible solution:

Refresh the branch onto current main while preserving both no-op sentinel suppression and current internal-placeholder-only suppression, then rerun focused heartbeat and exact merge-head validation.

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

Yes from source inspection: current main can strip a pure heartbeat token and then restore it through relayable exec fallback. I did not run a live current-main repro in this read-only pass.

Is this the best way to solve the issue?

Yes after refresh: fixing the heartbeat normalization/fallback boundary is narrower and more durable than prompt-only or channel-specific suppression. The conflicted branch cannot be treated as final until it is resolved against current main.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 010b61746379.

Label changes

Label justifications:

P2: The PR addresses a user-visible heartbeat/system-event message leak with limited blast radius and no security or data-loss signal.
merge-risk: 🚨 message-delivery: The unresolved conflict sits in heartbeat delivery suppression logic and can change whether system-event replies are sent or suppressed.
rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🦞 diamond lobster and patch quality is 🦐 gold shrimp.
status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (screenshot): The PR body includes after-fix terminal output for cron and exec paths, and Mantis supplied Telegram Desktop screenshot proof for the visible sentinel behavior.
proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes after-fix terminal output for cron and exec paths, and Mantis supplied Telegram Desktop screenshot proof for the visible sentinel behavior.
proof: 📸 screenshot: Contributor real behavior proof includes screenshot evidence. The PR body includes after-fix terminal output for cron and exec paths, and Mantis supplied Telegram Desktop screenshot proof for the visible sentinel behavior.
mantis: telegram-visible-proof: Mantis should capture Telegram visible proof. The PR changes visible Telegram heartbeat/sentinel delivery behavior that is suitable for Telegram Desktop proof.

Evidence reviewed

PR surface:

Source +48, Tests +133, Other +1. Total +182 across 5 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	3	56	8	+48
Tests	1	134	1	+133
Docs	0	0	0	0
Config	0	0	0	0
Generated	0	0	0	0
Other	1	1	0	+1
Total	5	191	9	+182

What I checked:

Root and scoped policy read: Root, extensions, Telegram, scripts, and agents guidance were read; the review applied the repository policy that heartbeat fallback and message-delivery behavior are merge-risk-sensitive, and Telegram-visible behavior needs real proof. (AGENTS.md:1, 010b61746379)
Live PR state: GitHub reports head 9da5df9 as mergeable=CONFLICTING and mergeStateStatus=DIRTY, so exact merge-head validation cannot be trusted yet. (9da5df9d2d24)
Current main still has the fallback leak shape: Current main still restores original reply text for relayable exec completions when normalization strips to empty, which can re-deliver a pure HEARTBEAT_OK unless the PR's sentinel guard is integrated. (src/infra/heartbeat-runner.ts:2050, 010b61746379)
Current main has adjacent placeholder suppression to preserve: Current main now carries isInternalPlaceholderOnly handling in normalizeHeartbeatReply, so conflict resolution must preserve that newer suppression while adding the PR's sentinel handling. (src/infra/heartbeat-runner.ts:873, 010b61746379)
PR implementation: The PR head adds isNoOpSentinelReplyText, applies it before heartbeat stripping, and prevents exec fallback restoration when the source reply is a no-op sentinel. (src/infra/heartbeat-runner.ts:824, 9da5df9d2d24)
PR regression coverage: The PR adds focused tests for exact no-op sentinels, exec HEARTBEAT_OK suppression, meaningful exec summary delivery, and cron short-ack suppression. (src/infra/heartbeat-runner.respects-ackmaxchars-heartbeat-acks.test.ts:361, 9da5df9d2d24)

Likely related people:

TurboTheTurtle: Authored the current-main stream-error placeholder suppression in the same heartbeat normalization/fallback area that now conflicts with this PR refresh. (role: recent adjacent contributor; confidence: medium; commits: b580258e94e0; files: src/infra/heartbeat-runner.ts, src/infra/heartbeat-runner.tool-response.test.ts)
vincentkoc: Recent work touched heartbeat response-tool prompts, quoted silent-reply handling, and the run-node declaration file adjacent to this PR. (role: adjacent heartbeat and silent-reply contributor; confidence: medium; commits: 877eb1cbed04, 96c6f8022c24, 7546231762ff; files: src/infra/heartbeat-runner.ts, src/auto-reply/tokens.ts, scripts/run-node.d.mts)
steipete: Recent history includes heartbeat scheduler and central runner changes in the same runtime file. (role: recent heartbeat area contributor; confidence: medium; commits: bbc4bee7a22b, 180a970ac045; files: src/infra/heartbeat-runner.ts)
obviyus: Recent Telegram polling-session work touches the plugin file changed by this PR and is relevant to the Telegram-visible proof surface. (role: Telegram adjacent contributor; confidence: medium; commits: b7ec2851f38d; files: extensions/telegram/src/polling-session.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.

pfrederiksen · 2026-05-14T02:33:52Z

@clawsweeper re-review

clawsweeper · 2026-05-14T02:35:28Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

State: Complete
Detail: The targeted re-review finished, the durable review comment was updated, and the synced verdict was routed.
Run: https://github.com/openclaw/clawsweeper/actions/runs/25838305751
Updated: 2026-05-14T02:42:06.742Z

pfrederiksen · 2026-05-15T20:21:03Z

Updated for ClawSweeper’s asks:

Rebased onto current origin/main (0b7ff665f6).
Fixed the P2 by keeping cron events on heartbeat-mode ack suppression; only relayable exec completions use message-mode normalization.
Added regression coverage for cron-event short-ack suppression (HEARTBEAT_OK Watchdog clean now produces no send).
Added a terminal real-behavior proof to the PR body showing cron no-op sends [] while meaningful exec summaries still cross the send boundary.

Validation run:

CI=true pnpm exec oxfmt --check src/auto-reply/tokens.ts src/infra/heartbeat-runner.ts src/infra/heartbeat-runner.respects-ackmaxchars-heartbeat-acks.test.ts
CI=true pnpm exec oxlint src/auto-reply/tokens.ts src/infra/heartbeat-runner.ts src/infra/heartbeat-runner.respects-ackmaxchars-heartbeat-acks.test.ts
CI=true pnpm exec vitest run --config test/vitest/vitest.infra.config.ts src/infra/heartbeat-runner.respects-ackmaxchars-heartbeat-acks.test.ts — 16/16 passed
git diff --check

CI=true pnpm check:test-types currently fails in unrelated current-main fixture src/agents/model-runtime-policy.test.ts because ModelProviderConfig now requires baseUrl.

@clawsweeper re-review

Re-review progress:

State: Failed
Detail: The targeted re-review did not finish cleanly. Check the workflow run for details.
Run: https://github.com/openclaw/clawsweeper/actions/runs/25940581227
Updated: 2026-05-15T20:48:49.694Z

clawsweeper · 2026-05-15T20:22:42Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

State: Complete
Detail: The targeted re-review finished, the durable review comment was updated, and the synced verdict was routed.
Run: https://github.com/openclaw/clawsweeper/actions/runs/25940204673
Updated: 2026-05-15T20:44:15.593Z

pfrederiksen · 2026-05-15T20:23:39Z

@clawsweeper re-review

Updated the PR body with the exact real-behavior proof fields required by the policy and verified it locally with evaluateRealBehaviorProof before posting.

openclaw-barnacle · 2026-06-14T05:04:50Z

This pull request has been automatically marked as stale due to inactivity.
Please add updates or it will be closed.

openclaw-mantis · 2026-06-19T17:17:35Z

Mantis Telegram Desktop Proof

Summary: Mantis captured native Telegram Desktop before/after GIFs showing the no-op heartbeat reply is suppressed in this PR.

Scenario: telegram-desktop-proof
Trigger: pull_request_target
Run: https://github.com/openclaw/openclaw/actions/runs/27832738513
Artifact: https://github.com/openclaw/openclaw/actions/runs/27832738513/artifacts/7755196172
Baseline: pass at 9f30af5a967bbaf85e2754e60ba4f5a1f336fd54, expected baseline visual proof captured
Candidate: pass at 9da5df9d2d247f53e7e2f2b8b0c8cec15b9c0ff6, expected candidate visual proof captured
Overall: true

Main screenshot	This PR screenshot

Main	This PR

Motion-trimmed clips:

Raw QA files: https://artifacts.openclaw.ai/mantis/telegram-desktop/pr-73785/run-27832738513-1/index.json

openclaw-barnacle Bot added the size: S label Apr 28, 2026

pfrederiksen force-pushed the fix/73149-silent-noop-runtime branch 2 times, most recently from 7d4d936 to 4483377 Compare April 28, 2026 20:46

pfrederiksen force-pushed the fix/73149-silent-noop-runtime branch from 4483377 to 2116d31 Compare April 28, 2026 21:07

arcabotai mentioned this pull request May 1, 2026

buildExecEventPrompt: 'user delivery disabled' branch races runtime silent-reply detection, causes incomplete-turn errors #75322

Closed

clawsweeper Bot mentioned this pull request May 3, 2026

fix(heartbeat): suppress silent tokens in streaming replies #76334

Closed

vincentkoc mentioned this pull request May 3, 2026

fix(heartbeat): align response tool prompts #76458

Merged

25 tasks

clawsweeper Bot mentioned this pull request May 6, 2026

[Bug]: relayable exec completion heartbeat leaks HEARTBEAT_OK as user-visible alert #78197

Closed

clawsweeper Bot mentioned this pull request May 13, 2026

[Bug]: Telegram async exec followup leaks HEARTBEAT_OK/internal text after context overflow #74257

Closed

pfrederiksen force-pushed the fix/73149-silent-noop-runtime branch from 2116d31 to 49a3a14 Compare May 14, 2026 05:44

openclaw-barnacle Bot added the proof: supplied External PR includes structured after-fix real behavior proof. label May 14, 2026

pfrederiksen force-pushed the fix/73149-silent-noop-runtime branch from 49a3a14 to 50ec204 Compare May 15, 2026 20:20

openclaw-barnacle Bot added triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. and removed proof: supplied External PR includes structured after-fix real behavior proof. labels May 15, 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 May 15, 2026

clawsweeper Bot added the proof: sufficient ClawSweeper judged the real behavior proof convincing. label May 15, 2026

pfrederiksen force-pushed the fix/73149-silent-noop-runtime branch from 50ec204 to bc82710 Compare May 15, 2026 20:45

openclaw-barnacle Bot added channel: telegram Channel integration: telegram agents Agent runtime and tooling labels May 15, 2026

openclaw-barnacle Bot added stale Marked as stale due to inactivity and removed stale Marked as stale due to inactivity labels Jun 14, 2026

github-actions Bot mentioned this pull request Jun 16, 2026

🦞 OpenClaw 生态日报 2026-06-16 96loveslife/big_model_radar#12

Open

clawsweeper Bot temporarily deployed to qa-live-shared June 19, 2026 14:53 Inactive

clawsweeper Bot added rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. and removed rating: 🦞 diamond lobster Very strong PR readiness with only minor maintainer review expected. labels Jun 29, 2026

clawsweeper Bot mentioned this pull request Jul 1, 2026

fix(heartbeat): suppress fallback after route-matched message tool #84975

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

fix(heartbeat): suppress no-op system event replies#73785

fix(heartbeat): suppress no-op system event replies#73785
pfrederiksen wants to merge 2 commits into
openclaw:mainfrom
pfrederiksen:fix/73149-silent-noop-runtime

pfrederiksen commented Apr 28, 2026 •

edited

Loading

Uh oh!

greptile-apps Bot commented Apr 28, 2026

Uh oh!

clawsweeper Bot commented Apr 28, 2026 •

edited

Loading

Uh oh!

pfrederiksen commented May 14, 2026

Uh oh!

clawsweeper Bot commented May 14, 2026 •

edited

Loading

Uh oh!

pfrederiksen commented May 15, 2026 •

edited by clawsweeper Bot

Loading

Uh oh!

clawsweeper Bot commented May 15, 2026 •

edited

Loading

Uh oh!

pfrederiksen commented May 15, 2026

Uh oh!

openclaw-barnacle Bot commented Jun 14, 2026

Uh oh!

openclaw-mantis Bot commented Jun 19, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Uh oh!

Conversation

pfrederiksen commented Apr 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Real behavior proof

Validation

Uh oh!

greptile-apps Bot commented Apr 28, 2026

Greptile Summary

Confidence Score: 5/5

Uh oh!

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

Uh oh!

Uh oh!

pfrederiksen commented May 14, 2026

Uh oh!

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

Uh oh!

Uh oh!

pfrederiksen commented May 15, 2026 • edited by clawsweeper Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

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

Uh oh!

Uh oh!

pfrederiksen commented May 15, 2026

Uh oh!

openclaw-barnacle Bot commented Jun 14, 2026

Uh oh!

openclaw-mantis Bot commented Jun 19, 2026

Mantis Telegram Desktop Proof

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

pfrederiksen commented Apr 28, 2026 •

edited

Loading

clawsweeper Bot commented Apr 28, 2026 •

edited

Loading

clawsweeper Bot commented May 14, 2026 •

edited

Loading

pfrederiksen commented May 15, 2026 •

edited by clawsweeper Bot

Loading

clawsweeper Bot commented May 15, 2026 •

edited

Loading