@astralform/js 4.6.1 → 4.8.0

package/dist/index.cjs

@@ -507,6 +507,12 @@ var AstralformClient = class {
       return await response.json();
     });
   }
+  async patch(path, body) {
+    return this.withDeadline(async (signal) => {
+      const response = await this.send("PATCH", path, body, signal);
+      return await response.json();
+    });
+  }
   async del(path) {
     await this.request("DELETE", path);
   }
@@ -577,6 +583,25 @@ var AstralformClient = class {
       createdAt: m.created_at
     }));
   }
+  /**
+   * Replace the title the server generated from the conversation's first turn.
+   *
+   * The server does NOT bump `updated_at` for a rename — conversations list
+   * newest-updated first, and relabelling one is not activity — so the
+   * timestamp coming back is the original. Callers should merge the response
+   * rather than stamp their own, or they reintroduce the reordering the
+   * server deliberately avoids.
+   */
+  async renameConversation(id, title) {
+    const c = await this.patch(`/v1/conversations/${encodeURIComponent(id)}`, { title });
+    return {
+      id: c.id,
+      title: c.title,
+      messageCount: c.message_count,
+      createdAt: c.created_at,
+      updatedAt: c.updated_at
+    };
+  }
   async deleteConversation(id) {
     await this.del(`/v1/conversations/${encodeURIComponent(id)}`);
   }
@@ -1059,6 +1084,16 @@ function translateCustomEvent(name, data) {
         type: "todo_update",
         todos: data.todos ?? []
       };
+    case "plan_update":
+      return {
+        type: "plan_update",
+        plan: data.plan ?? ""
+      };
+    case "note_update":
+      return {
+        type: "note_update",
+        notes: data.notes ?? []
+      };
     case "context_update":
       return {
         type: "context_update",
@@ -1926,6 +1961,26 @@ var ChatSession = class {
       this.isLoadingConversations = false;
     }
   }
+  /**
+   * Rename a conversation, server first.
+   *
+   * Deliberately NOT optimistic, unlike the delete below. A failed delete is
+   * self-correcting (the row is still there on the next page fetch), but a
+   * failed rename that had already been written locally would leave the
+   * sidebar showing a title the server never accepted — and nothing refetches
+   * a conversation that is already in the loaded list.
+   *
+   * Mirrors the `title_generated` path: the entry in `conversations` is
+   * mutated in place, which is what every consumer of the list reads.
+   */
+  async renameConversation(id, title) {
+    const updated = await this.client.renameConversation(id, title);
+    const conv = this.conversations.find((c) => c.id === id);
+    if (conv) {
+      conv.title = updated.title;
+    }
+    await this.storage.updateConversationTitle(id, updated.title);
+  }
   async deleteConversation(id) {
     try {
       await this.client.deleteConversation(id);
@@ -2030,6 +2085,8 @@ var ChatEventType = {
   UserMessage: "user_message",
   TitleGenerated: "title_generated",
   TodoUpdate: "todo_update",
+  PlanUpdate: "plan_update",
+  NoteUpdate: "note_update",
   ContextUpdate: "context_update",
   SubagentStart: "subagent_start",
   SubagentStop: "subagent_stop",
@@ -2216,12 +2273,19 @@ var StreamManager = class {
     }
     await this.restore(conversationId);
   }
-  // ── Create / delete conversation ──────────────────────────────
+  // ── Create / rename / delete conversation ─────────────────────
   async createConversation() {
     const id = await this.session.createNewConversation();
     this.setActiveConversation(id);
     return id;
   }
+  /**
+   * Rename a conversation. Purely a relabel — no active-conversation or
+   * background-job bookkeeping to do, unlike delete, so this is a passthrough.
+   */
+  async renameConversation(id, title) {
+    await this.session.renameConversation(id, title);
+  }
   async deleteConversation(id) {
     await this.session.deleteConversation(id);
     this._backgroundJobs.delete(id);