Summary

• Add support for NO_REPLY (SILENT_REPLY_TOKEN) in cron isolated jobs to skip message delivery
• Previously only HEARTBEAT_OK was recognized, causing "request ended without sending any chunks" errors when AI responded with NO_REPLY

Problem

Cron isolated jobs with delivery.mode: "announce" would fail when the AI responded with NO_REPLY because:

1. The isHeartbeatOnlyResponse function only checked for HEARTBEAT_OK
2. NO_REPLY is the standard silent reply token used elsewhere in the codebase
3. This inconsistency caused the system to attempt delivery of "NO_REPLY" text, leading to errors

Changes

• src/cron/isolated-agent/helpers.ts: Import and check for SILENT_REPLY_TOKEN in isHeartbeatOnlyResponse
• src/cron/isolated-agent.delivers-response-has-heartbeat-ok-but-includes.test.ts: Add tests for NO_REPLY handling

Testing

• Added test: "skips delivery when response is NO_REPLY"
• Added test: "delivers when response has NO_REPLY but includes media"
• All existing tests pass

Related

This makes cron job behavior consistent with other parts of the system that already support NO_REPLY via isSilentReplyText().

Greptile Overview

Greptile Summary

• Updates cron isolated-agent delivery suppression to treat NO_REPLY (silent reply token) the same as HEARTBEAT_OK for text-only responses.
• Adds regression tests ensuring NO_REPLY skips delivery while still delivering when media is present.
• Keeps existing heartbeat/ackMaxChars behavior unchanged, aligning cron isolated jobs with the rest of the auto-reply pipeline’s silent-reply handling.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk.
• The change is narrowly scoped (adds an additional skip condition for a known token), preserves existing heartbeat behavior, and includes deterministic tests covering the new NO_REPLY cases (with and without media). No other call paths are affected beyond the intended cron isolated-agent delivery gating.
• No files require special attention

_{(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!}

Context used:

• Context from dashboard - CLAUDE.md (source)
• Context from dashboard - AGENTS.md (source)