Skip to content

The agent that grows with you

fix(cron): say a local chat's default delivery lands as a note

unsupportedpastels60d1ecb58f52
diff --git a/tools/cronjob_tools.py b/tools/cronjob_tools.py
index 2a9ef915263..4ddee5a0e34 100644
--- a/tools/cronjob_tools.py
+++ b/tools/cronjob_tools.py
@@ -1094,7 +1094,7 @@ Jobs run in a fresh session with no current-chat context, so prompts must be sel
},
"deliver": {
"type": "string",
- "description": "Where the job's output is POSTED as a one-way message (the job itself always runs in a fresh session with no chat context). Omit to address the chat/topic this job was created from. Otherwise: 'local' (save only, no delivery), 'all' (every connected home channel, resolved at fire time), 'bot-chat' or 'bot-chat:<profile>' (inject into a Bot Chat as a real message), or platform:chat_id:thread_id (e.g. 'telegram:-1001234567890:17585'). Comma-combine like 'origin,all'. A CLI or TUI session has no channel back into the chat: there the default only saves output (see action='list'), so to notify the user target a gateway-connected platform (e.g. 'telegram' or 'all'), and never promise a default-deliver job will message them in that session."
+ "description": "Where the job's output is POSTED as a one-way message (the job itself always runs in a fresh session with no chat context). Omit to address the chat/topic this job was created from. Otherwise: 'local' (save only, no delivery), 'all' (every connected home channel, resolved at fire time), 'bot-chat' or 'bot-chat:<profile>' (inject into a Bot Chat as a real message), or platform:chat_id:thread_id (e.g. 'telegram:-1001234567890:17585'). Comma-combine like 'origin,all'. From a local chat (CLI, TUI or Desktop) the default writes the result into that chat's history as a note, seen when the chat is reopened and by its next turn, not as a live message."
},
"failure_deliver": {
"type": "string",