openclaw - 💡(How to fix) Fix claw-bridge sends "No further note from me." to Telegram channel after heartbeat completion [1 comments, 2 participants]

Bug Report: `claw-bridge` sends unexplained "No further note from me." message to users

OpenClaw version: 2026.4.26 (be8c246) Platform: macOS Darwin 25.3.0 (arm64) Channel: Telegram

Behavior

After an async command completes (in this case, a heartbeat poll), a message appears in the Telegram channel from `claw-bridge` with the body:

No further note from me.

This message is visible to the end user as a regular chat message.

Expected Behavior

Internal system completion events from `claw-bridge` should not be surfaced to the user as readable messages. If this is intentional framework communication, it should be suppressed at the channel delivery layer or clearly marked as system-only.

Evidence

Confirmed via session trajectory log that none of the model's `assistantTexts` contain this string. All model outputs were either Chinese responses or `HEARTBEAT_OK` / `NO_REPLY`. The message originates exclusively from `claw-bridge`.

Relevant trajectory metadata: ``` sessionId: 2ede077e-c3d8-4adb-876d-56e632a73fed trigger: heartbeat poll completion event sender_label: claw-bridge body: "No further note from me." ```

Reproduction

1. Configure a Telegram channel with heartbeat polling enabled
2. Trigger a heartbeat poll while a background exec session is completing
3. Observe `claw-bridge` message delivered to the Telegram chat

Impact

Confusing UX — users see an unexplained system string as a chat message with no context.