pi-roundtable 0.13.0 → 0.14.0

package/CHANGELOG.md

@@ -5,6 +5,12 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+## [0.14.0] - 2026-10-14
+
+### Added
+
+- `attachmentsOf(message, dir, logger, fetchImpl?, limits?)` (`pi-roundtable/kit`) takes `limits.prepareImages?: boolean` (default `true`). `false` downloads the files only, with no `modelImagesOf`: `images` is empty and an image that cannot be decoded is not reported as a failure, so a host that hands the files to the attachment store does not decode twice or report an image failure twice. Download failures are reported as before.
+
 ## [0.13.0] - 2026-10-13
 
 ### Added

package/docs/plugins.md

@@ -556,7 +556,8 @@ A key the contract does not have stops the start and names the closest one.
 ### `context.attachments`: files from outside a turn
 
 A surface that takes a file as it arrives, such as Discord, hands the core a link, and the core downloads it into the conversation's attachment directory.
-The downloads of one message and of the message it replies to share a 60 second deadline, and a file that sends no byte for 10 seconds (the wait for its headers counts) is given up at once, so a stalled download costs 10 seconds, not the whole deadline. A file still to come when the deadline passes, a file that went quiet (`download failed: idle_timeout`), or one whose directory cannot be made, is reported as `download failed` and the turn goes on without it. `attachmentsOf(message, dir, logger, fetch?, { deadlineMs?, idleMs?, signal? })` takes both limits; on the agent server they are `discord.attachmentDownload: { deadlineMs?, idleMs? }` (each 1,000 to 600,000 ms; defaults 60,000 and 10,000), for a host on a slow link or with large files. A failure reason carries a code only (`download failed: ENOTDIR`, `download failed: TimeoutError`, `download failed: error`), never the error's text, which could quote a path of the host.
+The downloads of one message and of the message it replies to share a 60 second deadline, and a file that sends no byte for 10 seconds (the wait for its headers counts) is given up at once, so a stalled download costs 10 seconds, not the whole deadline. A file still to come when the deadline passes, a file that went quiet (`download failed: idle_timeout`), or one whose directory cannot be made, is reported as `download failed` and the turn goes on without it. `attachmentsOf(message, dir, logger, fetch?, { deadlineMs?, idleMs?, signal?, prepareImages? })` takes both limits; on the agent server they are `discord.attachmentDownload: { deadlineMs?, idleMs? }` (each 1,000 to 600,000 ms; defaults 60,000 and 10,000), for a host on a slow link or with large files. A failure reason carries a code only (`download failed: ENOTDIR`, `download failed: TimeoutError`, `download failed: error`), never the error's text, which could quote a path of the host.
+`prepareImages: false` (default `true`) downloads the files only: `images` is empty and an image that cannot be decoded is not reported, for a host that hands the files to the attachment store, which prepares the images itself, so they are not decoded twice and a failure is not reported twice.
 A plugin whose clients upload a file themselves, over HTTP for instance, has the file before any turn exists.
 `context.attachments` keeps such a file for the conversation until a turn uses it:
 

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "pi-roundtable",
-	"version": "0.13.0",
+	"version": "0.14.0",
 	"description": "A plugin-driven Pi agent server for one owner, reached through Discord or the web",
 	"type": "module",
 	"license": "MIT",

package/src/core/attachments/turn-attachments.ts

@@ -23,6 +23,12 @@ export async function collectAttachments(
 		idleMs?: number;
 		/** Aborts the downloads, as the deadline does. */
 		signal?: AbortSignal;
+		/**
+		 * Whether images are decoded for the model; default true. False downloads the files only:
+		 * `images` is empty and an image that cannot be decoded is no failure, for a host that hands
+		 * the files on to something that prepares them itself.
+		 */
+		prepareImages?: boolean;
 	},
 ): Promise<TurnAttachments> {
 	const { fetchImpl, logger } = options;
@@ -57,7 +63,10 @@ export async function collectAttachments(
 	);
 	const files = [...own.files, ...referenced.files];
 	const failures = [...own.failures, ...referenced.failures];
-	const prepared = await modelImagesOf(files, logger);
+	const prepared =
+		options.prepareImages === false
+			? { images: [], failures: [] }
+			: await modelImagesOf(files, logger);
 	const images = prepared.images;
 	failures.push(...prepared.failures);
 	if (files.length > 0 || failures.length > 0) {
@@ -74,13 +83,21 @@ export async function collectAttachments(
 	return { files, images, failures };
 }
 
-/** Collects a message's attachments into `dir`, reporting the files that failed. */
+/**
+ * Collects a message's attachments into `dir`, reporting the files that failed. `prepareImages:
+ * false` downloads the files only, without decoding the images for the model.
+ */
 export function attachmentsOf(
 	message: InboundMessage,
 	dir: string,
 	logger: Logger,
 	fetchImpl?: typeof fetch,
-	limits: { deadlineMs?: number; idleMs?: number; signal?: AbortSignal } = {},
+	limits: {
+		deadlineMs?: number;
+		idleMs?: number;
+		signal?: AbortSignal;
+		prepareImages?: boolean;
+	} = {},
 ): Promise<TurnAttachments> {
 	return collectAttachments(message, dir, {
 		logger,