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. |
> ⚠️ **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
> the composer, so a stranded prompt would go unnoticed (in paste mode the
> newlines reach the CLI as keys). So newlines are **rejected**: the
> check that re-presses an ignored Enter cannot reliably recognise a multi-line
> paste in the composer, so a stranded prompt would go unnoticed (in paste mode
> 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
> prompt file whose content is multi-line (after stripping trailing newlines)
> fails the run with a clear `errorMessage`. Put multi-line instructions in a