@astralform/js 4.6.1 → 4.7.0

package/dist/index.d.cts

@@ -889,6 +889,7 @@ declare class AstralformClient {
     private send;
     get<T>(path: string): Promise<T>;
     post<T>(path: string, body: unknown): Promise<T>;
+    patch<T>(path: string, body: unknown): Promise<T>;
     private del;
     private handleError;
     getHealth(): Promise<{
@@ -899,6 +900,16 @@ declare class AstralformClient {
     getAgentStatus(): Promise<AgentStatus>;
     getConversations(limit?: number, offset?: number): Promise<Conversation[]>;
     getMessages(conversationId: string): Promise<Message[]>;
+    /**
+     * 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.
+     */
+    renameConversation(id: string, title: string): Promise<Conversation>;
     deleteConversation(id: string): Promise<void>;
     /**
      * List the AI personas (sub-agents) available INSIDE the client's active
@@ -1223,6 +1234,19 @@ declare class ChatSession {
      * already scanned.
      */
     loadMoreConversations(): Promise<Conversation[]>;
+    /**
+     * 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.
+     */
+    renameConversation(id: string, title: string): Promise<void>;
     deleteConversation(id: string): Promise<void>;
     toggleClientTool(name: string): boolean;
 }
@@ -1349,6 +1373,11 @@ declare class StreamManager {
         skipHistoryReplay?: boolean;
     }): Promise<void>;
     createConversation(): Promise<string>;
+    /**
+     * Rename a conversation. Purely a relabel — no active-conversation or
+     * background-job bookkeeping to do, unlike delete, so this is a passthrough.
+     */
+    renameConversation(id: string, title: string): Promise<void>;
     deleteConversation(id: string): Promise<void>;
     stop(): void;
     destroy(): void;

package/dist/index.d.ts

@@ -889,6 +889,7 @@ declare class AstralformClient {
     private send;
     get<T>(path: string): Promise<T>;
     post<T>(path: string, body: unknown): Promise<T>;
+    patch<T>(path: string, body: unknown): Promise<T>;
     private del;
     private handleError;
     getHealth(): Promise<{
@@ -899,6 +900,16 @@ declare class AstralformClient {
     getAgentStatus(): Promise<AgentStatus>;
     getConversations(limit?: number, offset?: number): Promise<Conversation[]>;
     getMessages(conversationId: string): Promise<Message[]>;
+    /**
+     * 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.
+     */
+    renameConversation(id: string, title: string): Promise<Conversation>;
     deleteConversation(id: string): Promise<void>;
     /**
      * List the AI personas (sub-agents) available INSIDE the client's active
@@ -1223,6 +1234,19 @@ declare class ChatSession {
      * already scanned.
      */
     loadMoreConversations(): Promise<Conversation[]>;
+    /**
+     * 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.
+     */
+    renameConversation(id: string, title: string): Promise<void>;
     deleteConversation(id: string): Promise<void>;
     toggleClientTool(name: string): boolean;
 }
@@ -1349,6 +1373,11 @@ declare class StreamManager {
         skipHistoryReplay?: boolean;
     }): Promise<void>;
     createConversation(): Promise<string>;
+    /**
+     * Rename a conversation. Purely a relabel — no active-conversation or
+     * background-job bookkeeping to do, unlike delete, so this is a passthrough.
+     */
+    renameConversation(id: string, title: string): Promise<void>;
     deleteConversation(id: string): Promise<void>;
     stop(): void;
     destroy(): void;

package/dist/index.js

@@ -460,6 +460,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);
   }
@@ -530,6 +536,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)}`);
   }
@@ -1879,6 +1904,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);
@@ -2169,12 +2214,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);