Write a reply to a file: the write command

For the canvas's To .md: a one-off request with attachments, no history,
no thinking and no tools, whose reply is written to the first free name
in a folder instead of the conversation. It streams progress as a
character count, unwraps a reply the model fenced whole, and shares the
turn counter, so it stops a reply in flight and stop ends it with no file
left behind.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

1 files changed, 6 insertions, 1 deletions

diff --git a/README.md b/README.md
index 530ef99..8f622b9 100644
--- a/README.md
+++ b/README.md
@@ -43,7 +43,7 @@ first answers.
 JSON lines both ways on `$XDG_RUNTIME_DIR/desktop-assistant.sock` (mode
 0600). Every connected client sees every event.
 
-In: `ask {text, files}`, `stop`, `new`, `list`, `open {id}`, `search {q}`,
+In: `ask {text, files}`, `write {files, prompt, dir, name}`, `stop`, `new`, `list`, `open {id}`, `search {q}`,
 `delete {id}`.
 
 Out: `hello` on connect (state, model, context use, the current
@@ -55,6 +55,11 @@ conversation and any reply in flight), then `user`, `think`, `token`,
 Ids are integers; a malformed command or argument answers `error` and the
 connection stays open.
 
+`write` is a one-off request whose reply goes to a file instead of the
+conversation (the canvas's To .md): no history, no thinking, no tools; it
+streams `progress {chars}` and ends with `written {path}`, the first free
+name of `name` in `dir`. A stop leaves no file.
+
 `files` is a list of absolute paths, at most 8. Text and code files and
 PDFs are read and inlined, sharing half the free context (a PDF page with
 no text goes as an image, at most 4, rendered at 150 dpi, at most 1600 px);