Skip to content

fix(cron): suppress delivery when [SILENT] appears anywhere in response#5654

Merged
teknium1 merged 1 commit intoNousResearch:mainfrom
auspic7:fix/cron-silent-marker-suppression
Apr 6, 2026
Merged

fix(cron): suppress delivery when [SILENT] appears anywhere in response#5654
teknium1 merged 1 commit intoNousResearch:mainfrom
auspic7:fix/cron-silent-marker-suppression

Conversation

@auspic7
Copy link
Copy Markdown
Contributor

@auspic7 auspic7 commented Apr 6, 2026

Problem

The scheduler checked startswith('[SILENT]') to suppress delivery, but agents sometimes append [SILENT] after an explanation rather than responding with it alone:

2 deals filtered out (like<10, reply<15).

[SILENT]

This caused the message to be delivered despite the intent to suppress it.

Fix

Changed startswith(SILENT_MARKER) to SILENT_MARKER in ... so the marker is caught regardless of its position in the response.

Test

Added test_silent_trailing_suppresses_delivery to TestSilentDelivery — covers the case where [SILENT] is appended after content rather than leading the response.

Previously the scheduler checked startswith('[SILENT]'), so agents that
appended [SILENT] after an explanation (e.g. 'N items filtered.\n\n[SILENT]')
would still trigger delivery.

Change the check to 'in' so the marker is caught regardless of position.
Add test_silent_trailing_suppresses_delivery to cover this case.
@teknium1 teknium1 merged commit ea16949 into NousResearch:main Apr 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants