From 157752b4f03d43e9d23d8dc9b17f1b29c61b584c Mon Sep 17 00:00:00 2001 From: "Claudia[bot]" <4437565+Claudia[bot]@users.noreply.github.com> Date: Wed, 21 Oct 2026 08:10:00 +0200 Subject: [PATCH] docs(cron): rewrap the single-line prompt paragraph Co-Authored-By: Christian Haberl <116439789+christianhaberl@users.noreply.github.com> Co-Authored-By: Claude --- docs/wiki/Cron-Jobs.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/wiki/Cron-Jobs.md b/docs/wiki/Cron-Jobs.md index a3d49c1d..e26cbd01 100644 --- a/docs/wiki/Cron-Jobs.md +++ b/docs/wiki/Cron-Jobs.md @@ -54,8 +54,8 @@ or a server restart shifts later runs slightly. That drift is accepted rather th This is the rule people trip over. A cron job fires with nobody watching, and the check that re-presses an Enter the agent ignored cannot reliably recognise a multi-line paste in the composer, so a multi-line prompt could sit there unsent. In `paste` mode the newlines would -reach the agent as keys. So a multi-line prompt is **rejected**: the form refuses it, and a prompt file whose -contents are multi-line fails the run with a clear message. +reach the agent as keys. So a multi-line prompt is **rejected**: the form refuses it, and a +prompt file whose contents are multi-line fails the run with a clear message. For anything longer than a sentence, put the instructions in a file and make the prompt tell the agent to read it: