@filigran/chatbot 3.19.0 → 3.20.0

package/CHANGELOG.md

@@ -8,7 +8,152 @@ the versions follow [semantic versioning](https://semver.org/spec/v2.0.0.html).
 This file starts at 3.10.0; earlier releases are on the
 [releases page](https://github.com/FiligranHQ/filigran-ui/releases).
 
-## 3.19.0 — unreleased
+## 3.20.0 — unreleased
+
+### Added
+
+- `ChatMarkerRenderer.standalone`: an answer that is the renderer's marker and
+  nothing else shows the card alone, without the agent's name, the time or the
+  actions, as a note between messages (a change of agent, for instance). Each
+  answer showed its marker's card inside the answer's frame.
+- The panel speaks German, Italian, Korean, Russian and Simplified Chinese on
+  its own: a catalog for each, picked from `locale` by its language whatever
+  the region (`de-de`, `it-it`, `ko-kr`, `ru-ru`, `zh-cn`). Those languages
+  showed in English unless the host translated every key through `t`.
+  Traditional Chinese tags (`zh-TW`, `zh-HK`, `zh-Hant`) keep falling back.
+- An agent the backend marks `disable_chat: true` (`XtmAgent.disableChat`) is
+  said `Not recommended for chat` in the agent picker, and the composer warns
+  while it is the conversation's agent as the header names it. It stays
+  selectable.
+- The header names the channel a conversation was started in under the
+  agent's name (`Agent · {channel}`), as its row does, when the host draws no
+  `headerSubtitle`; `channelLabel` names it there too. The restore's
+  `channel` names it before the list is read.
+- The composer's warning also covers an agent the draft `@`-mentions that is
+  not meant for chat, until the mention is removed.
+- With workspaces, the list's `Not in a workspace` group has a `New
+  conversation outside a workspace` button, beside each workspace's own.
+- In a reply's "Working files" list, a file the same reply wrote again later,
+  with the same name and kind of file (MIME type without its parameters, else
+  the type label), carries a "Superseded" tag; its last version carries none.
+  A file listed again ranks where it first appeared.
+- `ChatPanelHandle.attachFiles(files)` puts files in the composer's tray as if
+  the user picked them, uploaded and held to the same limits, for the next
+  message: files another app shared to the host. Nothing happens where the
+  panel takes no files.
+- `initialConversationListCollapsed` starts the conversation list collapsed to
+  its strip, from which the user opens it: for a phone or a narrow window.
+  Read once, when the panel mounts.
+- `replaceMessage(message, { streaming })` lets a host draw a message its own
+  way: `undefined` or a boolean leaves it to the panel, `null` leaves it out,
+  and anything else is drawn in its place without the message's frame. It is
+  asked of every message, the reply's empty placeholder included, and a throw
+  leaves that message to the panel. For messages a host folds into one of its
+  own, such as the replies of a turn cut and resumed shown as one card.
+- `expandedWorkspaceGroups` and `onExpandedWorkspaceGroupsChange` let a host
+  keep, per user, which workspace groups of the conversation list are open.
+  Given, every other group starts collapsed until the user opens it, and a
+  workspace the user creates from the list opens. A host still reading them
+  passes `undefined` until it has them. Unset, groups start open and the ones
+  the user collapses are remembered per browser, as before.
+
+### Changed
+
+- The agent picker follows the conversation on screen: opening a conversation
+  of another agent, or reading back one the host continued with another agent,
+  picks that agent, so a new chat starts with it, after a reload too, and
+  `onAgentChange` is called.
+  An agent picked in the menu meanwhile stays picked. The picker kept the agent
+  last picked in the menu, while the header named the conversation's.
+
+### Fixed
+
+- `maxTotalSize: Infinity` lifts the cap on the total size of a message's
+  files, as a host with a per-file limit only passes it (XTM One's web chat and
+  Office add-in). The panel read a value that is not finite as invalid and kept
+  its 50 MB default total.
+- A message sent from a new chat no longer comes back as the next new chat's
+  draft: the draft leaves the conversation it was typed in as it is sent. The
+  write of the emptied composer could land on the conversation the send
+  created, leaving the sent text under the new chat's draft.
+- An image's lightbox is named after the image (its alt text, or the file's
+  name for an uploaded picture) and keeps `Image preview` for one with none; it
+  read `Image preview` for every picture.
+- Tab and Shift+Tab stay on the lightbox's own controls (Download when offered,
+  Close) while it is open; they reached the page under it.
+- An image's Expand button is visible while it has keyboard focus, so the focus
+  given back after the lightbox closes can be seen. It showed on hover only.
+- A refusal whose body has no `detail` shows its `error` when that is a
+  sentence, as the products' proxies answer (`{ "error": "..." }`, beside a
+  `status` or not), never a code (`invalid_token`, `Unauthorized`) nor a
+  status's reason phrase (`Not Found`, `Too Many Requests`). It shows above
+  the composer, in place of the answer, on a failed upload's chip, under the
+  conversation list and on a conversation that could not be loaded. The panel
+  showed its generic message instead.
+- The status line has its own wording when it has no agent's name (`The agent
+  is answering…`, `Consulting an agent…`, `Transferring to another agent…`),
+  where it filled the name with a lowercase `the agent`: `the agent is
+  answering…` started without a capital. A host translating through `t` in a
+  language the panel has no catalog for translates these three keys; it
+  translated `the agent` before, and shows them in English until it does.
+- A host that can steer (a `steer` route, on by default) gets its conversation
+  created before the first message, so the first turn can be steered. Where
+  turns end with their stream (no `cancel`, `skipWait` or `events` route) the
+  panel learned the conversation's id only at the turn's end, and a message
+  typed while that first turn ran could not be sent.
+- A steer the backend refuses because the turn just ended (409) goes out as
+  the next message, as a send during a turn winding down does, whatever
+  `holdSendsDuringTurn` says. Without it, the text went back to the composer
+  and the user had to send it again.
+- Files added from outside the panel's own events (a host's call) upload too:
+  the upload launched on a timer that assumed the tray had been updated
+  already, which only a pick guaranteed.
+- A wait a resumed turn continued (`wait_start`) ends on `wait_continued`
+  with `Analyzing results…`, as the turn moves on to read what it waited for.
+  The status line read `Thinking...` until the next status.
+
+## 3.19.1 — 2026-11-02
+
+### Added
+
+- The panel speaks German, Italian, Korean, Russian and Simplified Chinese on
+  its own: a catalog for each, picked from `locale` by its language whatever
+  the region (`de-de`, `it-it`, `ko-kr`, `ru-ru`, `zh-cn`). Those languages
+  showed in English unless the host translated every key through `t`.
+  Traditional Chinese tags (`zh-TW`, `zh-HK`, `zh-Hant`) keep falling back.
+- Inline, as a sidebar and fullscreen, the composer's footer has a line of
+  its own for what the keys do (`filigran-chat-composer-hint`), above the
+  disclaimer: an idle composer reads
+  `Enter to send · Shift+Enter for new line`, a busy one the status it read
+  before, and the line keeps its height when empty. The floating window keeps
+  one line, where a status takes the disclaimer's place.
+
+### Fixed
+
+- `filigran-chat-disclaimer` holds the disclaimer alone. It held the
+  composer's status in its place while a turn ran or a file failed to
+  upload; the status is now `filigran-chat-composer-hint`.
+- A refusal whose body has no `detail` shows its `error` when that is a
+  sentence, as the products' proxies answer (`{ "error": "..." }`, beside a
+  `status` or not), never a code (`invalid_token`, `Unauthorized`) nor a
+  status's reason phrase (`Not Found`, `Too Many Requests`). It shows above
+  the composer, in place of the answer, on a failed upload's chip, under the
+  conversation list and on a conversation that could not be loaded. The panel
+  showed its generic message instead.
+- The status line has its own wording when it has no agent's name (`The agent
+  is answering…`, `Consulting an agent…`, `Transferring to another agent…`),
+  where it filled the name with a lowercase `the agent`: `the agent is
+  answering…` started without a capital. A host translating through `t` in a
+  language the panel has no catalog for translates these three keys; it
+  translated `the agent` before, and shows them in English until it does.
+- A conversation list that could not be read (a refusal, a server or network
+  error) says "Could not load your conversations." with a Retry, in the
+  fullscreen list and the header's history menu, where it said "No
+  conversations yet". A read that fails once the list was read keeps the
+  conversations it showed, unless it was refused (401/403), which drops them;
+  a backend without the route (404/405) still shows an empty list.
+
+## 3.19.0 — 2026-11-02
 
 ### Added
 
@@ -164,7 +309,7 @@ This file starts at 3.10.0; earlier releases are on the
   query: the list stayed filtered by a search the user could neither see nor
   clear.
 
-## 3.18.1 — unreleased
+## 3.18.1 — 2026-11-02
 
 ### Fixed
 

package/README.md

@@ -107,7 +107,7 @@ import { ChatPanel } from '@filigran/chatbot';
 | `conversationId`    | `string \| null`                          | —            | The conversation on screen when the host owns it (a `?c=` URL); `null` is a new chat. Left `undefined`, the panel remembers its own, and a host-owned one is never written to storage |
 | `onConversationChange` | `(id: string \| null) => void`         | —            | Called whenever the conversation on screen changes, whoever changed it (a first answer, New chat, the history) |
 | `initialAgent`      | `string`                                  | —            | Agent selected once the list loads, by id or slug, over the remembered one |
-| `onAgentChange`     | `(agent: XtmAgent) => void`               | —            | Called when another agent is picked |
+| `onAgentChange`     | `(agent: XtmAgent) => void`               | —            | Called when another agent is picked, in the menu or by opening a conversation of another agent: the picker follows the conversation on screen |
 | `readOnly`          | `boolean`                                 | `false`      | Hides the composer: a conversation the user may read but not write to |
 | `readOnlyNotice`    | `React.ReactNode`                         | —            | Shown in place of the composer while `readOnly` |
 | `getRequestExtras`  | `() => Record<string, unknown>`           | —            | Fields merged into every message body, read at send time (the host's own per-message options). They never override the panel's fields |
@@ -119,6 +119,7 @@ import { ChatPanel } from '@filigran/chatbot';
 | `onArtifactOpen`    | `(artifact: ChatArtifact) => void`        | —            | Opens a deck, report or video in the host, in place of the `Open in XTM One` link |
 | `headerActions` / `banner` / `composerHeader` / `transcriptFooter` / `welcome` | `React.ReactNode` | — | The host's content in the header, above the thread, above the composer, after the last message, or in place of the welcome screen |
 | `renderMessageExtras` / `messageFooterActions` | `(message, { streaming }) => React.ReactNode` | — | The host's content under a message, and controls in a finished answer's footer; `streaming` while the message is the answer still being written. `message.raw` holds the backend's own fields — see [Host extensions](#host-extensions) |
+| `replaceMessage` | `(message, { streaming }) => React.ReactNode` | — | The host's own drawing of a message: `undefined` or a boolean leaves it to the panel, `null` leaves it out, anything else is drawn in its place without the message's frame (name, time, actions). Asked of every message, the reply's empty placeholder included. A throw leaves that message to the panel. For messages a host folds into one of its own, such as a turn cut and resumed shown as one card |
 | `sidebarRowActions` | `(conversation) => React.ReactNode`       | —            | The host's controls on a row of the conversation list |
 | `sidebarHeaderActions` | `React.ReactNode`  | —            | The host's controls beside New conversation |
 | `sidebarSections` | `React.ReactNode \| ((search: ChatSidebarSearch) => React.ReactNode)` | — | Sections under the list; a function draws them from the list's search (`query`, trimmed), again when the search or the function changes (pass a stable one, and put hooks in a component it returns), and offers the search box whatever the number of conversations |
@@ -137,12 +138,14 @@ import { ChatPanel } from '@filigran/chatbot';
 | `onTurnRunningChange` | `(running: boolean, info?: ChatTurnEnd) => void` | —     | A turn started or stopped running on screen, own or relayed: the state of the Stop button and of `draft.turnRunning`; with `false` comes how it ended, `info.ended`: `'answered'`, `'stopped'` or `'failed'` — see [Host extensions](#host-extensions). After a provisional end (see [Turns that outlive their stream](#turns-that-outlive-their-stream)) `false` comes at once, while sends are still held as the turn winds down: until its stored end or its stream's close, at most 5 s |
 | `onBeforeSend`      | `(draft) => false \| { text?, displayText?, extras? } \| void` | — | Sees every non-empty send first and takes it over (`false`), rewords it, shows the user's bubble other words or adds body fields (a message with fields of its own is held with `holdSendsDuringTurn`) — see [Host extensions](#host-extensions) |
 | `hideConversationList` | `boolean`                              | `false`      | Hides the conversation list of fullscreen and inline modes, for a rail or a task pane (usable from 320 px wide); the header's history menu stands in for it — see [Host extensions](#host-extensions) |
+| `expandedWorkspaceGroups` | `string[]` | — | The workspace groups the user has opened (workspace ids), for a host that keeps them per user: every other group starts collapsed, and one the user creates from the list opens. Read once, the first time it is given (`undefined` while the host reads them). Unset, groups start open and the collapsed ones are remembered per browser |
+| `onExpandedWorkspaceGroupsChange` | `(keys: string[]) => void` | — | The groups the user has opened, each time one is opened or collapsed (see `expandedWorkspaceGroups`) |
 | `holdSendsDuringTurn` | `boolean`                               | `false`      | A message that cannot steer is held and sent when the turn ends, instead of waiting in the composer. A turn winding down after a provisional end (until its stored end or its stream's close, at most 5 s) holds sends with or without it |
 | `onBeforeMove`      | `(conversation, workspace \| null) => boolean \| Promise<boolean>` | — | Asked before a drag or a row's Move menu files a conversation into a workspace (`null`: out of one); `false` leaves it where it was |
 | `onConversationActionFailed` | `(action, conversation \| null, error \| null) => boolean \| void` | — | A failed `'delete'`, `'rename'`, `'move'` or `'clearAll'`, with the backend's reason; return `true` when the host told the user itself, and the panel says nothing |
 | `sidebarSearchThreshold` | `number`                             | `7`          | The conversation list's search box shows above this many conversations; `0` shows it from the first |
-| `channelLabel`      | `(channel: string) => string \| null \| undefined` | — | Names the channel a row's conversation was started in (`Started in {channel}`); `null` shows nothing, `undefined` keeps the panel's names (Slack, Teams, WhatsApp, Telegram, Discord, Google Chat) |
-| `headerTitle` / `headerSubtitle` | `React.ReactNode \| ((context: ChatHeaderContext) => React.ReactNode)` | — | A title beside the header's agent name and a line under it, or functions of the conversation on screen (as the list holds it) and the agent |
+| `channelLabel`      | `(channel: string) => string \| null \| undefined` | — | Names the channel a conversation was started in, on its row (`Started in {channel}`) and in the header (`Agent · {channel}`); `null` shows nothing, `undefined` keeps the panel's names (Slack, Teams, WhatsApp, Telegram, Discord, Google Chat) |
+| `headerTitle` / `headerSubtitle` | `React.ReactNode \| ((context: ChatHeaderContext) => React.ReactNode)` | — | A title beside the header's agent name and a line under it, or functions of the conversation on screen (as the list holds it) and the agent. Without `headerSubtitle`, the line reads `Agent · {channel}` for a conversation started in a channel its row names |
 | `agentHref`         | `(agent: XtmAgent) => string \| undefined` | —          | Links the header's agent name to this address (http(s) or a path of the host's origin), in place; the chevron beside it opens the picker |
 | `onAgentNameClick`  | `(agent: XtmAgent) => void`               | —            | Takes a plain click on the header's agent name (over `agentHref`); the chevron beside it opens the picker |
 | `clearAllAction`    | `'delete' \| 'archive'`                   | `'delete'`   | What Clear all does, for its wording (`Archive all conversations`) |
@@ -194,13 +197,16 @@ A host adds what is its own without the package learning about it. An answer
 marker `[[KIND:args]]` renders the host's card where it stands, once the answer
 is done (`renderWhileStreaming` to show it earlier); a renderer named `FILE`,
 `PRESENTATION`, `REPORT` or `VIDEO` replaces the built-in card, and a marker no
-renderer names stays text:
+renderer names stays text. A `standalone` renderer draws an answer that is its
+marker and nothing else as the card alone, without the agent's name, the time
+or the actions: a note between messages, such as a change of agent:
 
 ```tsx
 const markers = useMemo(
   () => ({
     WORK_ITEM: { render: (id) => <WorkItemCard id={id} /> },
     INVESTIGATION: { render: (id) => <InvestigationBlock id={id} />, fullWidth: true },
+    AGENT_SWITCH: { render: (id) => <AgentSwitchDivider id={id} />, fullWidth: true, standalone: true },
   }),
   [],
 );
@@ -465,6 +471,11 @@ Returns available AI agents.
 `badges` is optional: short labels, already translated, shown after the
 agent's name in the agent picker. Anything but strings is ignored.
 
+`disable_chat` is optional: `true` marks an agent meant for assignments rather
+than chat. The picker says `Not recommended for chat` after its name, and the
+composer warns while it is the agent written to; it stays selectable. The
+panel reads it as `XtmAgent.disableChat`.
+
 ### `POST {apiBaseUrl}/chat/sessions`
 
 Restores conversation history (and, implicitly, resolves the session).
@@ -508,6 +519,11 @@ without one shows no time. `feedback` is the caller's own rating of an
 assistant answer: the thumbs are then locked on it ("Feedback already
 submitted").
 
+The response may also carry the conversation's `channel` (`slack`, `teams`,
+…), as the list does: the header names it (`Agent · {channel}`) without
+reading the list, which floating and sidebar modes read only once the history
+menu opens.
+
 The response **should echo a `conversation_id`**. When the stored
 `conversation_id` no longer exists (e.g. the platform was reset but the
 browser kept an old id in `localStorage`), the backend is expected to
@@ -520,8 +536,8 @@ conversation. If the endpoint responds with a non-2xx status, the component
 silently resets the stored id and starts fresh on the next message, except
 when it says nothing of the conversation: a `502`, `503` or `504` (or no
 answer at all) keeps the id and reads it back once the backend answers, and a
-`401` or `403` (expired credentials) keeps it, shows the response's `detail`
-(or "This conversation could not be loaded.") with a Retry button, and reads
+`401` or `403` (expired credentials) keeps it, shows the response's
+[reason](#a-refusals-reason) (or "This conversation could not be loaded.") with a Retry button, and reads
 it back as soon as `requestHeaders` change.
 
 Assistant history messages **should echo the same `attachments[]` array** that
@@ -564,14 +580,15 @@ Lists the user's past conversations for the history menu in the chat header.
 ```
 
 `last_message_preview` and `channel` are optional: a row shows the preview
-under its title, and names a messaging channel the conversation was started
-in (see `channelLabel`).
+under its title, and the search matches it; the row and the header name a
+messaging channel the conversation was started in (see `channelLabel`).
 
 Selecting a conversation restores it through the existing
 `POST /chat/sessions` contract above. The endpoint is fetched lazily when the
 history menu opens; a backend that doesn't implement it yet (404/405) simply
 yields an empty list, so the menu shows its empty state instead of breaking
-the chat. Set `apiEndpoints.history` to `null` to hide the history menu
+the chat. Any other failed read shows "Could not load your conversations."
+with a Retry, and keeps the conversations a previous read gave. Set `apiEndpoints.history` to `null` to hide the history menu
 entirely, or point it at a dedicated path if your proxy can't route `GET` on
 the sessions path.
 
@@ -583,7 +600,7 @@ the row reverts to its previous title.
 
 With [workspaces](#workspaces) on, the same route files a conversation:
 `{ "workspace_id": "uuid" }`, or `{ "workspace_id": null }` to take it out of
-its workspace. A refusal's `detail` is shown under the list.
+its workspace. A refusal's [reason](#a-refusals-reason) is shown under the list.
 
 ### Workspaces
 
@@ -659,6 +676,17 @@ Deletes a conversation from the history menu. Any 2xx response counts as
 success; deleting the active conversation resets the panel to a fresh chat so
 the next message never targets a dead conversation id.
 
+### A refusal's reason
+
+Where the panel shows why the backend refused a request, it reads the JSON body
+of the non-2xx answer: its `detail` when a string, or the `message` (or
+`detail`) of a `detail` object, as XTM One answers; else its `error` when that
+is a sentence, as the products' proxies answer (`{ "error": "..." }`, beside a
+`status` or not). A code (`invalid_token`, `Unauthorized`), a status's reason
+phrase (`Not Found`, `Too Many Requests`), anything else in the body (a
+top-level `message` included), a string over 500 characters or a body that is
+not JSON shows the panel's own, translated message.
+
 ### `POST {apiBaseUrl}/chat/messages`
 
 Sends a message and streams the response via SSE.
@@ -686,7 +714,7 @@ It must be JSON-serializable — a non-serializable value (circular reference,
 
 A refusal before the stream (a non-2xx answer: a rate limit, a refused
 option, an unknown conversation) shows the response's `detail` in place of the
-answer - a string, or the `message` (or `detail`) of an object - and
+answer ([its reason](#a-refusals-reason)), and
 "Unable to connect. Please check the configuration." when it has none; the
 handle's `send` resolves `'failed'`.
 
@@ -820,23 +848,25 @@ until the next send. On a non-2xx
 response or a network error nothing was stored: the optimistic user bubble is
 rolled back, the text is restored into the composer (prepended on its own line
 if the user already typed something new), the send resolves `'failed'` and the
-refusal's `detail`, when there is one, shows above the composer — so a backend
+refusal's [reason](#a-refusals-reason), when there is one, shows above the composer — so a backend
 without steering support degrades gracefully and the message is never silently
 lost. A `409` means no turn is running any more, an ordinary race: no notice
-shows, and with `holdSendsDuringTurn` the message is held and sent as the next
-turn instead of going back to the composer. Set `apiEndpoints.steer` to `null`
-to disable the steering affordances entirely.
+shows, and the message is held and sent as the next turn, with or without
+`holdSendsDuringTurn`. Set `apiEndpoints.steer` to `null` to disable the
+steering affordances entirely.
 
 Steering only applies to sends on the `rest` backend with a known
-`conversation_id` (the first turn of a fresh conversation only receives its id
-on `done`). A message with attachments steers only with `steerAttachments`
+`conversation_id`. The stream names a fresh conversation only on `done`, so
+while steering is on a new chat is created (`POST {sessions}`) before its first
+message, and that first turn can be steered too; with `steer: null` it is not.
+A message with attachments steers only with `steerAttachments`
 (once every file is uploaded); one carrying conversation references, agent
 mentions or body fields of its own (`send`'s `extras`, `onBeforeSend`'s
 `extras`) never steers, since a steer reaches the agent as text alone: it waits
 for the turn to end (`holdSendsDuringTurn`), and `onBeforeSend` is asked again,
 with `turnRunning: false`, before it goes out. A file that failed to upload
 neither steers nor waits, nor goes without that file: its chip says why (the
-upload's `detail`), and the composer offers no send, and says why, until the
+upload's [reason](#a-refusals-reason)), and the composer offers no send, and says why, until the
 user removes it. `send` and a voice
 call attach no files, so this never holds them. Esc stops generating.
 
@@ -1044,7 +1074,7 @@ chat) opts into six more routes, none with a default:
 
 | `apiEndpoints` key | Request | What it does |
 | --- | --- | --- |
-| `cancel` | `POST {cancel}` with `{ conversation_id }` | Stop asks the backend to end the turn; the panel keeps reading until the stream's `cancelled` frame (or lets go after 10 s, or at once on a network error or an answer of `{ "turn": "none" }`, reading the conversation back for an end it had not read yet). A Stop pressed before the panel's own send started its turn (its stream delivered nothing yet) carries `"awaiting_send": true`, and its `none` says nothing of that turn: the Stop stays pending and is sent again, without the flag, as the turn starts (or as the answer comes, the turn started meanwhile); any other answer reached a turn, and nothing goes again. A backend may keep a Stop with that flag for the send's turn, and must then take a second cancel of one turn; a Stop without it says nothing of a later send. A refusal (non-2xx) keeps the turn running and shows its `detail` above the composer |
+| `cancel` | `POST {cancel}` with `{ conversation_id }` | Stop asks the backend to end the turn; the panel keeps reading until the stream's `cancelled` frame (or lets go after 10 s, or at once on a network error or an answer of `{ "turn": "none" }`, reading the conversation back for an end it had not read yet). A Stop pressed before the panel's own send started its turn (its stream delivered nothing yet) carries `"awaiting_send": true`, and its `none` says nothing of that turn: the Stop stays pending and is sent again, without the flag, as the turn starts (or as the answer comes, the turn started meanwhile); any other answer reached a turn, and nothing goes again. A backend may keep a Stop with that flag for the send's turn, and must then take a second cancel of one turn; a Stop without it says nothing of a later send. A refusal (non-2xx) keeps the turn running and shows its [reason](#a-refusals-reason) above the composer |
 | `skipWait` | `POST {skipWait}` with `{ conversation_id }` | `Continue now` on `status: wait_start` (`{ seconds, reason }`), for as long as the pause lasts (see the status values) |
 | `events` | `GET {events}/{conversation_id}/events?client_id=<id>` → SSE | Turns this panel did not start (another tab, a reload mid-turn), `user_message`, `conversation_title`, `approval_resolved`; every frame of a turn names it (`turn_id`, below) |
 | `messagesPage` | `GET {messagesPage}/{conversation_id}/messages?before=<message id>&limit=50&supports_artifacts=true` → `{ messages, has_more }` | "Load earlier messages" past the restored ones, offered when the restore answers `has_more: true` |
@@ -1290,9 +1320,12 @@ both. The same variables may be set in CSS on an ancestor instead.
 
 ### Internationalization
 
-The panel speaks English, French, Spanish and Japanese on its own: it ships a
-catalog for each and picks one from `locale` (`fr-FR` reads French; English, or
-a language it lacks, is its own keys). A host in another language translates
+The panel speaks English, French, German, Italian, Spanish, Japanese, Korean,
+Russian and Simplified Chinese on its own: it ships a catalog for each and
+picks one from `locale` by its language, whatever the region (`fr-FR` reads
+French, `zh-cn` Chinese; English, or a language it lacks, is its own keys).
+Traditional Chinese (`zh-TW`, `zh-HK`, `zh-Hant`) has no catalog: it reads
+English unless the host translates it through `t`. A host in another language translates
 through `t`. A host with nothing to add only passes `locale`:
 
 ```tsx

package/dist/index.d.ts

@@ -36,8 +36,11 @@ interface ApiEndpoints {
      * message was persisted and will be injected into the running agentic loop
      * at the next iteration boundary. On a non-2xx response the optimistic
      * bubble is rolled back and the text is restored into the composer, so a
-     * backend without steering support degrades gracefully. Set to null to
-     * disable mid-run steering entirely.
+     * backend without steering support degrades gracefully. A new chat is
+     * created (`POST {sessions}`) before its first message, so a steer can name
+     * the first turn's conversation: the stream names it only when the turn
+     * ends. Set to null to disable mid-run steering entirely, and that create
+     * with it.
      */
     steer?: string | null;
     /**
@@ -471,7 +474,7 @@ interface ChatPanelProps {
     onDownloadError?: (error: unknown, attachment: ChatAttachment) => void;
     /** Maximum number of files attachable in one chat context. Default: 10. */
     maxFileCount?: number;
-    /** Maximum total size in bytes for attached files. Default: 50 * 1024 * 1024 (50 MB). */
+    /** Maximum total size in bytes for attached files; `Infinity` for none. Default: 50 * 1024 * 1024 (50 MB). */
     maxTotalSize?: number;
     /** Maximum size in bytes of one attached file. Default: none (only `maxTotalSize`). */
     maxFileSize?: number;
@@ -570,7 +573,7 @@ interface ChatPanelProps {
     onMessageFeedback?: (messageId: string, feedback: MessageFeedback | null, message: ChatMessage) => void;
     /**
      * The user's language as a BCP 47 tag (`'fr'`, `'en-US'`): the language the
-     * panel speaks (its own catalog: en, es, fr, ja) where `t` does not
+     * panel speaks (its own catalog: en, de, es, fr, it, ja, ko, ru, zh-Hans) where `t` does not
      * translate a key, formats the time under each message and is the language
      * answers are read aloud in. Default: the browser's own, except that a host
      * passing `t` and no `locale` gets no catalog.
@@ -619,7 +622,11 @@ interface ChatPanelProps {
     onConversationChange?: (conversationId: string | null) => void;
     /** Agent selected once the list loads, by id or slug, over the remembered one. */
     initialAgent?: string;
-    /** Called when another agent is picked. */
+    /**
+     * Called when another agent is picked, in the menu or by opening a
+     * conversation of another agent (the picker follows the conversation on
+     * screen, so a new chat starts with its agent).
+     */
     onAgentChange?: (agent: XtmAgent) => void;
     /** Hides the composer: a conversation the user may read but not write to. */
     readOnly?: boolean;
@@ -682,6 +689,18 @@ interface ChatPanelProps {
     welcome?: React.ReactNode;
     /** Rendered under a message's content, before its footer; `context.streaming` while the answer is still coming. */
     renderMessageExtras?: (message: ChatMessage, context: ChatMessageSlotContext) => React.ReactNode;
+    /**
+     * Draws a message in its own way: `undefined` (or a boolean, as
+     * `isCut(m) && <Card />` gives) leaves it to the panel, `null` leaves it
+     * out, and anything else is drawn in its place, without the message's frame
+     * (its name, time and actions). For a host that folds several messages into
+     * one of its own (a turn cut and resumed, drawn as one card on the first of
+     * them, the others left out). Asked of every message, streaming ones
+     * included, the reply's empty placeholder too (`null` leaves out its status
+     * bubble): return `undefined` fast for the others. A throw, while asked or
+     * while the replacement is drawn, leaves that message to the panel.
+     */
+    replaceMessage?: (message: ChatMessage, context: ChatMessageSlotContext) => React.ReactNode;
     /** Controls added to a finished message's footer. */
     messageFooterActions?: (message: ChatMessage, context: ChatMessageSlotContext) => React.ReactNode;
     /** Controls added to a conversation's row in the conversation list. */
@@ -805,6 +824,26 @@ interface ChatPanelProps {
      * `sidebar*` slots render nothing meanwhile. Default: false.
      */
     hideConversationList?: boolean;
+    /**
+     * The conversation list starts collapsed to its strip, from which the user
+     * opens it: where it would squeeze the thread, a phone or a narrow window.
+     * Read once, when the panel mounts. Default: false.
+     */
+    initialConversationListCollapsed?: boolean;
+    /**
+     * The workspace groups of the conversation list the user has opened (their
+     * keys: a workspace's id), for a host that keeps them per user. Given, every
+     * other group starts collapsed until the user opens it, so many workspaces
+     * do not push the conversations in none below the fold; one the user creates
+     * from the list opens. Read once, the first time it is given: a host still
+     * reading them passes `undefined` until it has them. The panel keeps what
+     * the user opens from then on, while the list is hidden and shown again too.
+     * Unset, groups start open and the ones the user collapses are remembered
+     * per browser.
+     */
+    expandedWorkspaceGroups?: string[];
+    /** The workspace groups the user has opened, each time they open or collapse one (see `expandedWorkspaceGroups`). */
+    onExpandedWorkspaceGroupsChange?: (keys: string[]) => void;
     /**
      * Asked before a conversation is filed into a workspace (`null`: taken out
      * of its workspace), by a drag or the row's Move menu: `false` (or a promise
@@ -826,14 +865,18 @@ interface ChatPanelProps {
     sidebarSearchThreshold?: number;
     /**
      * Names the channel a conversation was started in, on its row (`Started in
-     * {channel}`): a string names it, `null` shows nothing, `undefined` keeps
+     * {channel}`) and in the header (`Agent · {channel}`): a string names it, `null` shows nothing, `undefined` keeps
      * the panel's own name (Slack, Teams, WhatsApp, Telegram, Discord, Google
      * Chat; no other channel is shown).
      */
     channelLabel?: (channel: string) => string | null | undefined;
     /** A title beside the agent's name in the header (the conversation's, say), or a function of what is on screen. */
     headerTitle?: React.ReactNode | ((context: ChatHeaderContext) => React.ReactNode);
-    /** A line under the agent's name in the header (`Agent · Slack`, say), or a function of what is on screen. */
+    /**
+     * A line under the agent's name in the header, or a function of what is on
+     * screen. Undefined: `Agent · {channel}` for a conversation started in a
+     * channel its row names (see `channelLabel`), nothing otherwise.
+     */
     headerSubtitle?: React.ReactNode | ((context: ChatHeaderContext) => React.ReactNode);
     /**
      * Links the header's agent name to this address (an http(s) URL or a path
@@ -877,6 +920,11 @@ interface ChatMarkerRenderer {
     renderWhileStreaming?: boolean;
     /** Give it the thread's full width rather than the prose's. */
     fullWidth?: boolean;
+    /**
+     * An answer that is this marker and nothing else shows the card alone, as a
+     * note between messages: no agent name, time or actions around it.
+     */
+    standalone?: boolean;
 }
 /** What a code block renderer is drawn from. */
 interface ChatCodeBlockContext {
@@ -925,6 +973,12 @@ interface ChatPanelHandle {
      */
     getDraft: () => string;
     focusComposer: () => void;
+    /**
+     * Put *files* in the composer's tray as if the user picked them (uploaded and
+     * checked the same way), to go with the next message: files another app
+     * shared to the host. Nothing where the panel takes no files.
+     */
+    attachFiles: (files: readonly File[]) => void;
     /** Same as the Stop button; also cancels the question a voice call awaits, and stops it speaking. */
     stop: () => void;
     /**
@@ -1264,7 +1318,7 @@ interface ChatFile {
     fileId?: string;
     /** Upload status: 'pending' while uploading, 'done' when uploaded, 'error' on failure. */
     uploadStatus?: 'pending' | 'done' | 'error';
-    /** Why the upload failed, as the backend said (`detail`), when it said. */
+    /** Why the upload failed, as the backend said, when it said: its reason (README, "A refusal's reason"). */
     uploadError?: string;
 }
 /** The conversation list's search, as a host's sections read it (`sidebarSections`). */
@@ -1349,6 +1403,12 @@ interface XtmAgent {
     group?: string;
     /** Short labels shown after its name in the agent picker (`Company`), already translated. */
     badges?: string[];
+    /**
+     * The agent is meant for assignments rather than chat (`disable_chat`): the
+     * picker says "Not recommended for chat" and the composer warns while it is
+     * the one written to. It stays selectable.
+     */
+    disableChat?: boolean;
 }
 
 /**