@adaptiqai/deepseek-harness 0.2.12 → 0.2.13

package/README.md

@@ -65,6 +65,7 @@ dsh plugin --profile web add @adaptiqai/deepseek-harness
 - **Subagents and teammates** also name the conversation that started them (`X-Adaptiq-Parent-Session-Id`), so the console shows them under it. A subagent is a `helper` of its parent; an Agent Teams teammate is a `track`, a line of work of its own (`X-Adaptiq-Session-Role`). A conversation you fork yourself names no parent.
 - **No compaction.** AdaptiqAI keeps the full conversation, so the plugin reports the model's true context window and declines the harness's compaction requests — in Remember and in Private — with a plain explanation, said once rather than at every step. Nothing is ever summarised away, and nothing is sent to the server for it.
 - **Thinking levels** come from each model's capability card (`adaptiq-model-capabilities-v1`): the levels, the value that turns thinking off, the default and the request field. Models without a card fall back to Low/High/Extra high/Max only when their id names a reasoning model.
+- **Images** reach a model whose capability card lists `image` in `input`: each one goes inline (`image_url` with a `data:` URL) where you put it in the message, after a short note naming it. The bytes come from the harness's own stored copy (content-addressed when you attached it), never from the original file, so a later turn resends exactly the same image even if the file changed. Images larger than 16 MP are scaled down first; the format is checked from the bytes (PNG, JPEG, WebP, GIF), and an image over 20 MB is refused with a plain message. Above 8 images in one request, the harness turns the oldest into notes. A model that reads text only gets a note in place of each image, and a notice says the images were not sent. Images a tool returns follow its result in the next message.
 - **Usage** is reported the harness's way: tokens read from memory count as cache reads, so the harness's own counters (cost, cache hit) are right.
 - **Busy and preparing answers** are retried by the harness, honouring the server's `Retry-After`.