@meshagent/meshagent-agents 0.47.1 → 0.48.0

package/CHANGELOG.md

@@ -1,15 +1,25 @@
+## [0.48.0]
+- Reworked the TS/JS agent chat stack to preserve ordered threaded messages and support injected-message threads across chat clients and process handling.
+- Added chat feed widgets and virtual scrolling to the React/Tailwind UI, improving large-thread performance.
+- Aligned `meshagent-agents-ts` with the Dart agents implementation and refreshed the shared chat/message contracts.
+- Removed the LiveKit dependency from the React package and updated shared package dependencies for the new chat stack.
+
 ## [0.47.1]
 - Added duplex messaging stream subscriptions and replay-state alignment in the TypeScript chat clients, bringing the NodeJS SDK in line with the new streaming model.
 - Reworked messaging and room client flow control so dispatch ordering, close behavior, and presence updates stay consistent under streaming loads.
 - Expanded stream and presence test coverage for the new messaging behavior.
 
 ## [0.47.0]
+- Aligned the TypeScript agent message and chat-client API with the Dart implementation, including strongly typed message constructors, `AgentFileContent`, client-tool request claiming, pending-thread matching, and direct MessagePack WebSocket transport.
+- Removed TypeScript-only dataset hydration, timeline, and derived session-state APIs from the agents package; UI-specific equivalents now live in `meshagent-tailwind`.
 - Improved TypeScript messaging clients so room delivery order and startup/presence behavior stay consistent.
 - Moved managed-agent client routing onto the Rust tunnel path and hardened agent chat-client event handling.
 - Added a `test:rust-process-e2e` entry point for the agents-ts package and expanded live chat/process-agent coverage.
 - Finished aligning CLI pagination behavior across feeds, rooms, mailboxes, scheduled tasks, and shared helpers.
 
 ## [0.46.3]
+- Chat thread sessions now retain successful client-tool completion events so restored UIs can render their outputs without re-executing tools.
+- Added SDK-owned dataset-thread hydration and canonical chat timelines, including sequence-ordered history replay before buffered live events.
 - `LivekitProtocolChannel.sendData` now clones outgoing `Uint8Array` payloads before publishing, avoiding shared-buffer mutation issues.
 
 ## [0.46.2]

package/README.md

@@ -35,6 +35,7 @@ Every protocol message is represented by a class with `toJson()` and can be pars
 
 ```ts
 import {
+  AgentFileContent,
   AgentMessage,
   TurnStart,
   agentInputContent,
@@ -44,7 +45,10 @@ const message = new TurnStart({
   threadId: "dataset://threads/example",
   content: agentInputContent({
     text: "Summarize this file.",
-    attachments: ["dataset://assets/files/report.pdf"],
+    attachments: [new AgentFileContent({
+      url: "dataset://assets/files/report.pdf",
+      name: "report.pdf",
+    })],
   }),
   provider: "openai",
   model: "gpt-5.4",
@@ -62,8 +66,8 @@ The package exports the message type constants as well, for example `agentTurnSt
 
 ```ts
 import {
+  AgentTextContentDelta,
   MessagingChatClient,
-  agentTextContentDeltaType,
 } from "@meshagent/meshagent-agents";
 import type { RoomClient } from "@meshagent/meshagent";
 
@@ -87,9 +91,8 @@ await session.sendText({
 });
 
 for await (const event of chat.events) {
-  if (event.message.type === agentTextContentDeltaType) {
-    const delta = event.message as typeof event.message & { text: string };
-    process.stdout.write(delta.text);
+  if (event.message instanceof AgentTextContentDelta) {
+    process.stdout.write(event.message.text);
   }
 }
 ```
@@ -111,6 +114,26 @@ await session.close();
 
 `ChatThreadSession` tracks local pending inputs in `session.pendingInputs`. Pending input state is updated when accepted, started, steered, rejected, ended, or cleared messages arrive from the agent.
 
+## WebSocket Chat Client
+
+`WebSocketChatClient` is the direct MessagePack WebSocket transport. It uses the `meshagent-msgpack` and `meshagent-agent.<token>` subprotocols and reconnects by default.
+
+```ts
+import { WebSocketChatClient } from "@meshagent/meshagent-agents";
+
+const chat = new WebSocketChatClient({
+  url: new URL("wss://example.test/messages"),
+  token: participantToken,
+  participantName: "user@example.com",
+});
+
+await chat.start();
+const { session } = await chat.startThread({
+  message: "Hello",
+  attachments: [],
+});
+```
+
 ## Custom Transports
 
 Use `BaseChatClient` if you want to send agent messages through another transport. Implement `sendAgentMessage(...)` and feed inbound messages back through `handleAgentMessage(...)`.