teapot-coding-agent 0.37.70 → 0.37.71

package/dist/agent/llm.js

@@ -194,7 +194,21 @@ function sanitize(messages) {
             const parts = m.content_parts.map((p) => p.type === "image_url"
                 ? { type: "image_url", image_url: { url: p.image_url.url } }
                 : { type: "text", text: p.text ?? "" });
-            return { role: m.role, content: parts };
+            /**
+             * EVERY other field has to survive, not just `content`.
+             *
+             * This returned `{ role, content }` alone, so a TOOL message carrying an image lost its
+             * `tool_call_id` — and the API rejected the whole request: `400 Invalid input: expected string,
+             * received undefined`. MEASURED on v0.37.69 (`github-bug-research-1f48715f`): the `read_file`
+             * result rendered with its "the image itself is attached" text and the very next call 400'd.
+             *
+             * Spreading `m` first is what makes the multimodal path identical to the text path; a tool
+             * message without its id is not a message at all.
+             */
+            // `content_parts` is OUR field, carrying the parts into `content`; sending it upstream is an
+            // unknown property (a strict server rejects the request), so it is dropped here.
+            const { content_parts: _parts, ...rest } = m;
+            return { ...rest, content: parts };
         }
         if ((m.role === "user" || m.role === "assistant") && !m.content) {
             return { ...m, content: m.tool_calls?.length ? "(tool call)" : "(no content)" };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "teapot-coding-agent",
-  "version": "0.37.70",
+  "version": "0.37.71",
   "description": "A lightweight, always-on multi-agent harness for AI coding agents",
   "type": "module",
   "license": "AGPL-3.0-or-later",