eve 0.89.0 → 0.90.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 +28 -9
- package/dist/src/channel/adapter.d.ts +12 -3
- package/dist/src/channel/adapter.js +1 -1
- package/dist/src/channel/auth/definitions.d.ts +7 -20
- package/dist/src/channel/auth/definitions.js +1 -1
- package/dist/src/channel/auth/jwt-ecdsa.js +1 -1
- package/dist/src/channel/auth/jwt-hmac.js +1 -1
- package/dist/src/channel/auth/oidc.js +1 -1
- package/dist/src/channel/auth/result.d.ts +2 -3
- package/dist/src/channel/auth/result.js +1 -1
- package/dist/src/channel/channel-address.d.ts +1 -1
- package/dist/src/channel/channel-address.js +1 -1
- package/dist/src/channel/schedule.js +1 -1
- package/dist/src/chunks/{use-eve-agent-Bbl4H5aA.js → use-eve-agent-Bwloorf8.js} +77 -63
- package/dist/src/chunks/{use-eve-agent-CNpxgKEH.js → use-eve-agent-XCB0-tLX.js} +77 -63
- package/dist/src/cli/dev/environment.js +1 -1
- package/dist/src/cli/dev/tui/remote-connection-probe.js +1 -1
- package/dist/src/cli/dev/tui/remote-connection-types.d.ts +1 -0
- package/dist/src/cli/dev/tui/runner.js +2 -2
- package/dist/src/cli/dev/tui/status-line.d.ts +2 -2
- package/dist/src/cli/dev/tui/status-line.js +1 -1
- package/dist/src/client/agent-info-schema.d.ts +341 -326
- package/dist/src/client/agent-info-schema.js +1 -1
- package/dist/src/client/agent-info-types.d.ts +13 -10
- package/dist/src/client/client-error.d.ts +1 -1
- package/dist/src/client/client.d.ts +5 -3
- package/dist/src/client/client.js +1 -1
- package/dist/src/compiled/.vendor-stamp.json +1 -1
- package/dist/src/evals/target.js +1 -1
- package/dist/src/eve-channel/auth.d.ts +19 -0
- package/dist/src/eve-channel/auth.js +1 -0
- package/dist/src/eve-channel/index.d.ts +1 -0
- package/dist/src/eve-channel/index.js +1 -1
- package/dist/src/eve-channel/types.d.ts +23 -4
- package/dist/src/execution/catalog/connection-entry.js +1 -1
- package/dist/src/execution/coordination-dispatch-shared.js +1 -1
- package/dist/src/execution/dynamic-workflow/tool.js +1 -1
- package/dist/src/execution/tools/agent-router-workflow.js +1 -1
- package/dist/src/internal/application/stamped-package-version.js +1 -1
- package/dist/src/internal/authored-module-graph.js +1 -1
- package/dist/src/internal/nitro/routes/agent-info/build-agent-info-response.d.ts +2 -2
- package/dist/src/protocol/routes.d.ts +7 -1
- package/dist/src/protocol/routes.js +1 -1
- package/dist/src/public/channels/github/githubChannel.js +1 -1
- package/dist/src/public/channels/github/state.d.ts +7 -0
- package/dist/src/public/channels/github/state.js +1 -1
- package/dist/src/public/channels/mcp.js +1 -1
- package/dist/src/public/channels/telegram/telegramChannel.js +1 -1
- package/dist/src/public/connections/index.d.ts +1 -1
- package/dist/src/public/definitions/channel.js +1 -1
- package/dist/src/public/definitions/connections/tool-call.d.ts +2 -2
- package/dist/src/reactions/frame.js +1 -1
- package/dist/src/runtime/channels/registry.d.ts +2 -2
- package/dist/src/runtime/channels/registry.js +1 -1
- package/dist/src/runtime/connections/approval-scope.d.ts +9 -0
- package/dist/src/runtime/connections/approval-scope.js +1 -0
- package/dist/src/runtime/connections/mcp-client.d.ts +1 -1
- package/dist/src/runtime/connections/mcp-client.js +1 -1
- package/dist/src/runtime/connections/provided-arguments.js +1 -1
- package/dist/src/runtime/subagents/workflow.js +1 -1
- package/dist/src/setup/scaffold/create/project.js +1 -1
- package/dist/src/shared/agent-info-access.d.ts +5 -0
- package/dist/src/shared/agent-info-access.js +1 -0
- package/dist/src/shared/connection-types.d.ts +21 -4
- package/dist/src/svelte/index.js +1 -1
- package/dist/src/svelte/use-eve-agent.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/vue/index.js +1 -1
- package/dist/src/vue/use-eve-agent.js +1 -1
- package/docs/channels/custom.mdx +2 -0
- package/docs/channels/eve.mdx +4 -2
- package/docs/concepts/sessions-runs-and-streaming.md +6 -2
- package/docs/connections/overview.mdx +30 -0
- package/docs/evals/targets.mdx +2 -0
- package/docs/evals/tool-stubs.mdx +4 -4
- package/docs/guides/auth-and-route-protection.md +16 -3
- package/docs/guides/client/overview.mdx +6 -2
- package/docs/guides/prepare-for-1-0.md +23 -1
- package/docs/tools/human-in-the-loop.md +1 -1
- package/package.json +1 -1
|
@@ -34,7 +34,7 @@ The client requires the successful response to match `{ ok: true, status: "ready
|
|
|
34
34
|
|
|
35
35
|
## Inspect an agent
|
|
36
36
|
|
|
37
|
-
Use `info()` to inspect an agent. The client requires
|
|
37
|
+
Use `info()` to inspect an agent. The client requires a complete agent-info version 5 response before returning it:
|
|
38
38
|
|
|
39
39
|
```ts
|
|
40
40
|
const info = await client.info();
|
|
@@ -43,7 +43,11 @@ console.log(info.agent.name, info.agent.model.id);
|
|
|
43
43
|
|
|
44
44
|
Pass `info({ signal })` to cancel the HTTP request. The signal is checked only after custom header and credential callbacks resolve; it does not limit how long those callbacks or the complete `info()` call can take.
|
|
45
45
|
|
|
46
|
-
|
|
46
|
+
The response separates active static definitions from dynamic resolvers, includes binding-backed source ownership and composition history, reports first-class memory slots and their provider-tool wrapper dependencies, reports local and remote agents separately, and returns the exact compiled channel route order. It includes authored instruction content, skill and schedule markdown, and server paths, so the server answers only operator principals (`service`, `runtime`, or `local-dev`) unless the channel's auth grants `allowAgentInfo`. Authenticate the client with an operator credential, such as Vercel OIDC, `jwtHmac()`, `jwtEcdsa()`, or a custom `AuthFn` that returns `principalType: "service"`; any other principal gets a `ClientError` with `status` `403` and `code` `"info_forbidden"`.
|
|
47
|
+
|
|
48
|
+
The version changes only for breaking reshapes; a server adds fields and enum values within a version. The client ignores fields it does not know, and enum-like fields holding a string it cannot interpret (such as `mode`, `sourceKind`, or a channel `method`) read as `"unrecognized"`, so handle that value when you switch on them. A missing or non-string value still throws `AgentInfoResponseError`. `kind` discriminants, such as an owner's, a model endpoint's, or a module's backing `kind`, are closed: a new variant comes with a version bump, and an unknown one throws `AgentInfoResponseError`.
|
|
49
|
+
|
|
50
|
+
A non-success response throws `ClientError`. Invalid JSON, a different agent-info version, duplicate identities, inconsistent totals, or mismatched source provenance throws `AgentInfoResponseError`. For a version mismatch, its `issues` name which side to upgrade: eve in the agent, or the eve package the client runs from.
|
|
47
51
|
|
|
48
52
|
## Authentication
|
|
49
53
|
|
|
@@ -78,6 +78,22 @@ Every connection must use the helper for its protocol. A plain object is no long
|
|
|
78
78
|
|
|
79
79
|
Use `defineOpenAPIConnection` for OpenAPI connections. Keep the helper inside the dynamic factory when authoring a dynamic connection. See [Connections](../connections).
|
|
80
80
|
|
|
81
|
+
## Move tool replacement grants to `eveVercelOidc`
|
|
82
|
+
|
|
83
|
+
`vercelOidc` from `eve/channels/auth` now only authenticates. If a `subjects` entry sets `allowToolStubs`, switch to `eveVercelOidc`, which takes the same options:
|
|
84
|
+
|
|
85
|
+
```diff
|
|
86
|
+
-import { vercelOidc } from "eve/channels/auth";
|
|
87
|
+
+import { eveVercelOidc } from "eve/channels/eve";
|
|
88
|
+
|
|
89
|
+
-vercelOidc({
|
|
90
|
+
+eveVercelOidc({
|
|
91
|
+
subjects: [{ subject: evalRunner, allowToolStubs: true }],
|
|
92
|
+
});
|
|
93
|
+
```
|
|
94
|
+
|
|
95
|
+
If a custom callback returns `allowToolStubs`, type it as `EveAuthFn` (or its result as `EveAuthResult`) from `eve/channels/eve` instead of `AuthFn` / `AuthResult`.
|
|
96
|
+
|
|
81
97
|
## Choose one sandbox layout
|
|
82
98
|
|
|
83
99
|
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.
|
|
@@ -155,6 +171,12 @@ Every error `eve/client` throws now extends `EveError` and carries a stable snak
|
|
|
155
171
|
|
|
156
172
|
`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
173
|
|
|
174
|
+
## Read agent info with an operator credential
|
|
175
|
+
|
|
176
|
+
`GET /eve/v1/info` and `client.info()` now serve only operators: `service` and `runtime` principals, such as Vercel OIDC, `jwtHmac()`, or `jwtEcdsa()` callers, and local development through a configured `localDev()`. Other callers, including web chat end users, get `403` with code `info_forbidden`. If a browser app calls `client.info()`, move that call to your server or hardcode what it shows. To give another credential access, return `principalType: "service"` or `allowAgentInfo: true` from its eve-channel authenticator; `allowAgentInfo: false` denies a caller that would otherwise qualify. See [Agent info access](./auth-and-route-protection#agent-info-access). `eve eval` against a deployment needs such a credential too; `eve remote` connects without one but omits the agent details.
|
|
177
|
+
|
|
178
|
+
The response is still agent-info version 5. The client now ignores unknown fields and reads unknown enum values as `"unrecognized"`; handle that value when you switch on fields such as `mode` or `sourceKind`. `kind` discriminants, such as a model endpoint's or an owner's `kind`, stay closed: a new variant comes with a version bump. See [Inspect an agent](./client/overview#inspect-an-agent).
|
|
179
|
+
|
|
158
180
|
## Update Workflow imports
|
|
159
181
|
|
|
160
182
|
Import durable primitives from `eve/workflow`, and run/hook operations from `eve/workflow/api`:
|
|
@@ -250,6 +272,6 @@ Model-effort `--reasoning` on `eve init` and `eve set model` is unchanged. `--as
|
|
|
250
272
|
|
|
251
273
|
## Check the resulting project
|
|
252
274
|
|
|
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.
|
|
275
|
+
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, and call `client.info()` with an operator credential if your tooling uses it. Test any proactive Slack messages and durable workflow waits your project defines.
|
|
254
276
|
|
|
255
277
|
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.
|
|
@@ -268,7 +268,7 @@ Approval is consent only. An approved tool call runs with the requesting user's
|
|
|
268
268
|
|
|
269
269
|
For auditing, traces record both people: the turn span's `agent.principal.current.*` attributes name the requester, and the approval span's `agent.approval.responder.type` and `agent.approval.responder.id` name who approved or denied the call. An approved call's tool span also records its approver as `agent.tool.approver.type` and `agent.tool.approver.id`, since the tool can act on the approver's behalf. All of these ids follow one rule: they are recorded only when the trace policy records both inputs and outputs and the conversation is public or running in development. Otherwise only the type is recorded.
|
|
270
270
|
|
|
271
|
-
A `defineTool` tool can still act on the approver's behalf when it chooses to. While an approved `defineTool` call runs, `ctx.approval.responder` is the principal who approved it, and `ctx.approval.responder.getToken(provider)` resolves that person's token for an inline provider, as `ctx.getToken(provider)` does for the requester. `ctx.session.auth.current` stays the requester. `ctx.approval` is absent for calls that needed no approval, and workflow tools don't receive it. `ctx.approval.responder.getToken(provider)` never starts a sign-in: when the approver has no token, it throws a `ConnectionAuthorizationFailedError` with `reason: "approver_authorization_required"`.
|
|
271
|
+
A `defineTool` tool can still act on the approver's behalf when it chooses to. While an approved `defineTool` call runs, `ctx.approval.responder` is the principal who approved it, and `ctx.approval.responder.getToken(provider)` resolves that person's token for an inline provider, as `ctx.getToken(provider)` does for the requester. `ctx.session.auth.current` stays the requester. `ctx.approval` is absent for calls that needed no approval, and workflow tools don't receive it. `ctx.approval.responder.getToken(provider)` never starts a sign-in: when the approver has no token, it throws a `ConnectionAuthorizationFailedError` with `reason: "approver_authorization_required"`. A connection's `headers` and `toolCall.providedArguments` callbacks receive the same `ctx.approval.responder` while an approved connection call runs; see [Send the approver to the server](/docs/connections#send-the-approver-to-the-server).
|
|
272
272
|
|
|
273
273
|
```ts
|
|
274
274
|
export default defineTool({
|