fix: suppress HEARTBEAT_OK responses from cron job output - #4
Merged
Conversation
eddmann
force-pushed
the
claude/debug-cron-heartbeat-SAw6t
branch
from
February 25, 2026 21:59
347df89 to
34a234d
Compare
eddmann
force-pushed
the
claude/debug-cron-heartbeat-SAw6t
branch
from
February 25, 2026 22:01
34a234d to
2b1e9ef
Compare
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
2 participants
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.
The HeartbeatRunner correctly suppresses HEARTBEAT_OK responses, but
the cron scheduler callback was blindly forwarding all agent responses
to Telegram. This caused noisy "[Cron: Reminder check] HEARTBEAT_OK"
messages whenever a cron job's agent run had nothing to report.
https://claude.ai/code/session_01MdQSLKGgkFaBJvzfVVkja8