eve 0.86.0 → 0.87.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.
- package/CHANGELOG.md +67 -0
- package/README.md +1 -1
- package/dist/src/acp/adapter.d.ts +2 -26
- package/dist/src/acp/adapter.js +1 -1
- package/dist/src/acp/server.d.ts +0 -3
- package/dist/src/ai/decision-adapter.d.ts +5 -3
- package/dist/src/ai/decision-adapter.js +1 -1
- package/dist/src/ai/decision-types.d.ts +4 -3
- package/dist/src/channel/adapter.d.ts +0 -14
- package/dist/src/channel/auth/definitions.d.ts +0 -4
- package/dist/src/channel/channel-address.d.ts +1 -1
- package/dist/src/channel/channel-address.js +1 -1
- package/dist/src/channel/channel-operations.d.ts +2 -2
- package/dist/src/channel/channel-operations.js +1 -1
- package/dist/src/channel/prompt-queue.d.ts +0 -2
- package/dist/src/channel/session-not-active-error.d.ts +10 -5
- package/dist/src/channel/session-not-active-error.js +1 -1
- package/dist/src/channel/session-stranded-error.d.ts +1 -1
- package/dist/src/channel/session.d.ts +3 -4
- package/dist/src/channel/session.js +1 -1
- package/dist/src/channel/types.d.ts +5 -14
- package/dist/src/chunks/{use-eve-agent-B2jCfcnG.js → use-eve-agent-BExXjBv6.js} +82 -72
- package/dist/src/chunks/{use-eve-agent-DCLFi26P.js → use-eve-agent-C0KHCyb9.js} +82 -72
- package/dist/src/cli/dev/command-options.d.ts +4 -4
- package/dist/src/cli/dev/command.js +1 -1
- package/dist/src/cli/dev/tui/runner.js +1 -1
- package/dist/src/cli/dev/tui/test/fake-eve-server.js +1 -1
- package/dist/src/cli/dev/tui/tool-format.d.ts +2 -2
- package/dist/src/cli/dev/ui-options.d.ts +4 -4
- package/dist/src/cli/dev/ui-options.js +1 -1
- package/dist/src/client/agent-info-error.d.ts +4 -1
- package/dist/src/client/agent-info-error.js +1 -1
- package/dist/src/client/agent-session.d.ts +1 -4
- package/dist/src/client/agent-session.js +1 -1
- package/dist/src/client/agent-stream-follower.js +1 -1
- package/dist/src/client/client-error.d.ts +13 -4
- package/dist/src/client/client-error.js +1 -1
- package/dist/src/client/delivery.d.ts +2 -17
- package/dist/src/client/health-response-error.d.ts +4 -1
- package/dist/src/client/health-response-error.js +1 -1
- package/dist/src/client/index.d.ts +5 -3
- package/dist/src/client/index.js +1 -1
- package/dist/src/client/open-stream.d.ts +7 -12
- package/dist/src/client/open-stream.js +1 -1
- package/dist/src/client/session-controls.d.ts +2 -2
- package/dist/src/client/session-controls.js +1 -1
- package/dist/src/client/session-event-stream.d.ts +2 -2
- package/dist/src/client/session-event-stream.js +1 -1
- package/dist/src/client/session-store.d.ts +2 -6
- package/dist/src/client/session-store.js +1 -1
- package/dist/src/client/session.d.ts +4 -13
- package/dist/src/client/session.js +1 -1
- package/dist/src/client/sessions.d.ts +3 -6
- package/dist/src/client/types.d.ts +23 -32
- package/dist/src/compiled/.vendor-stamp.json +3 -3
- package/dist/src/compiled/@vercel/agent-runs/LICENSE +202 -0
- package/dist/src/compiler/manifest.js +1 -1
- package/dist/src/compiler/normalize-agent-config.js +1 -1
- package/dist/src/compiler/normalize-connection.d.ts +1 -1
- package/dist/src/compiler/normalize-connection.js +1 -1
- package/dist/src/compiler/normalize-instructions.js +1 -1
- package/dist/src/compiler/normalize-skill.js +1 -1
- package/dist/src/compiler/resolve-workspace-subagent.js +1 -1
- package/dist/src/context/memory-tools.d.ts +9 -5
- package/dist/src/discover/sandbox.js +1 -1
- package/dist/src/dynamic/definition.d.ts +11 -5
- package/dist/src/dynamic/definition.js +1 -1
- package/dist/src/evals/mock-model.d.ts +1 -1
- package/dist/src/evals/session-manager.d.ts +0 -2
- package/dist/src/evals/session.d.ts +1 -11
- package/dist/src/evals/session.js +1 -1
- package/dist/src/eve-channel/index.js +1 -1
- package/dist/src/eve-channel/support.js +1 -1
- package/dist/src/execution/dynamic-workflow/tool.js +1 -1
- package/dist/src/execution/effective-agent-config.js +1 -1
- package/dist/src/execution/sandbox/bindings/just-bash-runtime.d.ts +1 -2
- package/dist/src/execution/sandbox/bindings/just-bash-runtime.js +1 -1
- package/dist/src/execution/sandbox/bindings/just-bash.js +1 -1
- package/dist/src/execution/tools/agent-router-workflow.js +1 -1
- package/dist/src/instrumentation/ai-sdk-telemetry.d.ts +0 -2
- package/dist/src/instrumentation/providers.d.ts +1 -38
- package/dist/src/instrumentation/providers.js +1 -1
- package/dist/src/instrumentation/setup-context.d.ts +1 -7
- package/dist/src/internal/application/package.d.ts +1 -0
- package/dist/src/internal/application/package.js +1 -1
- package/dist/src/internal/application/stamped-package-version.js +1 -1
- package/dist/src/internal/authored-definition/core.js +1 -1
- package/dist/src/internal/authored-definition/schema-backed.js +1 -1
- package/dist/src/internal/classify-model-routing.d.ts +2 -3
- package/dist/src/internal/nitro/host/create-application-nitro.js +1 -1
- package/dist/src/internal/runtime-model.d.ts +9 -4
- package/dist/src/internal/runtime-model.js +1 -1
- package/dist/src/internal/workflow-bundle/authored-workflow-directives.js +1 -1
- package/dist/src/internal/workflow-bundle/builder-support.d.ts +1 -1
- package/dist/src/internal/workflow-bundle/builder-support.js +1 -1
- package/dist/src/internal/workflow-bundle/workflow-transformer.js +1 -1
- package/dist/src/models/auto.js +1 -1
- package/dist/src/protocol/delivery.d.ts +1 -0
- package/dist/src/protocol/reset-session.d.ts +0 -2
- package/dist/src/protocol/routes.d.ts +9 -2
- package/dist/src/protocol/routes.js +1 -1
- package/dist/src/public/channels/chat-sdk/chatSdkChannel.d.ts +1 -22
- package/dist/src/public/channels/discord/discordChannel.d.ts +3 -12
- package/dist/src/public/channels/discord/gateway/{index.d.ts → relay.d.ts} +2 -2
- package/dist/src/public/channels/discord/gateway/relay.js +1 -0
- package/dist/src/public/channels/discord/messages.d.ts +4 -4
- package/dist/src/public/channels/github/state.d.ts +0 -2
- package/dist/src/public/channels/index.d.ts +1 -2
- package/dist/src/public/channels/index.js +1 -1
- package/dist/src/public/channels/linear/index.d.ts +1 -1
- package/dist/src/public/channels/linear/index.js +1 -1
- package/dist/src/public/channels/linear/linearChannel.d.ts +0 -5
- package/dist/src/public/channels/linq/index.d.ts +1 -1
- package/dist/src/public/channels/linq/linqChannel.d.ts +7 -5
- package/dist/src/public/channels/photon/index.d.ts +1 -1
- package/dist/src/public/channels/photon/photonIMessageChannel.d.ts +15 -4
- package/dist/src/public/channels/slack/api.d.ts +1 -1
- package/dist/src/public/channels/slack/api.js +1 -1
- package/dist/src/public/channels/slack/blocks.d.ts +1 -1
- package/dist/src/public/channels/slack/blocks.js +2 -2
- package/dist/src/public/channels/slack/cards.d.ts +2 -297
- package/dist/src/public/channels/slack/cards.js +1 -1
- package/dist/src/public/channels/slack/index.d.ts +2 -2
- package/dist/src/public/channels/slack/index.js +1 -1
- package/dist/src/public/channels/slack/session-operations.d.ts +2 -2
- package/dist/src/public/channels/slack/session-operations.js +1 -1
- package/dist/src/public/channels/slack/slackChannel.d.ts +11 -72
- package/dist/src/public/channels/slack/slackChannel.js +1 -1
- package/dist/src/public/channels/teams/teamsChannel.d.ts +4 -3
- package/dist/src/public/channels/telegram/hitl.d.ts +2 -9
- package/dist/src/public/channels/telegram/index.d.ts +1 -1
- package/dist/src/public/channels/telegram/telegramChannel.d.ts +0 -2
- package/dist/src/public/channels/twilio/twilioChannel.d.ts +0 -2
- package/dist/src/public/channels/undelivered-reply.d.ts +0 -5
- package/dist/src/public/definitions/agent.d.ts +15 -7
- package/dist/src/public/definitions/agent.js +1 -1
- package/dist/src/public/definitions/channel.d.ts +7 -5
- package/dist/src/public/definitions/channel.js +1 -1
- package/dist/src/public/definitions/connections/protocol.d.ts +1 -7
- package/dist/src/public/definitions/connections/protocol.js +1 -1
- package/dist/src/public/experimental/channels/discord/gateway.d.ts +1 -0
- package/dist/src/public/experimental/channels/discord/gateway.js +1 -0
- package/dist/src/public/experimental/sandbox/just-bash.d.ts +1 -0
- package/dist/src/public/experimental/sandbox/just-bash.js +1 -0
- package/dist/src/public/experimental/workspace/index.d.ts +1 -0
- package/dist/src/public/experimental/workspace/index.js +1 -0
- package/dist/src/public/index.d.ts +2 -2
- package/dist/src/public/index.js +1 -1
- package/dist/src/public/instrumentation/otel.d.ts +1 -1
- package/dist/src/public/instrumentation/provider.d.ts +1 -1
- package/dist/src/public/instrumentation/provider.js +1 -1
- package/dist/src/public/memory/file/backend.d.ts +1 -1
- package/dist/src/public/memory/file/backends/in-memory.js +1 -1
- package/dist/src/public/memory/file/backends/vercel-blob.js +1 -1
- package/dist/src/public/memory/file/provider.js +1 -1
- package/dist/src/public/memory/index.d.ts +3 -11
- package/dist/src/public/models/anthropic/index.d.ts +1 -1
- package/dist/src/public/models/index.d.ts +1 -0
- package/dist/src/public/models/openai/index.d.ts +2 -2
- package/dist/src/public/next/index.d.ts +2 -2
- package/dist/src/public/sandbox/just-bash-sandbox.d.ts +27 -20
- package/dist/src/public/sandbox/just-bash.d.ts +0 -1
- package/dist/src/public/sessions/index.d.ts +1 -0
- package/dist/src/public/sessions/index.js +1 -1
- package/dist/src/public/tools/index.d.ts +1 -1
- package/dist/src/public/tools/index.js +1 -1
- package/dist/src/public/workflow/api.d.ts +25 -0
- package/dist/src/public/workflow/api.js +1 -0
- package/dist/src/public/workflow/index.d.ts +76 -0
- package/dist/src/public/workflow/index.js +1 -0
- package/dist/src/public/workflow-modules.d.ts +2 -17
- package/dist/src/react/use-eve-agent.d.ts +3 -2
- package/dist/src/react/use-eve-agent.js +1 -1
- package/dist/src/reactions/kinds/model.js +1 -1
- package/dist/src/runtime/agent/resolve-model.js +1 -1
- package/dist/src/runtime/resolve-agent.js +1 -1
- package/dist/src/runtime/resolve-dynamic.js +1 -1
- package/dist/src/runtime/subagents/dynamic-agent-config.js +1 -1
- package/dist/src/runtime/subagents/workflow.js +1 -1
- package/dist/src/sandbox/providers/default.js +1 -1
- package/dist/src/self-modification/extension/subagents/agent/agent.d.ts +2 -2
- package/dist/src/self-modification/sandbox.js +1 -1
- package/dist/src/setup/integrations/discord/daemon.js +2 -2
- package/dist/src/setup/scaffold/create/project.js +2 -2
- package/dist/src/setup/scaffold/create/web-template.d.ts +2 -2
- package/dist/src/setup/scaffold/create/web-template.js +2 -2
- package/dist/src/setup/verified-remote-agent.d.ts +1 -3
- package/dist/src/shared/agent-definition.d.ts +18 -9
- package/dist/src/shared/eve-error.d.ts +22 -0
- package/dist/src/shared/eve-error.js +1 -0
- package/dist/src/shared/session.d.ts +2 -2
- package/dist/src/shared/token-usage.d.ts +7 -1
- package/dist/src/svelte/index.js +1 -1
- package/dist/src/svelte/use-eve-agent.d.ts +2 -1
- package/dist/src/svelte/use-eve-agent.js +1 -1
- package/dist/src/tools/definition.d.ts +7 -5
- package/dist/src/tools/definition.js +1 -1
- package/dist/src/tools/provided/ask-question-workflow.js +1 -1
- package/dist/src/tools/provided/sleep-workflow.js +1 -1
- package/dist/src/tracing/eve/batch-span-processor.d.ts +1 -1
- package/dist/src/tracing/eve/content-span-processor.d.ts +1 -19
- package/dist/src/tracing/eve/otel-configuration.d.ts +6 -0
- package/dist/src/tracing/eve/otel-declaration.d.ts +6 -19
- package/dist/src/tracing/eve/span-export-policy.d.ts +0 -2
- package/dist/src/tracing/local/instrumentation-runtime.d.ts +0 -3
- package/dist/src/tracing/local/traces.d.ts +0 -13
- package/dist/src/vue/index.js +1 -1
- package/dist/src/vue/use-eve-agent.d.ts +3 -2
- package/dist/src/vue/use-eve-agent.js +1 -1
- package/docs/agent-config.md +15 -11
- package/docs/channels/custom.mdx +26 -10
- package/docs/channels/discord.mdx +10 -10
- package/docs/channels/eve.mdx +14 -8
- package/docs/channels/linear.mdx +11 -0
- package/docs/channels/linq.mdx +5 -1
- package/docs/channels/photon.mdx +6 -1
- package/docs/channels/slack.mdx +73 -14
- package/docs/channels/telegram.mdx +6 -0
- package/docs/code-extension.mdx +25 -0
- package/docs/concepts/default-harness.md +2 -2
- package/docs/concepts/execution-model-and-durability.mdx +11 -11
- package/docs/concepts/security-model.md +2 -2
- package/docs/concepts/sessions-runs-and-streaming.md +23 -10
- package/docs/concepts/upgrade-to-v27-events.md +2 -1
- package/docs/connections/overview.mdx +4 -0
- package/docs/evals/reporters.mdx +21 -0
- package/docs/extensions.md +12 -0
- package/docs/getting-started.mdx +5 -1
- package/docs/guides/auth-and-route-protection.md +1 -1
- package/docs/guides/client/continuations.mdx +12 -10
- package/docs/guides/client/messages.mdx +24 -1
- package/docs/guides/client/overview.mdx +8 -6
- package/docs/guides/client/streaming.mdx +24 -6
- package/docs/guides/decide.md +3 -3
- package/docs/guides/deployment/vercel.mdx +1 -1
- package/docs/guides/dev-tui.md +2 -2
- package/docs/guides/frontend/overview.mdx +1 -1
- package/docs/guides/frontend/use-eve-agent-svelte.mdx +13 -11
- package/docs/guides/frontend/use-eve-agent-vue.mdx +13 -11
- package/docs/guides/frontend/use-eve-agent.mdx +4 -4
- package/docs/guides/instrumentation/otel.mdx +3 -1
- package/docs/guides/prepare-for-1-0.md +255 -0
- package/docs/guides/remote-agents.md +22 -20
- package/docs/instructions.mdx +1 -1
- package/docs/memory/custom-provider.md +1 -1
- package/docs/memory/file.md +11 -2
- package/docs/meta.json +1 -0
- package/docs/reference/agent-files.md +17 -17
- package/docs/reference/cli.md +14 -9
- package/docs/reference/typescript-api.md +46 -20
- package/docs/sandbox/custom-providers.mdx +2 -0
- package/docs/sandbox/default.mdx +6 -6
- package/docs/sandbox/index.mdx +5 -5
- package/docs/sandbox/just-bash.mdx +30 -21
- package/docs/subagents/index.mdx +4 -4
- package/docs/tools/human-in-the-loop.md +1 -1
- package/docs/tools/workflows.mdx +52 -8
- package/docs/tutorial/first-agent.mdx +1 -1
- package/package.json +36 -9
- package/dist/CHANGELOG.md +0 -38
- package/dist/src/public/channels/discord/gateway/index.js +0 -1
|
@@ -54,13 +54,36 @@ or terminal session throws `SessionNotActiveError` immediately with `retryable:
|
|
|
54
54
|
[stranded](../../concepts/execution-model-and-durability#stranded-sessions) session throws
|
|
55
55
|
`ClientSessionStrandedError`, a `ClientError` with `code: "session_stranded"` and the
|
|
56
56
|
`eveVersion` that built the session when it recorded one. It is never retried automatically. Call
|
|
57
|
-
`session.
|
|
57
|
+
`session.end()` and create a new session.
|
|
58
58
|
The client never creates a replacement session. Following or reconnecting to a stranded session's
|
|
59
59
|
stream reports the same typed error without retrying, including when you were waiting for a
|
|
60
60
|
response to a message accepted before the upgrade. That accepted message is not redelivered.
|
|
61
61
|
`session.clear()` throws the same error, because clearing would keep a session that cannot run.
|
|
62
62
|
`session.stream({ follow: false })` and `session.snapshot()` still read the recorded history.
|
|
63
63
|
|
|
64
|
+
The typed errors `eve/client` throws (`ClientError` and its subclasses, `SessionNotActiveError`,
|
|
65
|
+
`HealthResponseError`, and `AgentInfoResponseError`) extend `EveError` and have a stable snake_case
|
|
66
|
+
`code`: `SessionNotActiveError` uses `session_not_active` or `session_not_ready`; `ClientError` carries
|
|
67
|
+
the response's code (such as `session_stranded` or `session_expired`), or `http_error` when the
|
|
68
|
+
response had none. Narrow with the static `is()` of the class you expect instead of `instanceof`,
|
|
69
|
+
so errors from a separately bundled copy of eve still match:
|
|
70
|
+
|
|
71
|
+
```ts
|
|
72
|
+
import { ClientError, SessionNotActiveError } from "eve/client";
|
|
73
|
+
|
|
74
|
+
try {
|
|
75
|
+
await session.send("Continue.");
|
|
76
|
+
} catch (error) {
|
|
77
|
+
if (SessionNotActiveError.is(error) && !error.retryable) {
|
|
78
|
+
// Start a new session.
|
|
79
|
+
} else if (ClientError.is(error) && error.code === "unauthorized") {
|
|
80
|
+
// Sign in again.
|
|
81
|
+
} else {
|
|
82
|
+
throw error;
|
|
83
|
+
}
|
|
84
|
+
}
|
|
85
|
+
```
|
|
86
|
+
|
|
64
87
|
## Send a full turn payload
|
|
65
88
|
|
|
66
89
|
Pass the full payload to `create()` for the first turn or `send()` for a follow-up:
|
|
@@ -113,11 +113,13 @@ await response.result();
|
|
|
113
113
|
|
|
114
114
|
Per-request headers override client-level values with the same name. For example, a turn can set its application user's `Authorization` header while `vercelOidc` continues to send the deployment-protection credential in `x-vercel-trusted-oidc-idp-token`.
|
|
115
115
|
|
|
116
|
-
##
|
|
116
|
+
## Faster sends with `inbox`
|
|
117
117
|
|
|
118
118
|
Keep the complete `session.state` when saving and restoring a conversation. It can include an
|
|
119
|
-
opaque `inbox`
|
|
120
|
-
|
|
119
|
+
opaque `inbox` value issued by the server. The client sends it back with later messages to avoid
|
|
120
|
+
another hook lookup. Persist it and pass it back unchanged: do
|
|
121
|
+
not inspect, edit, or construct it, because eve may change or extend its contents in any release.
|
|
122
|
+
A missing, stale, or rejected value only costs a slower lookup.
|
|
121
123
|
|
|
122
124
|
Set `EVE_INBOX_HANDLE_SECRET` to the same server-only random secret (at least 32 characters)
|
|
123
125
|
on the deployments that share sessions. Without this key, handles are neither issued nor used.
|
|
@@ -131,7 +133,7 @@ is configured. This change keeps the released SDK dependencies; adopting the SDK
|
|
|
131
133
|
enables the optimization. Handles exclude user metadata, live capabilities, and trace carriers,
|
|
132
134
|
which may contain private server baggage. The signature authenticates a handle; it does not hide its contents.
|
|
133
135
|
|
|
134
|
-
The server checks that the handle addresses the requested inbox. Workflow still validates the
|
|
136
|
+
The server checks that the handle addresses the requested session's inbox. Workflow still validates the
|
|
135
137
|
hook, persists the message, and wakes the workflow. A definite stale-owner rejection resolves
|
|
136
138
|
the current inbox again. An uncertain write is surfaced without submitting a second delivery.
|
|
137
139
|
|
|
@@ -182,10 +184,10 @@ for await (const event of session.stream({ follow: false })) {
|
|
|
182
184
|
console.log(event.type);
|
|
183
185
|
}
|
|
184
186
|
|
|
185
|
-
await session.
|
|
187
|
+
await session.end({ reason: "User requested a fresh session" });
|
|
186
188
|
```
|
|
187
189
|
|
|
188
|
-
`client.sessions` stores the session ID, stream cursor, and optional opaque inbox
|
|
190
|
+
`client.sessions` stores the session ID, stream cursor, and optional opaque `inbox` value. Every method calls an ID-addressed `/eve/v1/session/:sessionId/...` route. Sending through a handle for an unknown or terminal ID fails instead of creating a replacement, and `end()` leaves the handle pinned to the retired ID. Replace calls to the old `reset()` method with `end()`; use `client.sessions.create()` to start a different session. Upgrade the server before using a new client's `end()` method: earlier servers do not serve `/end`.
|
|
189
191
|
|
|
190
192
|
A client can own many independent fixed sessions at once:
|
|
191
193
|
|
|
@@ -37,7 +37,7 @@ const cleared = await session.clear();
|
|
|
37
37
|
await cleared.result();
|
|
38
38
|
```
|
|
39
39
|
|
|
40
|
-
Observe `context.settled` while streaming to check whether summarization succeeded. A failed or empty summary preserves the previous history. `session.
|
|
40
|
+
Observe `context.settled` while streaming to check whether summarization succeeded. A failed or empty summary preserves the previous history. `session.end()` instead retires the session; its delivery settles after retirement and address release.
|
|
41
41
|
|
|
42
42
|
## Aggregate a turn
|
|
43
43
|
|
|
@@ -172,11 +172,11 @@ Browser network failures use the same reconnect policy, both when opening a stre
|
|
|
172
172
|
|
|
173
173
|
If your consumer persists events, key on `event.meta.position`. It is stable across reconnects and rewinds, so an overlapping replay is safe to ingest twice. See [Positions](../../concepts/sessions-runs-and-streaming#positions).
|
|
174
174
|
|
|
175
|
-
Set `
|
|
175
|
+
Set `reconnect: false` when a relay or proxy owns the cursor and reconnection policy. This makes a single stream GET attempt and returns when that connection ends; it does not stop the server-side turn:
|
|
176
176
|
|
|
177
177
|
```ts
|
|
178
178
|
const response = await session.send("Run the long operation.", {
|
|
179
|
-
|
|
179
|
+
reconnect: false,
|
|
180
180
|
});
|
|
181
181
|
|
|
182
182
|
for await (const event of response.stream()) {
|
|
@@ -184,7 +184,24 @@ for await (const event of response.stream()) {
|
|
|
184
184
|
}
|
|
185
185
|
```
|
|
186
186
|
|
|
187
|
-
The same option is available on manual attachments as `session.stream({
|
|
187
|
+
The same option is available on manual attachments as `session.stream({ reconnect: false })`.
|
|
188
|
+
|
|
189
|
+
To tune connection-open retries, pass a `ReconnectOptions` object from `eve/client`:
|
|
190
|
+
|
|
191
|
+
```ts
|
|
192
|
+
const response = await session.send("Run the long operation.", {
|
|
193
|
+
reconnect: {
|
|
194
|
+
maxAttempts: 6,
|
|
195
|
+
baseDelayMs: 250,
|
|
196
|
+
maxDelayMs: 5_000,
|
|
197
|
+
retryableStatuses: [404, 409, 425, 500, 502, 503, 504],
|
|
198
|
+
},
|
|
199
|
+
});
|
|
200
|
+
```
|
|
201
|
+
|
|
202
|
+
`maxAttempts` defaults to `12` for each connection open. It also bounds consecutive transport failures during a bounded read (`follow: false`). Following reads continue reconnecting until stopped. `baseDelayMs` and `maxDelayMs` tune retries when opening a connection; reconnects after an interrupted response body retain their default backoff.
|
|
203
|
+
|
|
204
|
+
`retryableStatuses` replaces the default list (`404`, `409`, `425`, `500`, `502`, `503`, `504`) rather than extending it, so include any defaults you still want retried.
|
|
188
205
|
|
|
189
206
|
## Open a stream manually
|
|
190
207
|
|
|
@@ -253,8 +270,9 @@ continue. `snapshot()` always reads from line `0`; use a bounded stream directly
|
|
|
253
270
|
when you only need the unread suffix from an existing cursor.
|
|
254
271
|
|
|
255
272
|
Unlike `stream()`, `snapshot()` does not advance the originating
|
|
256
|
-
`ClientSession`. Its returned
|
|
257
|
-
line after the captured prefix.
|
|
273
|
+
`ClientSession`. Its returned `session` is the handle's full `ClientSessionState`, including the
|
|
274
|
+
opaque `inbox` value, with `streamIndex` set to the exact line after the captured prefix. Persist
|
|
275
|
+
it as is to restore the conversation later.
|
|
258
276
|
|
|
259
277
|
## Follow a subagent
|
|
260
278
|
|
package/docs/guides/decide.md
CHANGED
|
@@ -173,10 +173,10 @@ To use that choice to delegate while keeping specialist subagents out of the par
|
|
|
173
173
|
Pass `signal: ctx.abortSignal` to cancel the request. Import `DecisionModel`, `DecisionState`,
|
|
174
174
|
`DecisionStatePart`, `DecisionInput`, `DecisionQuestion`, `DecisionAnswer`, `DecisionOptions`,
|
|
175
175
|
and `DecisionResult` from `eve/ai` to annotate reusable configs and handlers.
|
|
176
|
-
Model instances must implement
|
|
176
|
+
Model instances must implement decision model specification `v4`, the version AI SDK 7 supports;
|
|
177
177
|
a matching `provider`, `modelId`, and `specificationVersion` alone is not an implementation.
|
|
178
|
-
|
|
179
|
-
answer validation, retries, and provider errors follow AI SDK semantics.
|
|
178
|
+
If the installed `ai` package does not export a decision API, `decide` throws an error naming the
|
|
179
|
+
missing export. Input and answer validation, retries, and provider errors follow AI SDK semantics.
|
|
180
180
|
|
|
181
181
|
You can also call `decide` outside a tool; it does not require an active eve
|
|
182
182
|
session. Each call performs its own decision. `auto` uses this function
|
|
@@ -83,7 +83,7 @@ Vercel evaluates `vercel.ts` before resolving the service graph. `withEve` adds
|
|
|
83
83
|
|
|
84
84
|
The Web Chat installer can generate this composition for a standalone agent or a selected workspace agent. Configure authentication for every exposed agent. To self-host the same source layout, replace Vercel composition with your own [process and proxy configuration](./self-hosting#run-workspace-members).
|
|
85
85
|
|
|
86
|
-
Run Vercel CLI 59.16.0 or newer with `vercel dev --local` to start the complete service graph locally without linking a Vercel project. A generated Vercel Web Chat project exposes this as `pnpm dev:all`. When the directory is linked, Vercel also loads its development environment and settings. Use `pnpm dev` or `pnpm dev:eve` when you want one agent and the eve terminal UI, or `pnpm dev:web` when you want the frontend without its agent services. Named agents use the same `/eve/<name>/v1/*` routes in development, and default `defineWorkspaceAgent` transports can call peers without deployment credentials.
|
|
86
|
+
Run Vercel CLI 59.16.0 or newer with `vercel dev --local` to start the complete service graph locally without linking a Vercel project. A generated Vercel Web Chat project exposes this as `pnpm dev:all`. When the directory is linked, Vercel also loads its development environment and settings. Use `pnpm dev` or `pnpm dev:eve` when you want one agent and the eve terminal UI, or `pnpm dev:web` when you want the frontend without its agent services. Named agents use the same `/eve/<name>/v1/*` routes in development, and default `defineWorkspaceAgent` transports can call peers without deployment credentials. Import the experimental helper from `eve/experimental/workspace`; see [Vercel workspace peers](../../subagents#vercel-workspace-peers). The workspace layout and `eve/vercel` integration are not experimental.
|
|
87
87
|
|
|
88
88
|
Generated transport routes are inserted before a filesystem handler or, when no filesystem handler exists, before authored routes. `withEve` throws instead of overwriting an authored service key or exact transport route that belongs to a generated agent. Remove the authored route, and remove or rename the authored service; `withEve` adds both automatically. Names in the array form of `services` must also be unique. Other service names, routes, bindings, and Cron Jobs remain authored in `vercel.ts`.
|
|
89
89
|
|
package/docs/guides/dev-tui.md
CHANGED
|
@@ -133,10 +133,10 @@ Use `/traces` to inspect traces recorded during local development. See [Local tr
|
|
|
133
133
|
Use `eve dev` flags to control tool calls, reasoning, subagents, connection authorization, response statistics, context usage, and logs:
|
|
134
134
|
|
|
135
135
|
```bash
|
|
136
|
-
eve dev --tools full --reasoning collapsed --logs all
|
|
136
|
+
eve dev --show-tools full --show-reasoning collapsed --logs all
|
|
137
137
|
```
|
|
138
138
|
|
|
139
|
-
`--subagents` accepts `collapsed` (the default), `full`, or `hidden`. `full` also writes each subagent message and tool call to the transcript as it finishes, and `hidden` leaves subagent tasks out of the transcript and the task panel.
|
|
139
|
+
`--show-subagents` accepts `collapsed` (the default), `full`, or `hidden`. `full` also writes each subagent message and tool call to the transcript as it finishes, and `hidden` leaves subagent tasks out of the transcript and the task panel.
|
|
140
140
|
|
|
141
141
|
Use `--host` and `--port` to bind the local server, or `--no-ui` to run without the terminal UI. Set `EVE_TUI_RENDER_MARKDOWN=0` to show assistant and subagent responses without Markdown parsing or styling; `1` (the default) enables Markdown rendering. See the [`eve dev` CLI reference](../reference/cli#eve-dev) for the complete option list, accepted values, and defaults.
|
|
142
142
|
|
|
@@ -249,7 +249,7 @@ See [Resume a saved session](./use-eve-agent#resume-a-saved-session) for exactly
|
|
|
249
249
|
## Start a new conversation
|
|
250
250
|
|
|
251
251
|
- `newSession()` clears the chat and starts fresh. The old conversation stays on the server.
|
|
252
|
-
- `
|
|
252
|
+
- `end()` ends the conversation on the server. Call `newSession()` afterward to clear it locally.
|
|
253
253
|
|
|
254
254
|
To make the first reply faster, pass `prewarm: true`. eve then creates the next session before the user sends anything. Turn it on only after your auth headers are ready. See [Prewarming](./use-eve-agent#prewarming).
|
|
255
255
|
|
|
@@ -45,15 +45,15 @@ 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
|
|
49
|
-
|
|
|
50
|
-
| `messages`, `agents`
|
|
51
|
-
| `view`
|
|
52
|
-
| `status`
|
|
53
|
-
| `error`
|
|
54
|
-
| `events`
|
|
55
|
-
| `session`
|
|
56
|
-
| `send`, `respond`, `prewarm`, `resume`, `cancel`, `clear`, `compact`, `
|
|
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 |
|
|
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
|
|
|
@@ -91,14 +91,16 @@ an interaction; its response rows and eventual settlement are authoritative.
|
|
|
91
91
|
|
|
92
92
|
See [Human-in-the-loop prompts](./overview#human-in-the-loop-prompts) for request semantics and rendering guidance.
|
|
93
93
|
|
|
94
|
-
|
|
94
|
+
<a id="cancel-reset-and-resume" />
|
|
95
|
+
|
|
96
|
+
## Cancel, end, and resume
|
|
95
97
|
|
|
96
98
|
Pass `prewarm: true` to prepare an owned workflow on mount and after `newSession()`. It defaults
|
|
97
99
|
to `false`, so the first send creates the session. The binding waits for create acceptance,
|
|
98
100
|
retries while the inbox starts, and keeps the session stream open across turns. See [Prewarming](./use-eve-agent#prewarming) for creation, failure, and
|
|
99
101
|
connection behavior.
|
|
100
102
|
|
|
101
|
-
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.
|
|
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.
|
|
102
104
|
|
|
103
105
|
## Custom host and credentials
|
|
104
106
|
|
|
@@ -44,15 +44,15 @@ async function handleSubmit() {
|
|
|
44
44
|
|
|
45
45
|
The state fields are computed refs; the commands are ordinary methods:
|
|
46
46
|
|
|
47
|
-
| Property
|
|
48
|
-
|
|
|
49
|
-
| `messages`, `agents`
|
|
50
|
-
| `view`
|
|
51
|
-
| `status`
|
|
52
|
-
| `error`
|
|
53
|
-
| `events`
|
|
54
|
-
| `session`
|
|
55
|
-
| `send`, `respond`, `prewarm`, `resume`, `cancel`, `clear`, `compact`, `
|
|
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 |
|
|
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
|
|
|
@@ -100,14 +100,16 @@ const pendingRequests = computed(() =>
|
|
|
100
100
|
|
|
101
101
|
See [Human-in-the-loop prompts](./overview#human-in-the-loop-prompts) for request semantics and rendering guidance.
|
|
102
102
|
|
|
103
|
-
|
|
103
|
+
<a id="cancel-reset-and-resume" />
|
|
104
|
+
|
|
105
|
+
## Cancel, end, and resume
|
|
104
106
|
|
|
105
107
|
Pass `prewarm: true` to prepare an owned workflow on mount and after `newSession()`. It defaults
|
|
106
108
|
to `false`, so the first send creates the session. The binding waits for create acceptance,
|
|
107
109
|
retries while the inbox starts, and keeps the session stream open across turns. See [Prewarming](./use-eve-agent#prewarming) for creation, failure, and
|
|
108
110
|
connection behavior.
|
|
109
111
|
|
|
110
|
-
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. `
|
|
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.
|
|
111
113
|
|
|
112
114
|
## Custom host and credentials
|
|
113
115
|
|
|
@@ -24,7 +24,7 @@ React, [Vue](./use-eve-agent-vue), and [Svelte](./use-eve-agent-svelte) share th
|
|
|
24
24
|
| `resume` | Catch up to the durable tail. 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 |
|
|
28
28
|
| `newSession` | Clear local state and the local session cursor |
|
|
29
29
|
|
|
30
30
|
About snapshots:
|
|
@@ -184,7 +184,7 @@ function useSessionPanels(session: ClientSession) {
|
|
|
184
184
|
### Follow a receipt
|
|
185
185
|
|
|
186
186
|
- `follow(receipt)` tracks an accepted receipt until it settles, even if the stream caught up before the server admitted it.
|
|
187
|
-
- Pass only receipts from `send`, `respond`, `clear`, `compact`, or `
|
|
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.
|
|
190
190
|
|
|
@@ -230,9 +230,9 @@ For an existing idle session, `prewarm()` can move it to the deployment that acc
|
|
|
230
230
|
| Command | Effect |
|
|
231
231
|
| -------------- | ---------------------------------------------------------------------------------------------- |
|
|
232
232
|
| `newSession()` | Clears the local conversation and reuses the hook. The old session keeps running on the server |
|
|
233
|
-
| `
|
|
233
|
+
| `end()` | Retires the server-side session and returns its delivery |
|
|
234
234
|
|
|
235
|
-
After `
|
|
235
|
+
After `end()`, call `newSession()` to clear the retired conversation. With `prewarm` on, that prepares the next session; otherwise the next send creates it. A `session` you passed in stays yours: prewarming and `newSession()` never replace it.
|
|
236
236
|
|
|
237
237
|
## Resume a saved session
|
|
238
238
|
|
|
@@ -128,7 +128,9 @@ export default otelIntegration({
|
|
|
128
128
|
```
|
|
129
129
|
|
|
130
130
|
Pass `spanProcessors` to `otelIntegration()` when a custom destination needs
|
|
131
|
-
filtering or transformation.
|
|
131
|
+
filtering or transformation. Processors and exporters from any `@opentelemetry/*` build
|
|
132
|
+
satisfy the `SpanProcessor` and `SpanExporter` types from `eve/instrumentation/otel`;
|
|
133
|
+
`SpanProcessorOrName` also accepts `"auto"`. The example's `exportPolicy` preserves span
|
|
132
134
|
metadata while removing inputs and outputs from this destination.
|
|
133
135
|
|
|
134
136
|
## Add runtime context
|
|
@@ -0,0 +1,255 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: "Prepare for 1.0"
|
|
3
|
+
description: "Update session controls, authoring definitions, imports, public types, client errors, retry options, and terminal flags for the pre-1.0 API cleanup."
|
|
4
|
+
url: /guides/prepare-for-1-0
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
Use this checklist when upgrading an existing project to the coordinated pre-1.0 API cleanup release. These changes do not make the release 1.0; the [stability policy](../reference/typescript-api#stability-policy) still distinguishes stable and experimental APIs.
|
|
8
|
+
|
|
9
|
+
Upgrade eve in your agent server and apply the authored-file changes below so it builds. Deploy it before upgrading clients: new clients call the `/end` endpoint, which older servers do not serve. Then update frontend code and scripts.
|
|
10
|
+
|
|
11
|
+
## End a session or start a new conversation
|
|
12
|
+
|
|
13
|
+
Replace retirement methods named `reset()` with `end()` on client sessions, `SessionStore`, React/Vue/Svelte bindings, channel session handles, `ChannelSource` from `eve/channels`, and the Slack handler context (`ctx.end()`):
|
|
14
|
+
|
|
15
|
+
```diff
|
|
16
|
+
-await session.reset({ reason: "Conversation finished" });
|
|
17
|
+
+await session.end({ reason: "Conversation finished" });
|
|
18
|
+
```
|
|
19
|
+
|
|
20
|
+
`end()` resolves with a delivery receipt, like the other session controls. The stream still records the control as `source: { control: "reset" }` on `delivery.admitted` for compatibility with recorded history, so code that matches that value does not change.
|
|
21
|
+
|
|
22
|
+
The HTTP endpoint changes from `POST /eve/v1/session/:sessionId/reset` to `POST /eve/v1/session/:sessionId/end`. Upgraded servers still serve `POST …/reset` beside `/end`, so existing HTTP callers keep working, but move them to `/end`.
|
|
23
|
+
|
|
24
|
+
Ending permanently retires the session and leaves the handle on the retired ID. Do not use `end()` for a **New chat** button. Use `newSession()` when the frontend binding or store owns session creation. When you supply an external `session`, `newSession()` only clears local state and keeps that handle; create a new client session and bind a new store or component to it instead:
|
|
25
|
+
|
|
26
|
+
```ts
|
|
27
|
+
import { Client } from "eve/client";
|
|
28
|
+
|
|
29
|
+
const client = new Client({ baseUrl: "https://agent.example" });
|
|
30
|
+
const { session } = await client.sessions.create();
|
|
31
|
+
await session.send("Start a new conversation.");
|
|
32
|
+
```
|
|
33
|
+
|
|
34
|
+
Use `clear()` to clear model context in the same active session instead. See [Session controls](./client/overview#sessions) for the differences.
|
|
35
|
+
|
|
36
|
+
The remote-agent cleanup path and persisted session-history encodings remain compatible with older deployments. This does not let a new client call `/end` on an old server; upgrade the server first.
|
|
37
|
+
|
|
38
|
+
## Rename the compaction threshold
|
|
39
|
+
|
|
40
|
+
`compaction.threshold` is a fraction from `0` through `1`, not a percentage. Rename the authored field without changing its value:
|
|
41
|
+
|
|
42
|
+
```diff
|
|
43
|
+
export default defineAgent({
|
|
44
|
+
- compaction: { thresholdPercent: 0.7 },
|
|
45
|
+
+ compaction: { threshold: 0.7 },
|
|
46
|
+
});
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
The old field fails validation with migration guidance. The default remains `0.9`. See [Compaction](../agent-config#compaction).
|
|
50
|
+
|
|
51
|
+
`limits.sessionUsage: false` is now accepted when you want to disable the token-usage limit, including an inherited limit. Omitting it keeps the normal default; no migration is required.
|
|
52
|
+
|
|
53
|
+
## Export defineAgent from agent.ts
|
|
54
|
+
|
|
55
|
+
Every local `agent.ts`, root or subagent, must export the value `defineAgent` returns. A plain object now fails the build with `Export defineAgent({...}) from "<path>".`:
|
|
56
|
+
|
|
57
|
+
```diff
|
|
58
|
+
-export default { model: "anthropic/claude-sonnet-5" };
|
|
59
|
+
+import { defineAgent } from "eve";
|
|
60
|
+
+
|
|
61
|
+
+export default defineAgent({ model: "anthropic/claude-sonnet-5" });
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
A dynamic subagent resolver that selects a local agent must also return `defineAgent({...})`, `defineRemoteAgent(...)`, or `null`.
|
|
65
|
+
|
|
66
|
+
`DynamicSentinel`, `DisabledToolSentinel`, and `DisabledRouteSentinel` are opaque and no longer expose `kind` or `evaluate`. Create them only with `defineDynamic()`, `disableTool()`, and `disableRoute()`; hand-written objects of the same shape are rejected.
|
|
67
|
+
|
|
68
|
+
## Wrap connection definitions
|
|
69
|
+
|
|
70
|
+
Every connection must use the helper for its protocol. A plain object is no longer assumed to be an MCP connection:
|
|
71
|
+
|
|
72
|
+
```diff
|
|
73
|
+
-export default { url: "https://issues.example/mcp" };
|
|
74
|
+
+import { defineMcpClientConnection } from "eve/connections";
|
|
75
|
+
+
|
|
76
|
+
+export default defineMcpClientConnection({ url: "https://issues.example/mcp" });
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
Use `defineOpenAPIConnection` for OpenAPI connections. Keep the helper inside the dynamic factory when authoring a dynamic connection. See [Connections](../connections).
|
|
80
|
+
|
|
81
|
+
## Choose one sandbox layout
|
|
82
|
+
|
|
83
|
+
If both `agent/sandbox.ts` and `agent/sandbox/` exist, move the definition to `agent/sandbox/sandbox.ts`. The combination now fails discovery instead of silently ignoring the root definition.
|
|
84
|
+
|
|
85
|
+
A standalone `agent/sandbox.ts` remains supported. See [Sandbox layout](../sandbox#define-an-environment).
|
|
86
|
+
|
|
87
|
+
## Move experimental imports
|
|
88
|
+
|
|
89
|
+
Import workspace helpers from the experimental entry:
|
|
90
|
+
|
|
91
|
+
```diff
|
|
92
|
+
-import { defineWorkspaceAgent } from "eve";
|
|
93
|
+
+import { defineWorkspaceAgent } from "eve/experimental/workspace";
|
|
94
|
+
```
|
|
95
|
+
|
|
96
|
+
Move `WorkspaceAgentDefinition` and `WorkspaceAgentTransport` type imports to the same entry. The `agents/<name>/` workspace layout and `withEve` from `eve/vercel` stay stable; the helper's experimental status does not change them.
|
|
97
|
+
|
|
98
|
+
Move just-bash `customCommands` and `filesystem` under `experimental`, and import their types, such as `JustBashCommand` and `JustBashFilesystem`, from `eve/experimental/sandbox/just-bash`. `JustBashSandbox` itself, `autoInstall`, and `prepare` stay on `eve/sandbox/just-bash`:
|
|
99
|
+
|
|
100
|
+
```diff
|
|
101
|
+
export const environment = JustBashSandbox.environment({
|
|
102
|
+
- customCommands: [today],
|
|
103
|
+
+ experimental: { customCommands: [today] },
|
|
104
|
+
});
|
|
105
|
+
```
|
|
106
|
+
|
|
107
|
+
The Discord Gateway relay moves and drops its prefix:
|
|
108
|
+
|
|
109
|
+
```diff
|
|
110
|
+
-import { experimental_runDiscordGatewayRelay } from "eve/channels/discord/gateway";
|
|
111
|
+
+import { runDiscordGatewayRelay } from "eve/experimental/channels/discord/gateway";
|
|
112
|
+
```
|
|
113
|
+
|
|
114
|
+
See [just-bash](../sandbox/just-bash) and [Discord](../channels/discord).
|
|
115
|
+
|
|
116
|
+
## Flatten reconnect options
|
|
117
|
+
|
|
118
|
+
Replace `streamReconnectPolicy` with `reconnect`, move open-retry fields directly into that object, and rename `retryableErrorStatuses`:
|
|
119
|
+
|
|
120
|
+
```diff
|
|
121
|
+
const delivery = await session.send("Continue the review.", {
|
|
122
|
+
- streamReconnectPolicy: {
|
|
123
|
+
- streamOpenReconnectPolicy: { maxAttempts: 3, baseDelayMs: 250, maxDelayMs: 5000 },
|
|
124
|
+
- retryableErrorStatuses: [429, 503],
|
|
125
|
+
+ reconnect: {
|
|
126
|
+
+ maxAttempts: 3,
|
|
127
|
+
+ baseDelayMs: 250,
|
|
128
|
+
+ maxDelayMs: 5000,
|
|
129
|
+
+ retryableStatuses: [429, 503],
|
|
130
|
+
},
|
|
131
|
+
});
|
|
132
|
+
```
|
|
133
|
+
|
|
134
|
+
To disable automatic reconnects:
|
|
135
|
+
|
|
136
|
+
```diff
|
|
137
|
+
-streamReconnectPolicy: { reconnect: false }
|
|
138
|
+
+reconnect: false
|
|
139
|
+
```
|
|
140
|
+
|
|
141
|
+
Use the exported `ReconnectOptions` type from `eve/client` instead of `StreamReconnectPolicy` or `StreamReconnectRetryPolicy`. The option also applies to client session and event readers. Defaults and cursor recovery are unchanged; following reads keep reconnecting, and server-side readers do not reconnect. See [Streaming](./client/streaming#reconnection).
|
|
142
|
+
|
|
143
|
+
## Update client error handling and saved state
|
|
144
|
+
|
|
145
|
+
Every error `eve/client` throws now extends `EveError` and carries a stable snake_case `code`. Import the error classes from `eve/client` and narrow with their static `is()` rather than `instanceof`, so errors from a separately bundled copy of eve still match:
|
|
146
|
+
|
|
147
|
+
```diff
|
|
148
|
+
-if (error instanceof SessionNotActiveError && error.code === "EVE_SESSION_NOT_ACTIVE") {
|
|
149
|
+
+if (SessionNotActiveError.is(error) && error.code === "session_not_active") {
|
|
150
|
+
// Start a new session.
|
|
151
|
+
}
|
|
152
|
+
```
|
|
153
|
+
|
|
154
|
+
`SessionNotActiveError.code` is `session_not_ready` (with `retryable: true`) while a session is still starting, otherwise `session_not_active`; `EVE_SESSION_NOT_ACTIVE` is gone. `ClientError.code` is now `http_error` instead of `undefined` when the response carried no code.
|
|
155
|
+
|
|
156
|
+
`session.snapshot()` now returns the full `ClientSessionState`, including the opaque `inbox` value, instead of only `sessionId` and `streamIndex`. Persist it as is and pass it back unchanged, for example with `client.sessions.attach(saved.sessionId, saved)`. See [Faster sends with `inbox`](./client/overview#faster-sends-with-inbox).
|
|
157
|
+
|
|
158
|
+
## Update Workflow imports
|
|
159
|
+
|
|
160
|
+
Import durable primitives from `eve/workflow`, and run/hook operations from `eve/workflow/api`:
|
|
161
|
+
|
|
162
|
+
```diff
|
|
163
|
+
-import { createHook, createWebhook, sleep, FatalError, RetryableError, getWorkflowMetadata } from "workflow";
|
|
164
|
+
-import { start, getRun, resumeHook } from "workflow/api";
|
|
165
|
+
+import { createHook, createWebhook, sleep, FatalError, RetryableError, getWorkflowMetadata } from "eve/workflow";
|
|
166
|
+
+import { start, getRun, resumeHook } from "eve/workflow/api";
|
|
167
|
+
```
|
|
168
|
+
|
|
169
|
+
Bare `workflow` and `workflow/*` imports in authored modules now fail the build. Only the exports listed above are public; other SDK subpaths, helpers, and options are not supported by these entries. The previously removed `agent` and `ask` helpers stay removed: importing them from `eve/workflow` fails with a pointer to `defineWorkflowTool()` from `eve/tools`.
|
|
170
|
+
|
|
171
|
+
Both entries declare eve-owned types instead of the SDK's:
|
|
172
|
+
|
|
173
|
+
- `getHookByToken` is removed. Pass a deterministic `token` to `createHook({ token })`, and resume the hook with `resumeHook(token, payload)`. `resumeHook` accepts only a token, not a hook record or an encryption-key override, and resolves to `void`.
|
|
174
|
+
- `start(workflow, args?)` takes a `"use workflow"` function, not a source string, and no options such as `deploymentId` or `world`; eve routes runs to the agent's own queue and deployment.
|
|
175
|
+
- `start` and `getRun` return a `WorkflowRun` with only `runId`, `status`, `returnValue`, and `cancel()`.
|
|
176
|
+
|
|
177
|
+
```diff
|
|
178
|
+
-const hook = await getHookByToken(token);
|
|
179
|
+
-await resumeHook(hook, payload);
|
|
180
|
+
+await resumeHook(token, payload);
|
|
181
|
+
```
|
|
182
|
+
|
|
183
|
+
Use `WorkflowHook`, `WorkflowWebhook`, and `WorkflowMetadata` from `eve/workflow`, and `WorkflowRun` and `WorkflowRunStatus` from `eve/workflow/api`, for explicit annotations. Call `eve/workflow/api` operations from routes or `"use step"` helpers, not replayed workflow bodies. Both entries use eve's bundled SDK; do not install another SDK to make these imports resolve.
|
|
184
|
+
|
|
185
|
+
You can remove `eve/workflow-modules` from tsconfig `types` and reference directives. Existing references remain resolvable through 1.x, but the entry no longer declares bare modules. See [Workflow imports](../tools/workflows#workflow-imports).
|
|
186
|
+
|
|
187
|
+
## Replace third-party types in eve signatures
|
|
188
|
+
|
|
189
|
+
eve's authoring and configuration types no longer expose AI SDK, zod, OpenTelemetry, or channel-adapter types; only the model helpers still return AI SDK models. Any AI SDK language model or OpenTelemetry processor still type-checks wherever eve accepts one, so most projects only change annotations:
|
|
190
|
+
|
|
191
|
+
- Agent `model` fields accept `EveLanguageModel` (exported from `eve` and `eve/models`); any AI SDK language model satisfies it. `anthropic()`, `openai()`, `chatgpt()`, and `mockModel()` still return AI SDK language models, so nothing changes where you pass them to AI SDK functions.
|
|
192
|
+
- `DecisionModel` instances must declare `specificationVersion: "v4"`.
|
|
193
|
+
- `TokenUsage`, the usage record `limits.sessionUsage` callbacks receive, is now exported from `eve` for annotations.
|
|
194
|
+
- `MemoryToolDefinition` is removed. Type memory provider tools as `MemoryToolSet`, a map of `defineTool()` values (`ToolDefinition` from `eve/tools`).
|
|
195
|
+
- Import `SpanProcessor`, `SpanExporter`, and `SpanProcessorOrName` from `eve/instrumentation/otel`, `LinqWebhookVerifier` from `eve/channels/linq`, and `PhotonIMessageWebhookVerifier` and `PhotonProjectCredentials` from `eve/channels/photon`.
|
|
196
|
+
|
|
197
|
+
## Keep custom data out of channel state bookkeeping
|
|
198
|
+
|
|
199
|
+
Built-in channel state types no longer include the default handlers' bookkeeping, such as Slack `taskCards` and `threadStatus`, Chat SDK streaming fields, `pendingSignIns`, posted prompt cards, `shownPromptId`, `undeliveredReplyErrorId`, and Discord's `interactionToken`, `initialResponseSent`, and `hasMessageAnchor` (read the interaction token from the Discord handle). `TelegramHitlState` is no longer exported. Addressing, identity, and audience fields are unchanged. Keep custom handler data in your own state keys instead of reading or writing these fields.
|
|
200
|
+
|
|
201
|
+
## Remove unsupported Slack card imports
|
|
202
|
+
|
|
203
|
+
Remove these exports from `eve/channels/slack` imports:
|
|
204
|
+
|
|
205
|
+
- `Modal*`, `TextInput*`, and `ExternalSelect*` builders and their associated types.
|
|
206
|
+
- `CardJSXElement` and `CardJSXProps`.
|
|
207
|
+
- `isCardElement` and `cardChildToFallbackText`.
|
|
208
|
+
- `ChatElement`, `ContainerProps`, and the builder props types: `ButtonProps`, `CardLinkProps`, `CardProps`, `DividerProps`, `FieldProps`, `ImageProps`, `LinkButtonProps`, `SelectOptionProps`, `SelectProps`, and `TextProps`.
|
|
209
|
+
|
|
210
|
+
Card builders no longer accept JSX-style props with `children`. Call their data forms instead:
|
|
211
|
+
|
|
212
|
+
```diff
|
|
213
|
+
-Actions({ children: [Button({ id: "approve", children: "Approve" })] });
|
|
214
|
+
+Actions([Button({ id: "approve", label: "Approve" })]);
|
|
215
|
+
```
|
|
216
|
+
|
|
217
|
+
Use `CardText` for labels and `cardToFallbackText` for whole cards. Use native Slack view data for custom modals; the removed builders did not have a supported eve delivery path. Built-in human-in-the-loop modals are unchanged.
|
|
218
|
+
|
|
219
|
+
Supported message cards remain available. An existing `initialMessage: { card }` continues to work; proactive messages can now also use `{ text }`, `{ markdown }`, or `{ blocks, text? }`. Optional files upload into the root message's thread. Retrying a proactive send can repeat both the root post and its uploads. See [Slack cards](../channels/slack#cards) and [proactive sends](../channels/slack#proactive-sessions).
|
|
220
|
+
|
|
221
|
+
## Replace undocumented helper imports
|
|
222
|
+
|
|
223
|
+
| Entry | Removed export | Migration |
|
|
224
|
+
| --------------------- | --------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
|
|
225
|
+
| `eve/tools` | `isDisabledToolSentinel` | Export `disableTool()` from a tool file; let the compiler handle the sentinel. |
|
|
226
|
+
| `eve/channels` | `isDisabledRouteSentinel` | Export `disableRoute()` from a route file instead of inspecting the sentinel. |
|
|
227
|
+
| `eve/instrumentation` | `isInstrumentationDisabled` | Export `disableInstrumentation()` instead of inspecting the sentinel. |
|
|
228
|
+
| `eve/client` | `failureOf` | Use `failure(view, turnId)` from `eve/events`. |
|
|
229
|
+
| `eve/channels` | `answerFromText` | Parse your channel's input and answer through its authorized session handle; see [Custom channels](../channels/custom). |
|
|
230
|
+
| `eve/channels/linear` | `defaultOnAgentSession` | Omit the override to use the built-in callback, or provide your own `onAgentSession`. |
|
|
231
|
+
|
|
232
|
+
## Rename terminal display flags
|
|
233
|
+
|
|
234
|
+
Update scripts that call `eve dev` or `eve remote connect`:
|
|
235
|
+
|
|
236
|
+
| Old flag | New flag |
|
|
237
|
+
| ------------------- | ------------------------ |
|
|
238
|
+
| `--tools` | `--show-tools` |
|
|
239
|
+
| `--reasoning` | `--show-reasoning` |
|
|
240
|
+
| `--subagents` | `--show-subagents` |
|
|
241
|
+
| `--connection-auth` | `--show-connection-auth` |
|
|
242
|
+
|
|
243
|
+
Values are unchanged, and the old display names are not aliases. For example:
|
|
244
|
+
|
|
245
|
+
```bash
|
|
246
|
+
eve dev --show-reasoning full --show-tools auto-collapsed
|
|
247
|
+
```
|
|
248
|
+
|
|
249
|
+
Model-effort `--reasoning` on `eve init` and `eve set model` is unchanged. `--assistant-response-stats`, `--context-size`, and `--logs` are unchanged too. See the [CLI reference](../reference/cli).
|
|
250
|
+
|
|
251
|
+
## Check the resulting project
|
|
252
|
+
|
|
253
|
+
Run your project's typecheck and `eve build`, then check the workflows you use: create a conversation, send a message, end it, and start another. Restore a saved session state and send to it. Test any proactive Slack messages and durable workflow waits your project defines.
|
|
254
|
+
|
|
255
|
+
Review [run-data retention](../agent-config#run-data-retention) before depending on a completed transcript remaining readable. This cleanup does not change the retention default: outside development, the default trace policy for private and unknown-audience sessions requests deletion when the session ends. Backend support determines whether deletion occurs; the current override remains experimental.
|