Cron issue
Problem
When using isolated cron jobs with
deliver: true, the agent sometimes narrates its process before outputting the actual message. This internal thinking gets delivered to external channels (Signal, Telegram, etc.), which is embarrassing and confusing for recipients.Example - a skoleintra cron job sent this to a family Signal group:
I have Vincent's schedule. Now let me switch to Alvin to get his schedule.>
Now I have all the information. Let me send the morning message.>
Mandag 12. januar
[actual formatted message...]
The first two lines are the agent thinking out loud, not intended output.
Expected Behavior
This should just work. The agent should know from context (deliver: true, provider, destination) that its output goes directly to an external channel - and behave accordingly without needing explicit instructions.
The payload already contains
deliver, provider, and to - the agent has all the information it needs to understand the situation.Current Workaround
Adding verbose warnings to every cron prompt:
CRITICAL: Your ENTIRE response will be sent directly to a family Signal group.
Do NOT include ANY thinking, commentary, or process updates.
Output ONLY the final formatted message.
This works but shouldn't be necessary.
Suggested Solution
Inject context into the system prompt for isolated sessions when
deliver: true. Something like:"This is an automated task. Your response will be delivered directly to [provider] ([destination]). Output only the final message - no thinking, commentary, or process updates."
The agent already has access to the delivery config - it just needs to be made aware of what that means.
