@streamoid/agent 0.6.28 → 0.6.30

package/README.md

@@ -23,6 +23,12 @@ import "@streamoid/agent/style.css";
 - **API base:** use a relative base and proxy `/stream-agent/api/v1` to the agent
   backend from the host (same-origin → cookies flow, no CORS).
 
-> This is the **built** package, committed for publish provenance. It is generated
-> from the stream-agent frontend via `npm run build:lib` — do not hand-edit.
-> Rebuild and `npm publish` from this directory.
+> This directory is the package TEMPLATE, not the package. `npm run build:lib` in
+> the stream-agent frontend copies it over the bundle it builds — do not hand-edit
+> the published output.
+>
+> **Publishing is not manual.** `.github/workflows/publish-agent.yml` publishes on
+> every push to `develop` whose `version` here is not yet on npm, then opens a pin
+> bump PR in every consumer. So the one thing a change to the chat needs is a new
+> version in this directory's `package.json`; merging it ships everything else.
+> The `agent-version` check on each PR fails if that has been forgotten.

package/dist/index.d.ts

@@ -67,7 +67,24 @@ export interface AgentChatShellAdapters {
   theme: { mode: 'light' | 'dark' };
   config: {
     apiBase: string;
-    hide?: { sidepane?: boolean; newBrief?: boolean; notifications?: boolean };
+    hide?: {
+      sidepane?: boolean;
+      newBrief?: boolean;
+      notifications?: boolean;
+      /**
+       * Drop the panel's own header strip — the title, "New task", "History"
+       * and the close.
+       *
+       * Default `false`: without the strip the panel offers no way to start a
+       * second task or reach a previous one, and most hosts have no list of
+       * their own. Pass `true` only where the host really does own those
+       * controls (CXO's left rail lists conversations already).
+       *
+       * NOT the same as `newBrief`, which is about the standalone app's chrome
+       * and which every host sets from the same copied snippet.
+       */
+      header?: boolean;
+    };
     /**
      * `inline_ask` declares this mount an inline assistant sitting on top of a
      * host application page. It unlocks the tools that only make sense there —
@@ -75,6 +92,12 @@ export interface AgentChatShellAdapters {
      * instructions to the prompt. Defaults to `normal`.
      */
     widgetMode?: 'normal' | 'inline_ask';
+    /**
+     * What the panel's header strip calls the assistant. Defaults to `Ask CXO`
+     * — a value baked in when the package was built, so a host that brands the
+     * assistant differently has no other way to change it.
+     */
+    title?: string;
   };
   navigation: {
     chatId: string | null;
@@ -83,6 +106,16 @@ export interface AgentChatShellAdapters {
   /** Backend recovered after an outage — host decides what to do (must NOT
    *  reload the host window). */
   onBackendRecovered?: () => void;
+  /**
+   * Close the panel. Supply it and the close is drawn in the panel's own header
+   * strip, beside "New task" and "History".
+   *
+   * A host that draws its own close over the panel's top-right corner (Artifax
+   * does, absolutely positioned, with a reserved band above the transcript) can
+   * hand it over here and drop both the button and the band. Omit it and
+   * nothing changes — no close is drawn and the host's own still works.
+   */
+  onClose?: () => void;
   /**
    * The page the panel is sitting on. Sent with every message, so update it as
    * the user navigates: the agent then knows where they are without spending a