@streamoid/agent 0.6.26 → 0.6.28

package/dist/index.d.ts

@@ -197,11 +197,44 @@ export interface ConversationSearchDialogProps {
 }
 
 /** "Search or Ask CXO" — the command dialog a host opens from its sidebar's
- *  search trigger, identical in every product. */
+ *  search trigger, identical in every product. The presentation only; see
+ *  {@link AskCxoDialog} for the same thing with the host wiring done. */
 export declare function ConversationSearchDialog(
   props: ConversationSearchDialogProps,
 ): ReactElement;
 
+export interface AskCxoDialogProps
+  extends Pick<
+    ConversationSearchDialogProps,
+    | 'workspaceId'
+    | 'search'
+    | 'onClose'
+    | 'placeholder'
+    | 'emptyStateTitle'
+    | 'emptyStateDescription'
+  > {
+  /** Show the chat panel. `chatId` is the conversation the user picked out of
+   *  the results, or `null` when they asked something new — hand that `null`
+   *  straight to the panel's `chatId` and let the chat create the conversation
+   *  itself. */
+  onOpenChat(chatId: string | null): void;
+  /** Drop the Ask row and Enter-to-ask, leaving a plain conversation search. */
+  searchOnly?: boolean;
+}
+
+/**
+ * "Search or Ask CXO", wired the fast way — PREFER THIS over
+ * {@link ConversationSearchDialog}.
+ *
+ * Both hosts that wired `onAsk` by hand got it wrong the same two ways: they
+ * awaited the send before opening the panel (2.655s of nothing, measured on
+ * artifax.test) and then handed the panel a conversation id the server had not
+ * seen, which costs another spinner and a `/messages` fetch that returns
+ * nothing. This asks for one callback — "show the chat, on this conversation or
+ * on nothing" — and does the rest. Nothing in it touches the network.
+ */
+export declare function AskCxoDialog(props: AskCxoDialogProps): ReactElement;
+
 /** Input for {@link startConversation}. */
 export interface StartConversationInput {
   workspaceId: string;
@@ -209,19 +242,30 @@ export interface StartConversationInput {
   email: string;
   /** The user's first message. Trimmed; empty is rejected. */
   prompt: string;
+  /** The background send failed. Nothing waits for it, so this is the only way
+   *  to hear about a message that never reached the server. */
+  onSendFailed?(error: unknown): void;
 }
 
 /**
- * Start a NEW conversation from a first message and return its id — for a host
- * that has a question but no chat open yet (the dialog's Ask row). Hand the id
- * back to the panel through `adapters.chatId`.
+ * Start a NEW conversation from a first message and return its id.
+ *
+ * @deprecated Use {@link AskCxoDialog}, or {@link enqueueChatPrompt} directly.
+ * The id this returns is for a conversation the SERVER HAS NOT SEEN YET, and a
+ * host that passes it to the panel lands on the panel's "open an existing
+ * conversation" path: blank transcript, full-column spinner, and a `/messages`
+ * fetch for a conversation that has none — 714ms of it on artifax.test.
+ *
+ * It also no longer waits for the send. It used to await the POST before
+ * resolving, which bought a full round trip (2.655s, measured) for an id
+ * generated client-side on the line above. So the returned id is no longer a
+ * receipt: it means "this is the conversation your message is on its way to".
+ * `null` still means the inputs were incomplete and nothing was sent; a
+ * rejection is reported through `onSendFailed`.
  *
  * Delegates to the same send path the chat itself uses, so `enc_token`,
  * `color_mode` and `host_context` are filled in from inside the bundle; a host
  * cannot see those and should not try to send them itself.
- *
- * Resolves `null` when the inputs are incomplete or the send fails, so a caller
- * can show "could not start this chat" without unpacking an error.
  */
 export declare function startConversation(
   input: StartConversationInput,