eve 0.46.0 → 0.46.1

package/docs/guides/client/streaming.mdx

@@ -75,7 +75,7 @@ for await (const event of response) {
 }
 ```
 
-`message.appended` and `reasoning.appended` are incremental delta events. eve may combine adjacent deltas of the same type while a durable stream write is in flight, but preserves their text and event ordering; any different event is a barrier. Their completed forms, `message.completed` and `reasoning.completed`, are the compatibility path for clients that don't render deltas.
+`message.appended`, `reasoning.appended`, and `action.input.appended` are incremental delta events. eve may combine adjacent deltas for the same text block or tool call while a durable stream write is in flight, but preserves their text and event ordering. A different event type, tool `callId`, or stream coordinate is a barrier. The completed text forms, `message.completed` and `reasoning.completed`, are the compatibility path for clients that don't render deltas. A streamed tool input is complete when the matching validated call arrives in `actions.requested`.
 
 ## Handle event types
 
@@ -98,23 +98,26 @@ function handleEvent(event: MessageStreamEvent) {
 
 The most common UI events are:
 
-| Event                | Use                                                                            |
-| -------------------- | ------------------------------------------------------------------------------ |
-| `message.received`   | Confirm the user message landed; `data.parts` includes text and file metadata. |
-| `reasoning.appended` | Render reasoning deltas when the model provides them.                          |
-| `message.appended`   | Render assistant text deltas.                                                  |
-| `actions.requested`  | Show tool calls as the model requests them, before execution.                  |
-| `action.partial`     | Update a generator tool's provisional output snapshot.                         |
-| `action.result`      | Show tool call results.                                                        |
-| `input.requested`    | Pause the UI for approval or a question answer.                                |
-| `input.resolved`     | Record the server-accepted outcome and response for each human-input request.  |
-| `result.completed`   | Read structured output from an [output schema](./output-schema).               |
-| `session.waiting`    | Enable the composer; the same fixed session handle accepts the next message.   |
-| `session.completed`  | Mark the conversation terminal.                                                |
-| `session.failed`     | Mark the conversation failed.                                                  |
+| Event                   | Use                                                                            |
+| ----------------------- | ------------------------------------------------------------------------------ |
+| `message.received`      | Confirm the user message landed; `data.parts` includes text and file metadata. |
+| `reasoning.appended`    | Render reasoning deltas when the model provides them.                          |
+| `message.appended`      | Render assistant text deltas.                                                  |
+| `action.input.appended` | Accumulate raw tool-input deltas before validation completes.                  |
+| `actions.requested`     | Show tool calls as the model requests them, before execution.                  |
+| `action.partial`        | Update a generator tool's provisional output snapshot.                         |
+| `action.result`         | Show tool call results.                                                        |
+| `input.requested`       | Pause the UI for approval or a question answer.                                |
+| `input.resolved`        | Record the server-accepted outcome and response for each human-input request.  |
+| `result.completed`      | Read structured output from an [output schema](./output-schema).               |
+| `session.waiting`       | Enable the composer; the same fixed session handle accepts the next message.   |
+| `session.completed`     | Mark the conversation terminal.                                                |
+| `session.failed`        | Mark the conversation failed.                                                  |
 
 For the complete event table, see [Sessions, runs & streaming](../../concepts/sessions-runs-and-streaming).
 
+Each `action.input.appended` event stores `inputTextDelta` and its zero-based UTF-16 code-unit `inputTextOffset`, so consumers can reject a gap instead of concatenating corrupt input. The default message reducer starts or restarts at offset `0` and ignores a nonzero offset that is not contiguous. It accumulates accepted deltas into a `dynamic-tool` part with `state: "input-streaming"`; its `inputText` field contains cumulative raw text that may be incomplete JSON. The matching `actions.requested` event upgrades the same `toolCallId` to `state: "input-available"` and puts the validated value in `input`.
+
 When a submitted message includes attachments, `message.received.data.message` stays the
 flattened compatibility summary, while `message.received.data.parts` carries renderable text and
 file metadata. File parts never include raw bytes or internal sandbox paths; `url` appears only for

package/docs/guides/dev-tui.md

@@ -20,6 +20,7 @@ The transcript remains in your terminal scrollback after you exit. Run `/help` i
 | `/deploy`     | Deploy the agent to Vercel production. Links the directory first if needed.                                                                               |
 | `/vc:install` | Install the Vercel CLI.                                                                                                                                   |
 | `/vc:login`   | Log in to Vercel or restore access to a remote deployment.                                                                                                |
+| `/info`       | Show the resolved application, compiled artifacts, discovery diagnostics, and messaging routes.                                                           |
 | `/loglevel`   | Choose which server and agent logs appear in the transcript.                                                                                              |
 | `/traces`     | Open the local trace viewer. Pass a trace ID prefix to open a specific trace.                                                                             |
 | `/reset`      | Start a fresh session.                                                                                                                                    |
@@ -29,7 +30,7 @@ The transcript remains in your terminal scrollback after you exit. Run `/help` i
 | `/exit`       | Quit the UI.                                                                                                                                              |
 | `/help`       | List available commands.                                                                                                                                  |
 
-`/model`, `/add`, `/deploy`, and `/traces` are available when `eve dev` runs locally. They are unavailable when the UI connects to a server with `--url`.
+`/model`, `/add`, `/deploy`, `/info`, and `/traces` are available when `eve dev` runs locally. They are unavailable when the UI connects to a server with `--url`.
 
 ## Add an integration
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "eve",
-  "version": "0.46.0",
+  "version": "0.46.1",
   "private": false,
   "description": "Filesystem-first framework for durable backend AI agents that run anywhere.",
   "keywords": [
@@ -390,7 +390,7 @@
     "@chat-adapter/state-memory": "4.34.0",
     "@chat-adapter/twilio": "4.34.0",
     "@clack/core": "1.3.1",
-    "@linqapp/chat-sdk-adapter": "^0.3.0",
+    "@linqapp/chat-sdk-adapter": "^0.5.1",
     "@modelcontextprotocol/server": "2.0.0",
     "@nuxt/kit": "^4.0.0",
     "@opentelemetry/context-async-hooks": "2.6.1",