@subako-ai/assistant-ui 0.1.1 → 0.1.2

package/README.md

@@ -23,7 +23,6 @@ import { SubakoProvider, useSession } from "@subako-ai/react";
 import { SubakoChat } from "@subako-ai/assistant-ui";
 
 const subako = new SubakoSessionClient({
-	baseUrl: "https://api.us.cloud.subako.ai",
 	getToken: (sessionId) => fetch(`/api/subako/token/${sessionId}`).then((r) => r.text()),
 });
 
@@ -83,7 +82,7 @@ layer, that turns unlayered element rules away and takes the layered ones
 instead, so Tailwind v3's preflight, a `normalize.css`, and the app's global
 `button` all leave the chat as it is. The one rule of a reset's that still
 reaches a button is `[type="button"]`, which names an attribute; it takes the
-background only, and the buttons are the colour of the bar they sit on. A tool
+background only, and the buttons are the color of the bar they sit on. A tool
 UI the app draws itself is not guarded: that is the app's own markup.
 
 An app whose CSS is layered itself — Tailwind v4 is one — says where `subako`
@@ -113,10 +112,10 @@ nonce the page puts on its own tags:
 A page with no such policy needs nothing: left out, the attribute is not
 written at all.
 
-### Colours
+### Colors
 
-Every surface names its own colour and its own background, so the chat is
-legible on a page of any colour instead of inheriting half of one. They come
+Every surface names its own color and its own background, so the chat is
+legible on a page of any color instead of inheriting half of one. They come
 from eight custom properties, light by default and dark under
 `prefers-color-scheme: dark`; the root also carries `color-scheme: light dark`
 so form controls follow. Set the properties on `.subako-chat` itself to theme
@@ -276,7 +275,7 @@ A tool that needs approval has to ask for it from whatever draws it: a row of
 the app's own gets `approval` and `respondToApproval` like any tool-call part,
 and the run waits until something answers. `SubakoToolApproval` is the chat's
 own prompt, for dropping in — Allow and Deny while the server waits on the
-person, nothing once there is an answer or the run was cancelled:
+person, nothing once there is an answer or the run was canceled:
 
 ```tsx
 import { SubakoToolApproval } from "@subako-ai/assistant-ui";

package/dist/chat.d.ts

@@ -7,7 +7,7 @@ export type SubakoToolApprovalProps = Pick<ToolCallMessagePartProps, "toolName"
 /**
  * The approval prompt of the chat's own tool row, for a tool UI the app draws
  * itself: Allow and Deny while the server waits on the person, and nothing
- * once there is an answer or the run was cancelled. Spread the tool call's
+ * once there is an answer or the run was canceled. Spread the tool call's
  * props into it; the answer reaches `resolveApproval` the same way.
  */
 export declare function SubakoToolApproval({ toolName, approval, respondToApproval }: SubakoToolApprovalProps): ReactNode;

package/dist/chat.js

@@ -8,8 +8,8 @@ import remarkGfm from "remark-gfm";
 import { useSubakoRuntime } from "./runtime.js";
 /**
  * Enough style to read a conversation with no setup at all. Every surface names
- * its own colour and its own background, so the chat is legible on a page of any
- * colour rather than inheriting half of one. The eight custom properties are the
+ * its own color and its own background, so the chat is legible on a page of any
+ * color rather than inheriting half of one. The eight custom properties are the
  * theming seam: light by default, dark when the browser asks for it, and an app
  * that sets them on `.subako-chat` overrides both. `className` is where an app
  * takes the rest over.
@@ -153,7 +153,7 @@ const awaiting = (approval) => approval !== undefined && approval.approved === u
 /**
  * The approval prompt of the chat's own tool row, for a tool UI the app draws
  * itself: Allow and Deny while the server waits on the person, and nothing
- * once there is an answer or the run was cancelled. Spread the tool call's
+ * once there is an answer or the run was canceled. Spread the tool call's
  * props into it; the answer reaches `resolveApproval` the same way.
  */
 export function SubakoToolApproval({ toolName, approval, respondToApproval }) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@subako-ai/assistant-ui",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "assistant-ui runtime and chat for Subako sessions",
   "homepage": "https://subako.ai",
   "license": "Apache-2.0",
@@ -34,15 +34,15 @@
     "react": "^19.2.0",
     "react-dom": "^19.2.0",
     "typescript": "^5.9.3",
-    "@subako-ai/sdk": "0.1.1",
-    "@subako-ai/react": "0.1.1"
+    "@subako-ai/react": "0.1.2",
+    "@subako-ai/sdk": "0.1.2"
   },
   "peerDependencies": {
     "@assistant-ui/react": "^0.15.0",
     "@assistant-ui/react-markdown": "^0.14.15",
     "react": "^19.0.0",
-    "@subako-ai/react": "^0.1.1",
-    "@subako-ai/sdk": "^0.1.1"
+    "@subako-ai/react": "^0.1.2",
+    "@subako-ai/sdk": "^0.1.2"
   },
   "engines": {
     "node": ">=22"

package/src/chat.tsx

@@ -18,8 +18,8 @@ import { useSubakoRuntime } from "./runtime.js";
 
 /**
  * Enough style to read a conversation with no setup at all. Every surface names
- * its own colour and its own background, so the chat is legible on a page of any
- * colour rather than inheriting half of one. The eight custom properties are the
+ * its own color and its own background, so the chat is legible on a page of any
+ * color rather than inheriting half of one. The eight custom properties are the
  * theming seam: light by default, dark when the browser asks for it, and an app
  * that sets them on `.subako-chat` overrides both. `className` is where an app
  * takes the rest over.
@@ -188,7 +188,7 @@ export type SubakoToolApprovalProps = Pick<ToolCallMessagePartProps, "toolName"
 /**
  * The approval prompt of the chat's own tool row, for a tool UI the app draws
  * itself: Allow and Deny while the server waits on the person, and nothing
- * once there is an answer or the run was cancelled. Spread the tool call's
+ * once there is an answer or the run was canceled. Spread the tool call's
  * props into it; the answer reaches `resolveApproval` the same way.
  */
 export function SubakoToolApproval({ toolName, approval, respondToApproval }: SubakoToolApprovalProps): ReactNode {