eve 0.90.0 → 0.91.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (185) hide show
  1. package/CHANGELOG.md +34 -23
  2. package/dist/src/channel/auth/http-basic.js +1 -1
  3. package/dist/src/channel/channel-operations.d.ts +1 -1
  4. package/dist/src/channel/types.d.ts +2 -0
  5. package/dist/src/cli/dev/tui/prompt-commands.d.ts +1 -1
  6. package/dist/src/client/session.d.ts +1 -1
  7. package/dist/src/compiled/.vendor-stamp.json +1 -1
  8. package/dist/src/execution/dynamic-workflow/tool.js +1 -1
  9. package/dist/src/execution/proxied-deliver-step.js +1 -1
  10. package/dist/src/execution/sandbox/bash.js +2 -2
  11. package/dist/src/execution/session/active-turn.js +1 -1
  12. package/dist/src/execution/session/admission.d.ts +6 -0
  13. package/dist/src/execution/session/admission.js +1 -1
  14. package/dist/src/execution/session/delivery-facts.js +1 -1
  15. package/dist/src/execution/session/next-input.d.ts +2 -2
  16. package/dist/src/execution/session/next-input.js +1 -1
  17. package/dist/src/execution/session/program.js +1 -1
  18. package/dist/src/execution/session-inbox/inbox.d.ts +2 -2
  19. package/dist/src/execution/session-inbox/inbox.js +1 -1
  20. package/dist/src/execution/session-inbox/protocol.js +1 -1
  21. package/dist/src/execution/tools/agent-router-workflow.js +1 -1
  22. package/dist/src/harness/compaction/engine.js +2 -2
  23. package/dist/src/harness/current-messages.js +1 -1
  24. package/dist/src/harness/emission.d.ts +3 -0
  25. package/dist/src/harness/emission.js +1 -1
  26. package/dist/src/harness/facts.d.ts +5 -2
  27. package/dist/src/harness/facts.js +1 -1
  28. package/dist/src/harness/model-call/call.d.ts +7 -1
  29. package/dist/src/harness/model-call/call.js +3 -1
  30. package/dist/src/harness/provider-tool-history.d.ts +8 -0
  31. package/dist/src/harness/provider-tool-history.js +1 -1
  32. package/dist/src/harness/session-machine/transitions.d.ts +3 -2
  33. package/dist/src/harness/step/after-model.js +1 -1
  34. package/dist/src/harness/step/context.js +1 -1
  35. package/dist/src/harness/step/intake.js +1 -1
  36. package/dist/src/harness/step/prompt.js +1 -1
  37. package/dist/src/harness/tool-history-repair.d.ts +2 -0
  38. package/dist/src/harness/tool-history-repair.js +1 -1
  39. package/dist/src/harness/tool-loop.js +1 -1
  40. package/dist/src/internal/application/stamped-package-version.js +1 -1
  41. package/dist/src/protocol/session-events/families/delivery.d.ts +5 -3
  42. package/dist/src/protocol/session-events/families/delivery.js +1 -1
  43. package/dist/src/protocol/session-projection/fold.js +1 -1
  44. package/dist/src/public/channels/discord/hitl.js +1 -1
  45. package/dist/src/public/channels/slack/hitl.d.ts +2 -1
  46. package/dist/src/public/channels/slack/hitl.js +3 -3
  47. package/dist/src/public/channels/slack/interaction-cards.js +1 -1
  48. package/dist/src/public/channels/slack/request-card-render.js +1 -1
  49. package/dist/src/public/channels/teams/hitl.js +1 -1
  50. package/dist/src/public/channels/teams/verify.js +1 -1
  51. package/dist/src/public/definitions/hook.d.ts +90 -7
  52. package/dist/src/public/definitions/hook.js +1 -1
  53. package/dist/src/public/hooks/index.d.ts +3 -2
  54. package/dist/src/reactions/continuation.d.ts +19 -0
  55. package/dist/src/reactions/continuation.js +1 -0
  56. package/dist/src/reactions/intents.d.ts +10 -4
  57. package/dist/src/reactions/intents.js +1 -1
  58. package/dist/src/reactions/kinds/hook.js +1 -1
  59. package/dist/src/reactions/runner.js +1 -1
  60. package/dist/src/reactions/state.d.ts +15 -2
  61. package/dist/src/reactions/state.js +1 -1
  62. package/dist/src/runtime/resolve-connection.js +1 -1
  63. package/dist/src/runtime/subagents/workflow.js +1 -1
  64. package/dist/src/setup/primitives/open-url.js +1 -1
  65. package/dist/src/setup/scaffold/create/project.js +1 -1
  66. package/dist/src/shared/value-delta.d.ts +5 -4
  67. package/dist/src/shared/value-delta.js +1 -1
  68. package/dist/src/tools/provided/ask-question-workflow.js +1 -1
  69. package/dist/src/tools/provided/sleep-workflow.js +1 -1
  70. package/dist/src/tools/provided/web-fetch.js +1 -1
  71. package/docs/agent-config.md +199 -222
  72. package/docs/channels/chat-sdk.mdx +60 -64
  73. package/docs/channels/custom.mdx +264 -281
  74. package/docs/channels/discord.mdx +176 -123
  75. package/docs/channels/eve.mdx +136 -206
  76. package/docs/channels/github.mdx +24 -22
  77. package/docs/channels/linear.mdx +30 -30
  78. package/docs/channels/linq.mdx +25 -13
  79. package/docs/channels/mcp.mdx +154 -116
  80. package/docs/channels/overview.mdx +31 -32
  81. package/docs/channels/photon.mdx +32 -56
  82. package/docs/channels/slack.mdx +538 -375
  83. package/docs/channels/teams.mdx +40 -26
  84. package/docs/channels/telegram.mdx +13 -13
  85. package/docs/channels/twilio.mdx +11 -11
  86. package/docs/code-extension.mdx +40 -42
  87. package/docs/concepts/built-in-tools.md +89 -57
  88. package/docs/concepts/context-control.md +20 -20
  89. package/docs/concepts/default-harness.md +20 -36
  90. package/docs/concepts/execution-model-and-durability.mdx +96 -160
  91. package/docs/concepts/project-structure.mdx +21 -14
  92. package/docs/concepts/security-model.md +27 -27
  93. package/docs/concepts/sessions-runs-and-streaming.md +184 -198
  94. package/docs/concepts/state.md +7 -15
  95. package/docs/connections/mcp.mdx +109 -93
  96. package/docs/connections/openapi.mdx +57 -59
  97. package/docs/connections/overview.mdx +175 -170
  98. package/docs/evals/assertions.mdx +36 -29
  99. package/docs/evals/cases.mdx +38 -42
  100. package/docs/evals/judge.mdx +21 -29
  101. package/docs/evals/overview.mdx +42 -38
  102. package/docs/evals/reporters.mdx +54 -27
  103. package/docs/evals/running.mdx +15 -8
  104. package/docs/evals/targets.mdx +16 -19
  105. package/docs/evals/tool-stubs.mdx +111 -97
  106. package/docs/experimental/dynamic-schedules.mdx +118 -63
  107. package/docs/extensions.md +58 -65
  108. package/docs/getting-started.mdx +4 -6
  109. package/docs/guides/auth-and-route-protection.md +87 -70
  110. package/docs/guides/client/continuations.mdx +23 -26
  111. package/docs/guides/client/messages.mdx +47 -66
  112. package/docs/guides/client/output-schema.mdx +8 -8
  113. package/docs/guides/client/overview.mdx +45 -43
  114. package/docs/guides/client/streaming.mdx +62 -71
  115. package/docs/guides/decide.md +24 -79
  116. package/docs/guides/deployment/meta.json +1 -1
  117. package/docs/guides/deployment/overview.md +27 -18
  118. package/docs/guides/deployment/self-hosted-operations.md +99 -0
  119. package/docs/guides/deployment/self-hosting.md +63 -80
  120. package/docs/guides/deployment/vercel.mdx +31 -27
  121. package/docs/guides/deployment/workflow-worlds.md +100 -0
  122. package/docs/guides/dev-tui.md +48 -41
  123. package/docs/guides/dynamic-capabilities.md +49 -50
  124. package/docs/guides/frontend/nextjs.mdx +2 -2
  125. package/docs/guides/frontend/nuxt.mdx +11 -11
  126. package/docs/guides/frontend/overview.mdx +1 -1
  127. package/docs/guides/frontend/sveltekit.mdx +11 -11
  128. package/docs/guides/frontend/tanstack.mdx +16 -16
  129. package/docs/guides/frontend/use-eve-agent-svelte.mdx +21 -21
  130. package/docs/guides/frontend/use-eve-agent-vue.mdx +22 -22
  131. package/docs/guides/frontend/use-eve-agent.mdx +25 -25
  132. package/docs/guides/hooks.md +152 -106
  133. package/docs/guides/instrumentation/agent-runs.mdx +26 -30
  134. package/docs/guides/instrumentation/instrumentation.mdx +49 -76
  135. package/docs/guides/instrumentation/meta.json +1 -1
  136. package/docs/guides/instrumentation/otel.mdx +113 -179
  137. package/docs/guides/remote-agents.md +125 -187
  138. package/docs/guides/self-modification.md +18 -18
  139. package/docs/guides/session-context.md +16 -16
  140. package/docs/install-integrations.mdx +26 -24
  141. package/docs/instructions.mdx +37 -42
  142. package/docs/memory/custom-provider.md +35 -41
  143. package/docs/memory/file.md +93 -76
  144. package/docs/memory/overview.mdx +145 -156
  145. package/docs/patterns/durable-cross-channel-notifications.md +15 -19
  146. package/docs/patterns/dynamic-scheduling.md +19 -23
  147. package/docs/patterns/multi-tenant-approvals.md +17 -22
  148. package/docs/patterns/multi-tenant-auth.md +43 -42
  149. package/docs/patterns/multi-tenant-memory.md +39 -36
  150. package/docs/patterns/voice-notes.md +3 -3
  151. package/docs/protocols/acp.md +13 -13
  152. package/docs/protocols/ucp.mdx +7 -7
  153. package/docs/reference/agent-files.md +6 -6
  154. package/docs/reference/cli.md +99 -98
  155. package/docs/reference/telemetry.md +1 -1
  156. package/docs/reference/typescript-api.md +52 -53
  157. package/docs/responsible-use.md +2 -2
  158. package/docs/sandbox/custom-providers.mdx +60 -56
  159. package/docs/sandbox/default.mdx +23 -24
  160. package/docs/sandbox/docker.mdx +16 -10
  161. package/docs/sandbox/index.mdx +93 -61
  162. package/docs/sandbox/just-bash.mdx +17 -11
  163. package/docs/sandbox/troubleshooting.mdx +29 -23
  164. package/docs/sandbox/vercel.mdx +45 -52
  165. package/docs/schedules.mdx +65 -54
  166. package/docs/skills.mdx +74 -49
  167. package/docs/subagents/index.mdx +97 -136
  168. package/docs/tools/human-in-the-loop.md +160 -90
  169. package/docs/tools/meta.json +1 -1
  170. package/docs/tools/overview.mdx +229 -237
  171. package/docs/tools/tasks.md +118 -117
  172. package/docs/tools/workflows.mdx +447 -543
  173. package/docs/tutorial/connect-a-warehouse.mdx +11 -13
  174. package/docs/tutorial/first-agent.mdx +14 -16
  175. package/docs/tutorial/guard-the-spend.mdx +6 -8
  176. package/docs/tutorial/how-it-runs.mdx +8 -8
  177. package/docs/tutorial/query-sample-data.mdx +8 -8
  178. package/docs/tutorial/remember-definitions.mdx +4 -4
  179. package/docs/tutorial/run-analysis.mdx +20 -22
  180. package/docs/tutorial/ship-it.mdx +19 -19
  181. package/docs/tutorial/team-playbooks.mdx +9 -9
  182. package/docs/use-cases.mdx +13 -11
  183. package/package.json +1 -1
  184. package/docs/guides/instrumentation/migration.md +0 -96
  185. package/docs/tools/tasks-upgrade.md +0 -218
@@ -3,7 +3,7 @@ title: "SvelteKit"
3
3
  description: "Run an eve agent and a SvelteKit app as one project with the eveSvelteKit Vite plugin."
4
4
  ---
5
5
 
6
- `eve/sveltekit` runs a SvelteKit frontend and an eve agent as one project instead of two services. The `eveSvelteKit()` Vite plugin puts both on one dev server and one Vercel deploy, and [`useEveAgent`](./use-eve-agent-svelte) finds the mounted routes on its own. There's no CORS to configure and no URL env vars to keep in sync.
6
+ `eve/sveltekit` runs a SvelteKit frontend and an eve agent as one project. The `eveSvelteKit()` Vite plugin puts both on one dev server and one Vercel deploy. [`useEveAgent`](./use-eve-agent-svelte) finds the mounted routes on its own, so you configure no CORS or URL env vars.
7
7
 
8
8
  ## Prerequisites
9
9
 
@@ -38,11 +38,11 @@ export default defineConfig({
38
38
  });
39
39
  ```
40
40
 
41
- The plugin accepts only two options, `eveRoot` and `eveBuildCommand`.
41
+ The plugin accepts two options, `eveRoot` and `eveBuildCommand`.
42
42
 
43
43
  ## Call the binding
44
44
 
45
- With the plugin in `vite.config.ts`, components call [`useEveAgent`](./use-eve-agent-svelte) from `eve/svelte` and don't pass `baseUrl`:
45
+ With the plugin registered, components call [`useEveAgent`](./use-eve-agent-svelte) from `eve/svelte` and don't pass `baseUrl`:
46
46
 
47
47
  ```svelte
48
48
  <script lang="ts">
@@ -70,12 +70,12 @@ With the plugin in `vite.config.ts`, components call [`useEveAgent`](./use-eve-a
70
70
  </form>
71
71
  ```
72
72
 
73
- The browser still needs a production authentication policy. See [Authenticate browser requests](./overview#authenticate-browser-requests) for the default fail-closed behavior and channel configuration.
73
+ The browser still needs a production authentication policy. See [Authenticate browser requests](./overview#authenticate-browser-requests) for the default policy, which rejects unverified requests, and for channel configuration.
74
74
 
75
75
  ## Dev vs deploy topology
76
76
 
77
- - **Local dev.** `npm run dev` boots the eve dev server next to SvelteKit and proxies the eve routes to it, so the browser only ever hits the SvelteKit origin. `npm run build && npm run preview` behaves the same way: the preview server gets its own eve route proxy and either reuses the shared eve server or starts one.
78
- - **Vercel.** The SvelteKit app and the eve runtime deploy as a single project. On Vercel builds the plugin adds Build Output [`services`](https://vercel.com/docs/services) for eve and a `routes` entry that sends `/eve/v1/**` to that service before filesystem routing; the SvelteKit app remains the default app. No `vercel.json` is required. By default the generated service runs the installed eve binary from the SvelteKit app's dependencies, so the agent directory does not need its own `package.json`. When the agent needs its own build step, set `eveBuildCommand`:
77
+ - **Local dev.** `npm run dev` starts the eve dev server next to SvelteKit and proxies the eve routes to it. The browser talks only to the SvelteKit origin. `npm run build && npm run preview` works the same way: the preview server proxies the eve routes and reuses the shared eve server or starts one.
78
+ - **Vercel.** The SvelteKit app and the eve runtime deploy as a single project. On Vercel builds, the plugin adds an eve [service](https://vercel.com/docs/services) and routes `/eve/v1/**` to it before filesystem routing. The SvelteKit app serves everything else, and no `vercel.json` is required. By default, the generated service runs the installed eve binary from the SvelteKit app's dependencies, so the agent directory doesn't need its own `package.json`. When the agent needs its own build step, set `eveBuildCommand`:
79
79
 
80
80
  ```ts
81
81
  export default defineConfig({
@@ -98,7 +98,7 @@ The browser still needs a production authentication policy. See [Authenticate br
98
98
 
99
99
  ## Managing vercel.json yourself
100
100
 
101
- When `vercel.json` declares [`services`](https://vercel.com/docs/services), the plugin generates nothing and your configuration owns routing. It must include the eve service (`framework: "eve"`) and a rewrite that exposes the eve transport, or the build fails:
101
+ When `vercel.json` declares [`services`](https://vercel.com/docs/services), the plugin generates nothing, and your configuration controls routing. It must include the eve service (`framework: "eve"`) and a rewrite that sends `/eve/v1/*` requests to it, or the build fails:
102
102
 
103
103
  ```json title="vercel.json"
104
104
  {
@@ -110,12 +110,12 @@ When `vercel.json` declares [`services`](https://vercel.com/docs/services), the
110
110
  }
111
111
  ```
112
112
 
113
- ### Migrating from experimentalServices
113
+ ### Remove `experimentalServices`
114
114
 
115
- Earlier versions of the plugin wrote the legacy `experimentalServices` field into `vercel.json`. Vercel no longer routes that model, so the plugin now ignores the field and warns when it sees one. Migrate either way:
115
+ Vercel doesn't route the `experimentalServices` field in `vercel.json`: both services build, but every `/eve/v1/*` request returns `NOT_FOUND`. The plugin ignores the field and warns that `vercel.json defines experimentalServices`. Remove it in one of two ways:
116
116
 
117
- - **Generated (default).** Delete `vercel.json` (or just its `experimentalServices` block) and set the project's Framework Preset back to SvelteKit. The plugin generates the eve service and its routing on every Vercel build.
118
- - **Hand-maintained.** Replace `experimentalServices` with the stable `services` and `rewrites` shown above, and keep the Services Framework Preset.
117
+ - **Generated (default).** Delete `vercel.json` (or its `experimentalServices` block) and set the project's Framework Preset to SvelteKit. The plugin generates the eve service and its routing on every Vercel build.
118
+ - **Hand-maintained.** Replace `experimentalServices` with the `services` and `rewrites` shown above, and keep the Services Framework Preset.
119
119
 
120
120
  ## What to read next
121
121
 
@@ -3,7 +3,7 @@ title: "TanStack Start"
3
3
  description: "Run an eve agent and a TanStack Start app as one project with the eveTanStack Vite plugin."
4
4
  ---
5
5
 
6
- `eve/tanstack` runs a TanStack Start frontend and an eve agent as one project instead of two services. The `eveTanStack()` Vite plugin puts both on one dev server and one Vercel deploy, and [`useEveAgent`](./overview) from `eve/react` finds the mounted routes on its own. There's no CORS to configure and no URL env vars to keep in sync.
6
+ `eve/tanstack` runs a TanStack Start frontend and an eve agent as one project. The `eveTanStack()` Vite plugin puts both on one dev server and one Vercel deploy. [`useEveAgent`](./overview) from `eve/react` finds the mounted routes on its own, so you configure no CORS or URL env vars.
7
7
 
8
8
  ## Prerequisites
9
9
 
@@ -19,7 +19,7 @@ Run the Web Chat installer and choose **TanStack Start** when it asks which fram
19
19
  eve add channel/web
20
20
  ```
21
21
 
22
- In automation, answer the framework and hosting questions up front. Without a `web-framework` answer, non-interactive installs use Next.js:
22
+ In automation, answer the framework and hosting questions up front. Omit `web-framework` to install Next.js:
23
23
 
24
24
  ```bash
25
25
  eve add channel/web --non-interactive \
@@ -27,18 +27,18 @@ eve add channel/web --non-interactive \
27
27
  --answer 'web-hosting="vercel"'
28
28
  ```
29
29
 
30
- The installer creates a TanStack Start app under `apps/web/` and adds the `dev:web` and `build:web` scripts. It asks how to deploy it:
30
+ The installer creates a TanStack Start app under `apps/web/`, adds the `dev:web` and `build:web` scripts, and asks how to deploy it:
31
31
 
32
- - **Vercel services** (recommended) deploys Web Chat and the agent as separate services. Run both locally with `pnpm dev:all`; you don't need to link a Vercel project to do that.
33
- - **TanStack Start** hosts the agent in the TanStack Start app through `eveTanStack()`. Run it with `pnpm dev:web`. The app lives in `apps/web/` while its dependencies are in the project root `package.json`, so a Vercel deploy from the project root doesn't build it. Choose **Vercel services** to deploy Web Chat on Vercel.
32
+ - **Vercel services** (recommended) deploys Web Chat and the agent as separate services. Run both locally with `pnpm dev:all`, without linking a Vercel project.
33
+ - **TanStack Start** hosts the agent in the TanStack Start app through `eveTanStack()`. Run it with `pnpm dev:web`. A Vercel deploy from the project root doesn't build the app, because the app's dependencies are in the root `package.json`. Choose **Vercel services** to deploy Web Chat on Vercel.
34
34
 
35
- Rerun `eve add channel/web --skip-install` with the other choice to switch modes; the installer removes the `vercel.ts` and scripts it wrote for the previous one. When `apps/web/` already contains a Web Chat app, the installer keeps that app's framework and stops if you answer a different one. To switch between Next.js and TanStack Start, remove `apps/web/` first.
35
+ To switch hosting modes, rerun `eve add channel/web --skip-install` with the other choice. The installer removes the `vercel.ts` and scripts it wrote for the previous mode. An existing Web Chat app in `apps/web/` keeps its framework, and the installer stops if you answer a different one. To switch between Next.js and TanStack Start, remove `apps/web/` first.
36
36
 
37
37
  Sign in with Vercel setup is available only for the Next.js Web Chat app, so the TanStack Start installer doesn't ask about authentication.
38
38
 
39
- The chat has the same URL-addressed durable sessions as the [Next.js Web Chat](./nextjs#give-each-conversation-a-url): `/`, `/s`, and `/s/$sessionId`. Before accepting production browser traffic, replace the generated placeholder authorization policy. See [Authenticate browser requests](./overview#authenticate-browser-requests).
39
+ The chat uses the same routes as the [Next.js Web Chat](./nextjs#give-each-conversation-a-url): `/`, `/s`, and `/s/$sessionId`, one URL per session. Before accepting production browser traffic, replace the generated placeholder authorization policy. See [Authenticate browser requests](./overview#authenticate-browser-requests).
40
40
 
41
- The installer doesn't support selecting a workspace agent for single-app hosting: a workspace agent always deploys as a separate Vercel service. If you already have a TanStack Start app, skip the installer and follow the steps below.
41
+ A workspace agent always deploys as a separate Vercel service, because the installer doesn't support single-app hosting for it. If you already have a TanStack Start app, skip the installer and follow the steps below.
42
42
 
43
43
  ## Register the Vite plugin
44
44
 
@@ -71,7 +71,7 @@ export default defineConfig({
71
71
  });
72
72
  ```
73
73
 
74
- Without `nitro()` registered, Vite fails at startup with an error naming the missing plugin instead of serving a project whose eve routes would return 404.
74
+ Without `nitro()` registered, Vite fails at startup with an error naming the missing plugin.
75
75
 
76
76
  ### `eveTanStack` options
77
77
 
@@ -100,7 +100,7 @@ export default defineConfig({
100
100
 
101
101
  ## Call the hook
102
102
 
103
- With the plugin in `vite.config.ts`, components call [`useEveAgent`](./overview) from `eve/react` and don't pass `baseUrl`:
103
+ With the plugin registered, components call [`useEveAgent`](./overview) from `eve/react` and don't pass `baseUrl`:
104
104
 
105
105
  ```tsx title="src/routes/index.tsx"
106
106
  import { createFileRoute } from "@tanstack/react-router";
@@ -148,14 +148,14 @@ function Chat() {
148
148
  }
149
149
  ```
150
150
 
151
- The browser still needs a production authentication policy. See [Authenticate browser requests](./overview#authenticate-browser-requests) for the default fail-closed behavior and channel configuration.
151
+ The browser still needs a production authentication policy. See [Authenticate browser requests](./overview#authenticate-browser-requests) for the default policy, which rejects unverified requests, and for channel configuration.
152
152
 
153
- eve ships hook bindings for React, Vue, and Svelte. A TanStack Start app that uses Solid can still mount the agent with this plugin and call it through the [Client SDK](../client/overview).
153
+ eve ships hook bindings for React, Vue, and Svelte. A TanStack Start app that uses Solid can mount the agent with this plugin and call it through the [Client SDK](../client/overview).
154
154
 
155
155
  ## Dev vs deploy topology
156
156
 
157
- - **Local dev.** `npm run dev` boots the eve dev server next to TanStack Start and Nitro proxies `/eve/v1/**` to it, so the browser only ever hits the TanStack Start origin. The plugin uses the server named by `EVE_BASE_URL` when that variable is set, then a healthy shared eve dev server already running for the app, and otherwise starts one. A server the plugin starts stops when the Vite dev server closes (Vite 8.3 or later; earlier versions stop it when the process exits). Any tool that loads `vite.config.ts` in serve mode starts or reuses this server, including test runners such as Vitest. Keep `eveTanStack()` out of a separate test config if you don't want that.
158
- - **Vercel.** The TanStack Start app and the eve runtime deploy as a single project. On Vercel builds the plugin adds Build Output [`services`](https://vercel.com/docs/services) for eve and a `routes` entry that sends `/eve/v1/**` to that service before filesystem routing and before any routes you declare in `nitro({ vercel: { config } })`; the TanStack Start app remains the default app. No `vercel.json` is required. By default the generated service runs the installed eve binary from the TanStack Start app's dependencies, so the agent directory does not need its own `package.json`. When the agent needs its own build step, set `eveBuildCommand`:
157
+ - **Local dev.** `npm run dev` starts the eve dev server next to TanStack Start, and Nitro proxies `/eve/v1/**` to it. The browser talks only to the TanStack Start origin. The plugin uses the server named by `EVE_BASE_URL` when set. Otherwise it reuses a healthy shared eve dev server for the app, or starts one. A server the plugin starts stops when the Vite dev server closes (Vite 8.3 or later; earlier versions stop it when the process exits). Any tool that loads `vite.config.ts` in serve mode, such as Vitest, starts or reuses this server. To avoid that, keep `eveTanStack()` out of a separate test config.
158
+ - **Vercel.** The TanStack Start app and the eve runtime deploy as a single project. On Vercel builds, the plugin adds an eve [service](https://vercel.com/docs/services) and routes `/eve/v1/**` to it. This route runs before filesystem routing and before any routes you declare in `nitro({ vercel: { config } })`. The TanStack Start app serves everything else, and no `vercel.json` is required. By default, the generated service runs the installed eve binary from the TanStack Start app's dependencies, so the agent directory doesn't need its own `package.json`. When the agent needs its own build step, set `eveBuildCommand`:
159
159
 
160
160
  ```ts
161
161
  export default defineConfig({
@@ -178,11 +178,11 @@ eve ships hook bindings for React, Vue, and Svelte. A TanStack Start app that us
178
178
  });
179
179
  ```
180
180
 
181
- `eve build` and `vite build` (with Nitro's default Node.js preset) both write `.output/`. When the agent lives in the TanStack Start project root, build and serve eve from a separate directory (set `eveRoot` to it) so the two outputs do not overwrite each other. See [Self-host eve](../deployment/self-hosting) for running the eve service.
181
+ `eve build` and `vite build` (with Nitro's default Node.js preset) both write `.output/`. When the agent lives in the TanStack Start project root, the two outputs overwrite each other. Build and serve eve from a separate directory instead, and set `eveRoot` to it. See [Self-host eve](../deployment/self-hosting) for running the eve service.
182
182
 
183
183
  ## Managing vercel.json yourself
184
184
 
185
- When `vercel.json` declares [`services`](https://vercel.com/docs/services), the plugin generates nothing and your configuration owns routing. It must include the eve service (`framework: "eve"`) and a rewrite that exposes the eve transport, or the build fails:
185
+ When `vercel.json` declares [`services`](https://vercel.com/docs/services), the plugin generates nothing, and your configuration controls routing. It must include the eve service (`framework: "eve"`) and a rewrite that sends `/eve/v1/*` requests to it, or the build fails:
186
186
 
187
187
  ```json title="vercel.json"
188
188
  {
@@ -3,7 +3,7 @@ title: "useEveAgent (Svelte)"
3
3
  description: "Use the eve Svelte binding and its Svelte-specific reactive interface."
4
4
  ---
5
5
 
6
- `useEveAgent()` from `eve/svelte` exposes the shared eve frontend client through Svelte 5 reactive getters and methods. Read the [frontend overview](./overview) for session behavior, messages, human input, authorization, callbacks, and persistence. This page covers the Svelte-specific interface.
6
+ `useEveAgent()` from `eve/svelte` exposes the shared eve frontend client through Svelte 5 reactive getters and methods. See the [frontend overview](./overview) for session behavior, messages, human input, authorization, callbacks, and persistence.
7
7
 
8
8
  On SvelteKit, register the [`eveSvelteKit` Vite plugin](./sveltekit) to mount the agent routes on the application origin.
9
9
 
@@ -45,26 +45,25 @@ Call the binding once for a conversation and read its reactive getters directly.
45
45
 
46
46
  The state fields are reactive getters; the commands are ordinary methods:
47
47
 
48
- | Property | Svelte shape |
49
- | ----------------------------------------------------------------------------------------- | -------------------------------------------------- |
50
- | `messages`, `agents` | Reactive getters for each projected snapshot field |
51
- | `view` | `SessionView` |
52
- | `status` | `UseEveAgentStatus` |
53
- | `error` | `Error \| undefined` |
54
- | `events` | `readonly SessionStreamEvent[]` |
55
- | `session` | `ClientSessionState \| undefined` |
56
- | `send`, `respond`, `prewarm`, `resume`, `cancel`, `clear`, `compact`, `end`, `newSession` | Methods |
48
+ | Property | Svelte shape |
49
+ | --------------------------------------------------------------------------------------------------- | ---------------------------------------- |
50
+ | `messages`, `agents` | Reactive getters for the snapshot fields |
51
+ | `view` | `SessionView` |
52
+ | `status` | `UseEveAgentStatus` |
53
+ | `error` | `Error \| undefined` |
54
+ | `events` | `readonly SessionStreamEvent[]` |
55
+ | `session` | `ClientSessionState \| undefined` |
56
+ | `send`, `respond`, `prewarm`, `resume`, `follow`, `cancel`, `clear`, `compact`, `end`, `newSession` | Methods |
57
57
 
58
58
  Read the getters directly in templates, `$derived`, or `$effect`. The [`useEveAgent` reference](./use-eve-agent#returned-state) describes what each value and command does.
59
59
 
60
60
  ## Send a message
61
61
 
62
- Call `agent.send(text)` for text or pass content parts for attachments. The API and transport behavior match the [sending reference](./use-eve-agent#sending); only reactive access differs in Svelte. `send()` and `respond()` resolve with a `Delivery` receipt when accepted, without waiting for execution to finish. Read its `sessionId` and `deliveryId`, or use the receipt's [delivery reads](../client/messages#reusable-delivery-reads).
62
+ Call `agent.send(text)` for text or pass content parts for attachments. The API and streaming behavior match the [sending reference](./use-eve-agent#sending). `send()` and `respond()` resolve with a `Delivery` receipt when the server accepts the request, before the agent finishes. Read the receipt's `sessionId` and `deliveryId`, or use its [`stream()` and `result()` reads](../client/messages#reusable-delivery-reads).
63
63
 
64
64
  ## Human-in-the-loop prompts
65
65
 
66
- Read requests from the shared `view` and answer them with `respond()`. Submission does not settle
67
- an interaction; its response rows and eventual settlement are authoritative.
66
+ Read requests from the shared `view` and answer them with `respond()`. A request stays open until `interaction.settled`, even after you submit an answer.
68
67
 
69
68
  ```svelte
70
69
  <script lang="ts">
@@ -95,16 +94,17 @@ See [Human-in-the-loop prompts](./overview#human-in-the-loop-prompts) for reques
95
94
 
96
95
  ## Cancel, end, and resume
97
96
 
98
- Pass `prewarm: true` to prepare an owned workflow on mount and after `newSession()`. It defaults
99
- to `false`, so the first send creates the session. The binding waits for create acceptance,
100
- retries while the inbox starts, and keeps the session stream open across turns. See [Prewarming](./use-eve-agent#prewarming) for creation, failure, and
101
- connection behavior.
97
+ Pass `prewarm: true` to create the session on mount and after `newSession()`. Omit it to create the session on the first send. The binding keeps the session stream open across turns. See [Prewarming](./use-eve-agent#prewarming) for creation and failure behavior, and [Stream lifetime](./use-eve-agent#stream-lifetime) for connection behavior.
102
98
 
103
- Call `agent.cancel()` to stop the durable server-side turn while the binding remains attached through settlement. Offer it while `activeTurn(agent.view)` from `eve/events` returns a turn: `agent.status` reports outstanding work, so it is `"idle"` while a turn waits only on a person. Destroying the component only disconnects its local stream; it does not cancel server execution. Call `agent.newSession()` to clear local state and start a new session. `agent.end()` instead retires the server-side session. Pass `initialSession`, `initialEvents`, and `resume: true` to restore a saved conversation and follow an in-flight turn. During bounded catch-up, `agent.status` is `"resuming"`; keep the hydrated conversation visible, disable submission, and wait for `"idle"` or `"busy"`, and inspect the separate `error` field. Use `agent.resume()` directly when restoration is controlled imperatively. See [Resumable sessions](./use-eve-agent#resume-a-saved-session) for the persistence contract and [Cancelling](./use-eve-agent#cancelling) for cancellation behavior.
99
+ Call `agent.cancel()` to stop the turn on the server; the binding stays attached until the turn ends. Offer it while `activeTurn(agent.view)` from `eve/events` returns a turn, because `agent.status` reports outstanding work and is `"idle"` while a turn waits only on a person. Destroying the component only disconnects its local stream, and the turn keeps running on the server.
100
+
101
+ Call `agent.newSession()` to clear local state and start a new session; `agent.end()` instead ends the session on the server.
102
+
103
+ Pass `initialSession`, `initialEvents`, and `resume: true` to restore a saved conversation and follow a turn that is still running. During catch-up, `agent.status` is `"resuming"`. Keep the restored conversation visible, and disable submission until it changes to `"idle"` or `"busy"`. Failures appear in the separate `error` field. Call `agent.resume()` directly to control restoration imperatively. See [Resume a saved session](./use-eve-agent#resume-a-saved-session) for the persistence contract and [Cancelling](./use-eve-agent#cancelling) for cancellation behavior.
104
104
 
105
105
  ## Custom host and credentials
106
106
 
107
- Pass `baseUrl`, `auth`, or `headers` to the binding using the same options as the other frontend bindings. See [Custom hosts and headers](./overview#custom-hosts-and-headers).
107
+ Pass `baseUrl`, `auth`, or `headers` to the binding, as with the other frontend bindings. See [Custom hosts and headers](./overview#custom-hosts-and-headers).
108
108
 
109
109
  ## Attach page context per turn
110
110
 
@@ -112,11 +112,11 @@ Pass `clientContext` to `send()` or `respond()`, or use `prepareSend` to add con
112
112
 
113
113
  ## Lifecycle callbacks
114
114
 
115
- Pass `onEvent`, `onError`, `onFinish`, or `onSessionChange` when the application needs lifecycle notifications. See [Lifecycle callbacks](./use-eve-agent#lifecycle-callbacks) for callback timing and optimistic projection behavior.
115
+ Pass `onEvent`, `onError`, `onFinish`, or `onSessionChange` to react to events, errors, finished turns, and session changes. See [Lifecycle callbacks](./use-eve-agent#lifecycle-callbacks) for when each one fires and how optimistic messages behave.
116
116
 
117
117
  ## Derive your own state
118
118
 
119
- Use `agent.view` and selectors from `eve/events` for lifecycle state, and `agent.messages` for rendering. See [Derive your own state](./overview#derive-your-own-state).
119
+ Use `agent.view` and selectors from `eve/events` for session state, and `agent.messages` for rendering. See [Derive your own state](./overview#derive-your-own-state).
120
120
 
121
121
  ## What to read next
122
122
 
@@ -3,9 +3,9 @@ title: "useEveAgent (Vue)"
3
3
  description: "Use the eve Vue composable and its Vue-specific reactive interface."
4
4
  ---
5
5
 
6
- `useEveAgent()` from `eve/vue` exposes the shared eve frontend client as Vue computed refs and methods. Read the [frontend overview](./overview) for session behavior, messages, human input, authorization, callbacks, and persistence. This page covers the Vue-specific interface.
6
+ `useEveAgent()` from `eve/vue` exposes the shared eve frontend client as Vue computed refs and methods. See the [frontend overview](./overview) for session behavior, messages, human input, authorization, callbacks, and persistence.
7
7
 
8
- Nuxt users normally receive the composable as an auto-import after registering the [`eve/nuxt` module](./nuxt).
8
+ In Nuxt, the [`eve/nuxt` module](./nuxt) auto-imports the composable.
9
9
 
10
10
  ## Basic usage
11
11
 
@@ -44,26 +44,25 @@ async function handleSubmit() {
44
44
 
45
45
  The state fields are computed refs; the commands are ordinary methods:
46
46
 
47
- | Property | Vue shape |
48
- | ----------------------------------------------------------------------------------------- | ----------------------------------------------- |
49
- | `messages`, `agents` | Computed refs for each projected snapshot field |
50
- | `view` | `ComputedRef<SessionView>` |
51
- | `status` | `ComputedRef<UseEveAgentStatus>` |
52
- | `error` | `ComputedRef<Error \| undefined>` |
53
- | `events` | `ComputedRef<readonly SessionStreamEvent[]>` |
54
- | `session` | `ComputedRef<ClientSessionState \| undefined>` |
55
- | `send`, `respond`, `prewarm`, `resume`, `cancel`, `clear`, `compact`, `end`, `newSession` | Methods |
47
+ | Property | Vue shape |
48
+ | --------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
49
+ | `messages`, `agents` | Computed refs for the snapshot fields |
50
+ | `view` | `ComputedRef<SessionView>` |
51
+ | `status` | `ComputedRef<UseEveAgentStatus>` |
52
+ | `error` | `ComputedRef<Error \| undefined>` |
53
+ | `events` | `ComputedRef<readonly SessionStreamEvent[]>` |
54
+ | `session` | `ComputedRef<ClientSessionState \| undefined>` |
55
+ | `send`, `respond`, `prewarm`, `resume`, `follow`, `cancel`, `clear`, `compact`, `end`, `newSession` | Methods |
56
56
 
57
57
  Destructuring preserves reactivity because each state value remains a ref. Read refs with `.value` in `<script>` and without `.value` in a template. The [`useEveAgent` reference](./use-eve-agent#returned-state) describes what each value and command does.
58
58
 
59
59
  ## Send a message
60
60
 
61
- Call `send(text)` for text or pass content parts for attachments. The API and transport behavior match the [sending reference](./use-eve-agent#sending); only reactive access differs in Vue. `send()` and `respond()` resolve with a `Delivery` receipt when accepted, without waiting for execution to finish. Read its `sessionId` and `deliveryId`, or use the receipt's [delivery reads](../client/messages#reusable-delivery-reads).
61
+ Call `send(text)` for text or pass content parts for attachments. The API and streaming behavior match the [sending reference](./use-eve-agent#sending). `send()` and `respond()` resolve with a `Delivery` receipt when the server accepts the request, before the agent finishes. Read the receipt's `sessionId` and `deliveryId`, or use its [`stream()` and `result()` reads](../client/messages#reusable-delivery-reads).
62
62
 
63
63
  ## Human-in-the-loop prompts
64
64
 
65
- Read requests from the shared `view` and answer them with `respond()`. Submission does not settle
66
- an interaction; its response rows and eventual settlement are authoritative.
65
+ Read requests from the shared `view` and answer them with `respond()`. A request stays open until `interaction.settled`, even after you submit an answer.
67
66
 
68
67
  ```vue
69
68
  <script setup lang="ts">
@@ -104,16 +103,17 @@ See [Human-in-the-loop prompts](./overview#human-in-the-loop-prompts) for reques
104
103
 
105
104
  ## Cancel, end, and resume
106
105
 
107
- Pass `prewarm: true` to prepare an owned workflow on mount and after `newSession()`. It defaults
108
- to `false`, so the first send creates the session. The binding waits for create acceptance,
109
- retries while the inbox starts, and keeps the session stream open across turns. See [Prewarming](./use-eve-agent#prewarming) for creation, failure, and
110
- connection behavior.
106
+ Pass `prewarm: true` to create the session on mount and after `newSession()`. Omit it to create the session on the first send. The composable keeps the session stream open across turns. See [Prewarming](./use-eve-agent#prewarming) for creation and failure behavior, and [Stream lifetime](./use-eve-agent#stream-lifetime) for connection behavior.
111
107
 
112
- Call `cancel()` to stop the durable server-side turn while the composable remains attached through settlement. Offer it while `activeTurn(view.value)` from `eve/events` returns a turn: `status` reports outstanding work, so it is `"idle"` while a turn waits only on a person. Disposing the component only disconnects its local stream; it does not cancel server execution. Call `newSession()` to clear local state and start a new session. `end()` instead retires the server-side session. Pass `initialSession`, `initialEvents`, and `resume: true` to restore a saved conversation and follow an in-flight turn. During bounded catch-up, `status.value` is `"resuming"`; keep the hydrated conversation visible, disable submission, and wait for `"idle"` or `"busy"`, and inspect the separate `error` field. Use `resume()` directly when restoration is controlled imperatively. See [Resumable sessions](./use-eve-agent#resume-a-saved-session) for the persistence contract and [Cancelling](./use-eve-agent#cancelling) for cancellation behavior.
108
+ Call `cancel()` to stop the turn on the server; the composable stays attached until the turn ends. Offer it while `activeTurn(view.value)` from `eve/events` returns a turn, because `status` reports outstanding work and is `"idle"` while a turn waits only on a person. Disposing the component only disconnects its local stream, and the turn keeps running on the server.
109
+
110
+ Call `newSession()` to clear local state and start a new session; `end()` instead ends the session on the server.
111
+
112
+ Pass `initialSession`, `initialEvents`, and `resume: true` to restore a saved conversation and follow a turn that is still running. During catch-up, `status.value` is `"resuming"`. Keep the restored conversation visible, and disable submission until it changes to `"idle"` or `"busy"`. Failures appear in the separate `error` field. Call `resume()` directly to control restoration imperatively. See [Resume a saved session](./use-eve-agent#resume-a-saved-session) for the persistence contract and [Cancelling](./use-eve-agent#cancelling) for cancellation behavior.
113
113
 
114
114
  ## Custom host and credentials
115
115
 
116
- Pass `baseUrl`, `auth`, or `headers` to the composable using the same options as the other frontend bindings. See [Custom hosts and headers](./overview#custom-hosts-and-headers).
116
+ Pass `baseUrl`, `auth`, or `headers` to the composable, as with the other frontend bindings. See [Custom hosts and headers](./overview#custom-hosts-and-headers).
117
117
 
118
118
  ## Attach page context per turn
119
119
 
@@ -121,11 +121,11 @@ Pass `clientContext` to `send()` or `respond()`, or use `prepareSend` to add con
121
121
 
122
122
  ## Lifecycle callbacks
123
123
 
124
- Pass `onEvent`, `onError`, `onFinish`, or `onSessionChange` when the application needs lifecycle notifications. See [Lifecycle callbacks](./use-eve-agent#lifecycle-callbacks) for callback timing and optimistic projection behavior.
124
+ Pass `onEvent`, `onError`, `onFinish`, or `onSessionChange` to react to events, errors, finished turns, and session changes. See [Lifecycle callbacks](./use-eve-agent#lifecycle-callbacks) for when each one fires and how optimistic messages behave.
125
125
 
126
126
  ## Derive your own state
127
127
 
128
- Use `view` and selectors from `eve/events` for lifecycle state, and `messages` for rendering. See [Derive your own state](./overview#derive-your-own-state).
128
+ Use `view` and selectors from `eve/events` for session state, and `messages` for rendering. See [Derive your own state](./overview#derive-your-own-state).
129
129
 
130
130
  ## What to read next
131
131
 
@@ -19,9 +19,9 @@ React, [Vue](./use-eve-agent-vue), and [Svelte](./use-eve-agent-svelte) share th
19
19
  | `events` | The session's raw stream events, deduplicated and in order |
20
20
  | `session` | Serializable session cursor: `sessionId` and `streamIndex` |
21
21
  | `send`, `respond` | Send a message or answers. Resolve with a `Delivery` receipt when accepted |
22
- | `cancel` | Request durable cancellation of the active turn |
22
+ | `cancel` | Ask the server to cancel the active turn |
23
23
  | `prewarm` | Create a session, or prepare an idle one, without starting a turn |
24
- | `resume` | Catch up to the durable tail. Later following obeys `followWhile` |
24
+ | `resume` | Catch up to the end of the stream. Later following obeys `followWhile` |
25
25
  | `follow` | Follow a delivery receipt from this or another store on the same session |
26
26
  | `clear`, `compact` | Queue a context change and return its delivery |
27
27
  | `end` | Retire the server-side session and return its delivery |
@@ -29,7 +29,7 @@ React, [Vue](./use-eve-agent-vue), and [Svelte](./use-eve-agent-svelte) share th
29
29
 
30
30
  About snapshots:
31
31
 
32
- - A snapshot publishes after every event in a committed stream line has been applied.
32
+ - A snapshot publishes after every event in a recorded stream line has been applied.
33
33
  - A view you keep, and its observations, never change after later updates.
34
34
  - Internal tables and preview dictionaries are not public fields.
35
35
 
@@ -94,10 +94,10 @@ A `tool` part shows a call's shared state, with partial input while it streams.
94
94
  | `state` | `streaming` while input arrives, then `requested`, `approval`, `running`, `blocked`, `completed`, `failed`, `rejected`, or `cancelled` |
95
95
  | `inputText` | Partial input, only while `state` is `streaming` |
96
96
  | `input`, `output`, `error` | Validated input, current or final output, and error details |
97
- | `interaction` | The latest approval or question about the call. It stays `open` while an answer is submitted, until settlement |
97
+ | `interaction` | The latest approval or question about the call. It stays `open` after an answer is submitted, until eve decides it |
98
98
 
99
99
  - Read outcomes, reasons, and task identities from `call(view, part.callId)`, not from the part.
100
- - A call stays open if your stream stopped following before it settled. Decide what an open call shows after the stream ends.
100
+ - A call stays open if your stream stopped following before it finished. Decide what an open call shows after the stream ends.
101
101
  - A call that a model retry replaced isn't shown; the replacement asks again.
102
102
  - A delegated call stays `running` until `call.settled`. Its child's detail is on a separate stream; see [Child agents](#child-agents).
103
103
 
@@ -121,7 +121,7 @@ Steering timing depends on what the turn is doing:
121
121
 
122
122
  - Before answer output or local tool execution starts, eve interrupts model generation and continues the same turn with the correction.
123
123
  - Running tools finish and save their results first.
124
- - After answer output starts, steering waits for the next committed workflow boundary.
124
+ - After the reply starts streaming, a steering message waits until the current step is saved.
125
125
  - Reasoning and search progress don't count as answer output.
126
126
 
127
127
  ### Optimistic messages
@@ -140,7 +140,7 @@ With `optimistic: true`, the default, a submitted message shows in `messages` be
140
140
 
141
141
  ## Cancelling
142
142
 
143
- - `cancel()` targets the turn this store is observing and keeps the stream attached through settlement.
143
+ - `cancel()` targets the turn this store is observing and keeps the stream attached until the turn ends.
144
144
  - If no turn is active, it waits for a submission that was pending when you called it, including preparation, session creation, and POST acceptance, then cancels that turn. It never stops an unrelated later turn.
145
145
  - It doesn't withdraw a queued message. If the message never reaches a running turn, `cancel()` does nothing. An idle `cancel()` doesn't arm a future request.
146
146
  - Cancellation is cooperative: a turn can finish before it takes effect.
@@ -152,7 +152,7 @@ By default, the hook keeps one stream open across turns and idle periods, so rep
152
152
 
153
153
  - A turn settling doesn't close the connection.
154
154
  - The stream reconnects from its cursor after a disconnect and when the server's renewable 60-second lease ends. Renewal doesn't start a turn or clear UI state.
155
- - Unmounting or `newSession()` closes the local stream without cancelling the durable session.
155
+ - Unmounting or `newSession()` closes the local stream without cancelling the session on the server.
156
156
 
157
157
  ### Close the stream when idle
158
158
 
@@ -183,7 +183,7 @@ function useSessionPanels(session: ClientSession) {
183
183
 
184
184
  ### Follow a receipt
185
185
 
186
- - `follow(receipt)` tracks an accepted receipt until it settles, even if the stream caught up before the server admitted it.
186
+ - `follow(receipt)` tracks an accepted receipt until it finishes, even if the stream caught up before the server admitted it.
187
187
  - Pass only receipts from `send`, `respond`, `clear`, `compact`, or `end` on the same session. A receipt the stream never admits keeps the store `"busy"` until the session ends or you call `newSession()`.
188
188
  - `follow()` doesn't create a session or grant access.
189
189
  - Limit retries after stream errors, and resolve authorization failures before retrying.
@@ -250,7 +250,7 @@ const agent = useEveAgent({
250
250
 
251
251
  - `initialEvents` must be an ordered prefix of the same session's stream. Its end doesn't have to match where the stream resumes.
252
252
  - Catch-up starts after the source lines your events cover. Coverage uses line positions, not event counts.
253
- - Keep reader metadata unchanged. `meta.next` can record source lines that produced no events, as with [converted v26 history](/docs/concepts/upgrade-to-v27-events).
253
+ - Keep reader metadata unchanged. `meta.next` can record source lines that produced no events.
254
254
  - The `initialSession` cursor alone never extends coverage. A partial line is replayed from its start.
255
255
  - Each event's [`meta.position`](/docs/concepts/sessions-runs-and-streaming#positions) is stable, and the store drops positions it already applied. An overlapping replay renders once, and `onEvent` fires only for new events.
256
256
  - `session.streamIndex` and `position(view)` both track the covered prefix.
@@ -258,8 +258,8 @@ const agent = useEveAgent({
258
258
  ### Catch-up
259
259
 
260
260
  - While catching up, `status` is `"resuming"`. Render saved messages, but disable sending and answering, and don't show cancel or progress controls.
261
- - `resume()` resolves when catch-up reaches the durable tail, even while a turn runs.
262
- - Afterward, `status` is `"busy"` for running or queued work, or `"idle"` for a settled session or a turn waiting only on a person.
261
+ - `resume()` resolves when catch-up reaches the end of the stream, even while a turn runs.
262
+ - Afterward, `status` is `"busy"` for running or queued work, or `"idle"` for a session with nothing running or a turn waiting only on a person.
263
263
  - The connection then stays open to follow the session, unless `followWhile` closes it.
264
264
  - A terminal session failure sets `error`.
265
265
 
@@ -269,29 +269,29 @@ const agent = useEveAgent({
269
269
  | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
270
270
  | `onEvent(event)` | For each stream event as it arrives |
271
271
  | `onError(error)` | When session creation, streaming, resume, or a live turn fails, or a prewarm fails with no send waiting. Restored historical failures don't fire it |
272
- | `onFinish(snapshot)` | When a live turn settles, after its committed line is visible. Catch-up never fires it |
272
+ | `onFinish(snapshot)` | When a live turn ends, after its last events are visible. Catch-up never fires it |
273
273
  | `onSessionChange(session)` | When a session is created, its cursor advances, or `newSession()` clears it |
274
274
 
275
- To read the result of one delivery, use `receipt.result()` instead of `onFinish`. A delivery can settle while its turn still waits for input.
275
+ To read the result of one delivery, use `receipt.result()` instead of `onFinish`. A delivery can finish while its turn still waits for input.
276
276
 
277
277
  ## Interactions
278
278
 
279
- Approvals, questions, sign-ins, and budget prompts are interactions. Read them with `interaction(view, id)`, `interactions(view)`, or `openInteractions(view)` from `eve/events`.
279
+ Approvals, questions, sign-ins, and budget prompts are requests for input, which the API calls interactions. Read them with `interaction(view, id)`, `interactions(view)`, or `openInteractions(view)` from `eve/events`.
280
280
 
281
- - An interaction is `open` until eve settles it. Submitting an answer doesn't settle it; the stream's `interaction.settled` does.
281
+ - A request stays `open` until eve decides it. Submitting an answer doesn't end it; the stream's `interaction.settled` event does.
282
282
  - A tool part's `state` is the call's state, not the decision. A call can be `cancelled` while its approval was never answered.
283
283
 
284
- | `outcome` | Meaning |
285
- | ----------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
286
- | `accepted` | A person approved or answered it |
287
- | `declined` | A person declined |
288
- | `withdrawn`, `interrupted`, `abandoned`, `expired`, `invalid`, `failed` | No decision. The interaction ended another way, such as a cancelled turn or a message sent while a sign-in was pending |
284
+ | `outcome` | Meaning |
285
+ | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
286
+ | `accepted` | A person approved or answered it |
287
+ | `declined` | A person declined |
288
+ | `withdrawn`, `interrupted`, `abandoned`, `expired`, `invalid`, `failed` | No decision. The request ended another way, such as a cancelled turn or a message sent while a sign-in was pending |
289
289
 
290
290
  Show "Approved" or "Denied" only for `accepted` and `declined`. For any other outcome, show the outcome itself. Keep a default branch: later releases can add outcomes.
291
291
 
292
292
  ## Use eve's answers
293
293
 
294
- Read lifecycle state from `view` with functions from `eve/events`, instead of scanning `events` or keeping your own copy:
294
+ Read session state from `view` with functions from `eve/events`, instead of scanning `events` or keeping your own copy:
295
295
 
296
296
  | Question | Ask eve |
297
297
  | ----------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
@@ -325,8 +325,8 @@ const shallow = useEveAgent({ followAgents: ({ depth }) => depth <= 3 });
325
325
  - The predicate is synchronous. An excluded child's descendants aren't discovered. Root depth is zero.
326
326
  - Each `agents[sessionId]` describes one opening, with an `owner` naming its call or task. Its `observation.conversation` has its own `agents`, `messages`, and `view`.
327
327
  - Calls that continue a task reuse its child conversation.
328
- - Read a call's or delivery's settled result for its outcome, not the child's latest message.
329
- - Parent-relayed interactions are the actionable prompts. Don't render a second set of controls from child observations.
328
+ - Read a call's or delivery's final result for its outcome, not the child's latest message.
329
+ - Requests the parent relays are the ones people answer. Don't render a second set of controls from child observations.
330
330
 
331
331
  ### Limits
332
332
 
@@ -381,5 +381,5 @@ if (activity.status === "linked") {
381
381
  ### Without the hook
382
382
 
383
383
  - For headless capture, use [`SessionStore.observe()`](../client/streaming#observe-nested-traces-without-a-framework). Archive observed prefixes with their per-session cursors in your own versioned schema, and keep earlier archives when history expires.
384
- - If you read child streams yourself, attribute work with the parent's `child.sent` facts. Each one names the `callId` and the `childDeliveryId` on the child's stream. Don't count `delivery.consumed` on the child: answers to the child's questions are deliveries too.
384
+ - If you read child streams yourself, attribute work with the parent's `child.sent` events. Each one names the `callId` and the `childDeliveryId` on the child's stream. Don't count `delivery.consumed` on the child: answers to the child's questions are deliveries too.
385
385
  - With your own session, pass a `child.opened` event to [`session.agent()`](../client/streaming#follow-a-subagent) and follow the child with `stream()`. It reads local and remote children through the parent. See [What the parent sees](../../subagents#what-the-parent-sees).