Draw a picture, on a ComfyUI you are running

The last unbuilt capability, and built the way CLAUDE.md said it had to be: a
ToolDef reaching resolve_tools plus a permission and a capability flag, not a new
code path. The only genuinely new UI is one branch in the transcript.

services/images/ is three modules. comfy.py speaks HTTP -- submit, poll /history,
fetch the PNG, /free, and an /object_info discovery for the admin page only.
Polled and not socketed, because holding a connection open for the length of a
generation is the live-connection state the whole ssh.py design forbids, and the
thing being waited for takes tens of seconds anyway. The base URL is exempt from
the SSRF guard by construction, exactly as Connection.base_url and the audio
endpoints are -- said out loud in the docstring, because a default of
127.0.0.1:8188 is precisely the shape that guard exists to refuse and therefore
reads as a hole rather than a decision.

workflow.py fills a template, and the one thing that matters is that it walks the
parsed JSON rather than the text of it. A value that is exactly "{{steps}}"
becomes the number 20; ComfyUI validates types and refuses the string. A
placeholder inside a longer string is still text, which is what makes
"{{prompt}}, masterpiece" work -- and text substitution would additionally mean a
prompt containing a quotation mark produced a document that no longer parses, on
the one input guaranteed to hold arbitrary text. Which node holds the prompt is
the administrator's statement rather than a guess from node types: sniffing for
the first CLIPTextEncode works on the shipped workflow and on nothing else, and
swaps positive for negative the first time somebody reorders them. seed has no
fixed default, because one would make every unspecified generation identical and
make the retry loop redraw the same rejected picture four times.

tool.py is one call, one finished image. Returning every attempt to the
conversation would cost a round each, make the ceiling advisory rather than
enforced, and walk the reader past every reject -- so the reviewer lives inside
the tool and is asked about *bytes*: an attempt about to be discarded should not
leave an Attachment behind, so it sees a downscaled preview built in memory and
only the kept image is written. Anything that goes wrong in review is a keep;
losing a picture because a judging request timed out would be the check
destroying the thing it was checking. The last attempt is kept whatever the
verdict, so a request always produces something. Rejects are recorded, not
stored.

Preserve VRAM unloads the chat's own connection and nothing else, because the
memory being freed belongs to one machine: local llama-swap answers GET /unload,
and a box on the network has no reason to be unloaded when ComfyUI wants memory
here. The swap goes round the review rather than round the tool, which costs two
model loads per retry -- so the two settings are independent and the page warns
when both are on. Nothing loads the LLM back: the reply's next request does, and
that step exists in the description and not in the code, so the code says so.

Two rules elsewhere had to be drawn for the first time. message_payload sends
images only on user turns -- no assistant message had ever carried one, and the
moment one does the multimodal list form on an assistant turn is rejected by
OpenAI and most local runners, breaking every later turn in the chat. And
files.store gained keep_original, because _process_image turns anything without
alpha into JPEG q85 at 1400px: right for a phone photo, a visible loss on the one
output this feature exists to produce.

/image sends the ordinary message with force_tool, which becomes tool_choice for
the first round only -- left in place the reply would draw a picture, be asked
again, and draw another. FORCEABLE_TOOLS is an allow list because the name is
read off a form.

ToolContext gained chat_id, and that fixed a tool nobody had ever successfully
run: _run_scratch_write read context.chat_id on a dataclass with no such field,
so every call raised AttributeError, swallowed by run_tool's blanket except into
"the scratch_write tool failed" -- indistinguishable from a model calling it
wrongly. The test that existed asserted the family and the risk, which are
properties of the declaration rather than of the code.

Verified against the real ComfyUI 0.27.0 on this machine rather than against
documentation: every endpoint shape here was read off it, a generation ran end to
end through the client, the reviewer was shown a matching and a mismatched prompt
and answered KEEP and RETRY correctly, and the unload hook fired for the local
llama-swap and not for the remote box.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

PLAN.md

@@ -7,8 +7,8 @@ that would be expensive to revisit. Kept current as work lands; the detail of
 **Status:** usable daily. Streaming chat, attachments, reasoning, tool calling
 with web search, custom HTTP tools and MCP servers, agent chats that work on a
 machine over SSH, a knowledge library, notes, memory and skills, speech in and
-out, users and groups, model administration, installable as an app. 1529 tests,
-`ruff` clean.
+out, image generation over ComfyUI, users and groups, model administration,
+installable as an app. 1676 tests, `ruff` clean.
 
 ---
 
@@ -115,6 +115,30 @@ be a different project, not a refactor.
 - [x] Local MCP over stdio is deliberately absent: spawning a subprocess would
       run on this machine, which nothing here does
 
+### Image generation
+- [x] **Draws on a ComfyUI you are running**, as a tool the model chooses to
+      call and as an `/image` command that makes it call one. Never on this
+      machine, the same rule agent chats follow
+- [x] **Multiple workflow templates** — a name, a description and a ComfyUI API
+      export with `{{prompt}}` and ten other placeholders where the values go.
+      The model picks between them by their descriptions, and by checkpoint,
+      falling back to the chat's usual and then the instance default when it
+      names neither
+- [x] Model may set prompt, negative, seed, steps, cfg, width, height, sampler,
+      scheduler, denoise, checkpoint and template; **only the prompt is
+      required** and everything else has a default
+- [x] **The result is checked before you see it** — optionally, a vision model
+      is shown the picture and the request and says keep or retry, up to a
+      configurable number of attempts. Only clearly wrong images are retried;
+      the last attempt is kept whatever it says, so a request always produces
+      something
+- [x] **Preserve VRAM** — opt-in, for a machine that cannot hold both at once:
+      unload the chat's own language model, generate, free ComfyUI, and let the
+      next request load the model back. Per connection, so a box on the network
+      is never touched
+- [x] Instance-wide extra instructions, injected into the harness beside the
+      tool's own guidance
+
 ### Agent chats
 - [x] A chat is a **Chat** or an **Agent**, chosen when it starts and fixed
       thereafter — a transcript whose earlier turns ran somewhere else is not
@@ -290,10 +314,6 @@ be a different project, not a refactor.
 
 In the order they are likely to be worth doing.
 
-### Image generation
-Left until last from the start, as it needs heavy customisation. ComfyUI is
-already running on this machine and is the obvious first target.
-
 ### Smaller things
 - **OCR** for scanned PDFs
 - **Conversation branching** — `Message.parent_id` exists unused; needs a UI for