@haikit/client 0.5.0 → 0.6.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@haikit/client",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "description": "The haikit browser runtime: streams tool payloads into interactive UI surfaces. Plain ESM, no build step, no dependencies.",
   "keywords": [
     "haikit",

package/src/index.d.ts

@@ -114,8 +114,9 @@ export interface Chat {
   /**
    * Start the conversation before the user types, so a server with an init
    * tool runs it now and anything it shows is already there. Does nothing once
-   * this chat has a conversation, and a server without an init tool creates
-   * nothing. `mountChat` calls it when it opens and after `reset()`.
+   * the conversation has begun, and a server without an init tool creates
+   * nothing. If init throws, nothing is recorded, so calling it again tries
+   * again. `mountChat` calls it when it opens and after `reset()`.
    */
   start(): Promise<boolean>;
   interact(handle: string, action: string, value: unknown): Promise<void>;

package/src/index.js

@@ -332,15 +332,25 @@ export function createChat({ endpoint = "/hai", registry }) {
     return enqueue("/chat", { message: text });
   }
 
+  /**
+   * Whether the server has recorded this conversation's opening — init's call,
+   * or a first message — as its last `context` shows. Having a conversation id
+   * is not enough: `hello` arrives before init runs, and an init that throws
+   * leaves the id behind with an empty history.
+   */
+  const begun = () => state.context.messages.length > 0;
+
   /**
    * Start the conversation before the user types, so a server with an init
    * tool runs it now and whatever it shows is there first. Does nothing once
-   * this chat has a conversation. A server without an init tool answers with
-   * an empty stream and creates nothing; the first message starts the
-   * conversation, as it always has. Resolves like send().
+   * the conversation has begun. If init throws, the server records nothing,
+   * so calling this again tries again — as the first message would. A server
+   * without an init tool answers with an empty stream and creates nothing;
+   * the first message starts the conversation, as it always has. Resolves
+   * like send().
    */
   async function start() {
-    if (state.conversationId || closed()) return false;
+    if (begun() || closed()) return false;
     return enqueue("/start", {});
   }