@evandu/super-pi 0.1.64 → 0.1.66

package/dist/server/store.d.ts

@@ -185,7 +185,20 @@ export declare class Store {
      * the Archived group renders the same name.
      */
     renameConversation(conversationId: string, name: string): Promise<Conversation>;
-    addUserMessage(conversationId: string, content: string, images?: MessageImage[]): Promise<Message>;
+    addUserMessage(conversationId: string, content: string, images?: MessageImage[], attachments?: import("./types.js").MessageAttachments): Promise<Message>;
+    /**
+     * Appends one background-result message to a conversation, without starting a turn.
+     *
+     * Used by sub-agent dispatch completions and the exec service when they finish out of band - the
+     * result is the prompt for a follow-up turn in the old design, which made a "后台回传" render under
+     * the "你" bubble and asked the model to consume a tool envelope as user prose. This appends a
+     * `role: "tool"` message that the client renders with its own column and its own block UI, so the
+     * transcript shows the result AND nothing pretends the user said it.
+     *
+     * NO `turnContext` claim, NO `status: "running"`. The message sits in the transcript and a subsequent
+     * caller can start a turn normally if it wants the model to react to the result.
+     */
+    addToolMessage(conversationId: string, content: string): Promise<Message>;
     /**
      * Records the model a conversation runs on. `updatedAt` is deliberately NOT touched, for the same
      * reason rename does not touch it: it is the sidebar's recency key, and switching model is not
@@ -329,7 +342,7 @@ export declare class Store {
      * `cancel` and `steer` name the id, which is the only reason "cancel the second of two identical
      * messages" is expressible at all. `crypto.randomUUID`, like every other id in this store.
      */
-    enqueueMessage(conversationId: string, content: string, images?: MessageImage[]): Promise<QueuedMessage>;
+    enqueueMessage(conversationId: string, content: string, images?: MessageImage[], attachments?: import("./types.js").MessageAttachments): Promise<QueuedMessage>;
     /**
      * Removes one waiting message. Returns it, or `undefined` when it is already gone.
      *

package/dist/server/store.js

@@ -743,7 +743,7 @@ export class Store {
         await this.persistMetadata(conversationId);
         return structuredClone(conversation);
     }
-    async addUserMessage(conversationId, content, images) {
+    async addUserMessage(conversationId, content, images, attachments) {
         const conversation = this.requireConversation(conversationId);
         // The browser cannot reach an archived conversation, so this guard exists for any other caller -
         // a direct WebSocket client, or a future code path. Archiving is the promise that a conversation is
@@ -753,6 +753,8 @@ export class Store {
         const message = { id: id("message"), role: "user", content, createdAt: now() };
         if (images && images.length > 0)
             message.images = structuredClone(images);
+        if (attachments && attachments.length > 0)
+            message.attachments = structuredClone(attachments);
         conversation.messages.push(message);
         const firstUser = conversation.messages.find((item) => item.role === "user");
         const autoTitle = firstUser?.content.trim()
@@ -772,6 +774,28 @@ export class Store {
         await this.persist();
         return structuredClone(message);
     }
+    /**
+     * Appends one background-result message to a conversation, without starting a turn.
+     *
+     * Used by sub-agent dispatch completions and the exec service when they finish out of band - the
+     * result is the prompt for a follow-up turn in the old design, which made a "后台回传" render under
+     * the "你" bubble and asked the model to consume a tool envelope as user prose. This appends a
+     * `role: "tool"` message that the client renders with its own column and its own block UI, so the
+     * transcript shows the result AND nothing pretends the user said it.
+     *
+     * NO `turnContext` claim, NO `status: "running"`. The message sits in the transcript and a subsequent
+     * caller can start a turn normally if it wants the model to react to the result.
+     */
+    async addToolMessage(conversationId, content) {
+        const conversation = this.requireConversation(conversationId);
+        if (conversation.archivedAt)
+            throw new Error("无法向已归档的会话追加后台回传，请先恢复该会话");
+        const message = { id: id("message"), role: "tool", content, createdAt: now() };
+        conversation.messages.push(message);
+        conversation.updatedAt = message.createdAt;
+        await this.persist();
+        return structuredClone(message);
+    }
     /**
      * Records the model a conversation runs on. `updatedAt` is deliberately NOT touched, for the same
      * reason rename does not touch it: it is the sidebar's recency key, and switching model is not
@@ -1096,13 +1120,15 @@ export class Store {
      * `cancel` and `steer` name the id, which is the only reason "cancel the second of two identical
      * messages" is expressible at all. `crypto.randomUUID`, like every other id in this store.
      */
-    async enqueueMessage(conversationId, content, images) {
+    async enqueueMessage(conversationId, content, images, attachments) {
         this.requireConversation(conversationId);
         if (this.state.conversations.find((item) => item.id === conversationId)?.archivedAt)
             throw new Error("无法向已归档的会话排队消息，请先恢复该会话");
         const message = { id: id("q"), conversationId, content, state: "queued", createdAt: now() };
         if (images && images.length > 0)
             message.images = structuredClone(images);
+        if (attachments && attachments.length > 0)
+            message.attachments = structuredClone(attachments);
         this.state.queuedMessages.push(message);
         await this.persistCollections("queuedMessages");
         return structuredClone(message);

package/dist/server/types.d.ts

@@ -95,11 +95,26 @@ export type Message = {
     toolCalls?: ToolCallBlock[];
     thinking?: string;
     images?: MessageImage[];
+    attachments?: MessageAttachments;
     agentIdentity?: {
         id?: string;
         name: string;
     };
 };
+/**
+ * A piece of context attached to a user message that is shown as its OWN block under the bubble, rather
+ * than flattened into the prompt. Today: a skill the person picked from the slash menu - the model gets
+ * the skill text inlined into the prompt for execution, and the transcript shows the user that the
+ * skill they asked for is the one that was loaded. Collapsed by default because skill bodies can be
+ * hundreds of lines and the user already chose the skill by name.
+ */
+export type MessageAttachment = {
+    kind: "skill";
+    id: string;
+    name: string;
+    content: string;
+};
+export type MessageAttachments = MessageAttachment[];
 /**
  * ONE PARAMETER OF A TOOL CALL, as a call block lists it, and the boundary that keeps Pi's arguments out
  * of `state.json`.
@@ -674,6 +689,7 @@ export type QueuedMessage = {
     priority?: boolean;
     createdAt: string;
     images?: MessageImage[];
+    attachments?: MessageAttachments;
 };
 /**
  * What Pi reports about ITS OWN queue, forwarded to the browser as it arrives.
@@ -914,6 +930,7 @@ export type ClientCommandBody =
     conversationId: string;
     content: string;
     images?: MessageImage[];
+    attachments?: MessageAttachments;
 }
 /**
  * Revert the conversation to the state right AFTER one message: every message after it is removed from

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@evandu/super-pi",
-  "version": "0.1.64",
+  "version": "0.1.66",
   "description": "Web control plane and companion for Pi",
   "license": "MIT",
   "type": "module",