docs: the submit check cannot reliably recognise a multi-line paste

It does match one Claude shows inline when the first line has 24+
non-space characters; it misses a short first line and the
[Pasted text #N +k lines] placeholder. Say "cannot reliably" instead of
"cannot".

Co-Authored-By: Christian Haberl <116439789+christianhaberl@users.noreply.github.com>
Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
committed 2026-10-21 08:03:55 +02:00
1 parent cf9511cb57
commit 74dcf9a59d
4 files changed
+9 -9

No files matched your search

+3 -3
View File
@@ -208,9 +208,9 @@ trailing carriage return:
| `paste` | `session.write()` — writes directly to the PTY/mux | Bulk paste-style delivery. | | `paste` | `session.write()` — writes directly to the PTY/mux | Bulk paste-style delivery. |
> ⚠️ **Single-line only — enforced.** A job fires unattended, and the submit > ⚠️ **Single-line only — enforced.** A job fires unattended, and the submit
> check that re-presses an ignored Enter cannot recognise a multi-line paste in > check that re-presses an ignored Enter cannot reliably recognise a multi-line
> the composer, so a stranded prompt would go unnoticed (in paste mode the > paste in the composer, so a stranded prompt would go unnoticed (in paste mode
> newlines reach the CLI as keys). So newlines are **rejected**: the > the newlines reach the CLI as keys). So newlines are **rejected**: the
> schema and the form refuse a multi-line `promptText`, and at fire time a > schema and the form refuse a multi-line `promptText`, and at fire time a
> prompt file whose content is multi-line (after stripping trailing newlines) > prompt file whose content is multi-line (after stripping trailing newlines)
> fails the run with a clear `errorMessage`. Put multi-line instructions in a > fails the run with a clear `errorMessage`. Put multi-line instructions in a
+3 -3
View File
@@ -52,9 +52,9 @@ or a server restart shifts later runs slightly. That drift is accepted rather th
## Prompts are single line ## Prompts are single line
This is the rule people trip over. A cron job fires with nobody watching, and the check that 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 recognise a multi-line paste in the composer, so re-presses an Enter the agent ignored cannot reliably recognise a multi-line paste in the
a multi-line prompt could sit there unsent. In `paste` mode the newlines would reach the agent composer, so a multi-line prompt could sit there unsent. In `paste` mode the newlines would
as keys. So a multi-line prompt is **rejected**: the form refuses it, and a prompt file whose 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. 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 For anything longer than a sentence, put the instructions in a file and make the prompt tell
+2 -2
View File
@@ -97,7 +97,7 @@ const CRON_PSEUDO_FS_TREES: readonly string[] = ['/proc', '/sys', '/dev'];
/** Sync blocklist for the create/update workingDir gate (no settings extras). */ /** Sync blocklist for the create/update workingDir gate (no settings extras). */
const CRON_WORKING_DIR_BLOCKED_TREES: readonly string[] = [...DEFAULT_BLOCKED_TREES, ...CRON_PSEUDO_FS_TREES]; const CRON_WORKING_DIR_BLOCKED_TREES: readonly string[] = [...DEFAULT_BLOCKED_TREES, ...CRON_PSEUDO_FS_TREES];
/** Prompt delivery is single-line only: the submit check cannot recognise a multi-line paste. */ /** Prompt delivery is single-line only: the submit check cannot reliably recognise a multi-line paste. */
const HAS_NEWLINE = /[\r\n]/; const HAS_NEWLINE = /[\r\n]/;
/** The three session calls prompt delivery needs, so it can be tested without a PTY. */ /** The three session calls prompt delivery needs, so it can be tested without a PTY. */
@@ -538,7 +538,7 @@ export class CronService {
/** /**
* Resolves the prompt text and enforces the single-line constraint: a job * Resolves the prompt text and enforces the single-line constraint: a job
* fires unattended, and the submit check that re-presses an ignored Enter * fires unattended, and the submit check that re-presses an ignored Enter
* cannot recognise a multi-line paste in the composer (typed mode), so a * cannot reliably recognise a multi-line paste in the composer (typed mode), so a
* stranded prompt would go unnoticed; in paste mode the newlines reach the * stranded prompt would go unnoticed; in paste mode the newlines reach the
* CLI as keys. Rather than risk an unattended agent's instructions, fail the * CLI as keys. Rather than risk an unattended agent's instructions, fail the
* run with a clear error. A prompt FILE may end with trailing newline(s) * run with a clear error. A prompt FILE may end with trailing newline(s)
+1 -1
View File
@@ -1905,7 +1905,7 @@ export const ScheduledRunSchema = z.object({
/** 'HH:MM' 24-hour time. */ /** 'HH:MM' 24-hour time. */
const hhmmSchema = z.string().regex(/^([01]?\d|2[0-3]):[0-5]\d$/, 'Time must be HH:MM (24-hour)'); const hhmmSchema = z.string().regex(/^([01]?\d|2[0-3]):[0-5]\d$/, 'Time must be HH:MM (24-hour)');
/** Prompt delivery is single-line only (the submit check cannot see a multi-line paste) — reject newlines outright. */ /** Prompt delivery is single-line only (the submit check cannot reliably recognise a multi-line paste) — reject newlines outright. */
const noNewlines = (v: string) => !/[\r\n]/.test(v); const noNewlines = (v: string) => !/[\r\n]/.test(v);
/** Shared field shape for creating/updating a scheduled job. */ /** Shared field shape for creating/updating a scheduled job. */