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.
- package/CHANGELOG.md +34 -23
- package/dist/src/channel/auth/http-basic.js +1 -1
- package/dist/src/channel/channel-operations.d.ts +1 -1
- package/dist/src/channel/types.d.ts +2 -0
- package/dist/src/cli/dev/tui/prompt-commands.d.ts +1 -1
- package/dist/src/client/session.d.ts +1 -1
- package/dist/src/compiled/.vendor-stamp.json +1 -1
- package/dist/src/execution/dynamic-workflow/tool.js +1 -1
- package/dist/src/execution/proxied-deliver-step.js +1 -1
- package/dist/src/execution/sandbox/bash.js +2 -2
- package/dist/src/execution/session/active-turn.js +1 -1
- package/dist/src/execution/session/admission.d.ts +6 -0
- package/dist/src/execution/session/admission.js +1 -1
- package/dist/src/execution/session/delivery-facts.js +1 -1
- package/dist/src/execution/session/next-input.d.ts +2 -2
- package/dist/src/execution/session/next-input.js +1 -1
- package/dist/src/execution/session/program.js +1 -1
- package/dist/src/execution/session-inbox/inbox.d.ts +2 -2
- package/dist/src/execution/session-inbox/inbox.js +1 -1
- package/dist/src/execution/session-inbox/protocol.js +1 -1
- package/dist/src/execution/tools/agent-router-workflow.js +1 -1
- package/dist/src/harness/compaction/engine.js +2 -2
- package/dist/src/harness/current-messages.js +1 -1
- package/dist/src/harness/emission.d.ts +3 -0
- package/dist/src/harness/emission.js +1 -1
- package/dist/src/harness/facts.d.ts +5 -2
- package/dist/src/harness/facts.js +1 -1
- package/dist/src/harness/model-call/call.d.ts +7 -1
- package/dist/src/harness/model-call/call.js +3 -1
- package/dist/src/harness/provider-tool-history.d.ts +8 -0
- package/dist/src/harness/provider-tool-history.js +1 -1
- package/dist/src/harness/session-machine/transitions.d.ts +3 -2
- package/dist/src/harness/step/after-model.js +1 -1
- package/dist/src/harness/step/context.js +1 -1
- package/dist/src/harness/step/intake.js +1 -1
- package/dist/src/harness/step/prompt.js +1 -1
- package/dist/src/harness/tool-history-repair.d.ts +2 -0
- package/dist/src/harness/tool-history-repair.js +1 -1
- package/dist/src/harness/tool-loop.js +1 -1
- package/dist/src/internal/application/stamped-package-version.js +1 -1
- package/dist/src/protocol/session-events/families/delivery.d.ts +5 -3
- package/dist/src/protocol/session-events/families/delivery.js +1 -1
- package/dist/src/protocol/session-projection/fold.js +1 -1
- package/dist/src/public/channels/discord/hitl.js +1 -1
- package/dist/src/public/channels/slack/hitl.d.ts +2 -1
- package/dist/src/public/channels/slack/hitl.js +3 -3
- package/dist/src/public/channels/slack/interaction-cards.js +1 -1
- package/dist/src/public/channels/slack/request-card-render.js +1 -1
- package/dist/src/public/channels/teams/hitl.js +1 -1
- package/dist/src/public/channels/teams/verify.js +1 -1
- package/dist/src/public/definitions/hook.d.ts +90 -7
- package/dist/src/public/definitions/hook.js +1 -1
- package/dist/src/public/hooks/index.d.ts +3 -2
- package/dist/src/reactions/continuation.d.ts +19 -0
- package/dist/src/reactions/continuation.js +1 -0
- package/dist/src/reactions/intents.d.ts +10 -4
- package/dist/src/reactions/intents.js +1 -1
- package/dist/src/reactions/kinds/hook.js +1 -1
- package/dist/src/reactions/runner.js +1 -1
- package/dist/src/reactions/state.d.ts +15 -2
- package/dist/src/reactions/state.js +1 -1
- package/dist/src/runtime/resolve-connection.js +1 -1
- package/dist/src/runtime/subagents/workflow.js +1 -1
- package/dist/src/setup/primitives/open-url.js +1 -1
- package/dist/src/setup/scaffold/create/project.js +1 -1
- package/dist/src/shared/value-delta.d.ts +5 -4
- package/dist/src/shared/value-delta.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/tools/provided/web-fetch.js +1 -1
- package/docs/agent-config.md +199 -222
- package/docs/channels/chat-sdk.mdx +60 -64
- package/docs/channels/custom.mdx +264 -281
- package/docs/channels/discord.mdx +176 -123
- package/docs/channels/eve.mdx +136 -206
- package/docs/channels/github.mdx +24 -22
- package/docs/channels/linear.mdx +30 -30
- package/docs/channels/linq.mdx +25 -13
- package/docs/channels/mcp.mdx +154 -116
- package/docs/channels/overview.mdx +31 -32
- package/docs/channels/photon.mdx +32 -56
- package/docs/channels/slack.mdx +538 -375
- package/docs/channels/teams.mdx +40 -26
- package/docs/channels/telegram.mdx +13 -13
- package/docs/channels/twilio.mdx +11 -11
- package/docs/code-extension.mdx +40 -42
- package/docs/concepts/built-in-tools.md +89 -57
- package/docs/concepts/context-control.md +20 -20
- package/docs/concepts/default-harness.md +20 -36
- package/docs/concepts/execution-model-and-durability.mdx +96 -160
- package/docs/concepts/project-structure.mdx +21 -14
- package/docs/concepts/security-model.md +27 -27
- package/docs/concepts/sessions-runs-and-streaming.md +184 -198
- package/docs/concepts/state.md +7 -15
- package/docs/connections/mcp.mdx +109 -93
- package/docs/connections/openapi.mdx +57 -59
- package/docs/connections/overview.mdx +175 -170
- package/docs/evals/assertions.mdx +36 -29
- package/docs/evals/cases.mdx +38 -42
- package/docs/evals/judge.mdx +21 -29
- package/docs/evals/overview.mdx +42 -38
- package/docs/evals/reporters.mdx +54 -27
- package/docs/evals/running.mdx +15 -8
- package/docs/evals/targets.mdx +16 -19
- package/docs/evals/tool-stubs.mdx +111 -97
- package/docs/experimental/dynamic-schedules.mdx +118 -63
- package/docs/extensions.md +58 -65
- package/docs/getting-started.mdx +4 -6
- package/docs/guides/auth-and-route-protection.md +87 -70
- package/docs/guides/client/continuations.mdx +23 -26
- package/docs/guides/client/messages.mdx +47 -66
- package/docs/guides/client/output-schema.mdx +8 -8
- package/docs/guides/client/overview.mdx +45 -43
- package/docs/guides/client/streaming.mdx +62 -71
- package/docs/guides/decide.md +24 -79
- package/docs/guides/deployment/meta.json +1 -1
- package/docs/guides/deployment/overview.md +27 -18
- package/docs/guides/deployment/self-hosted-operations.md +99 -0
- package/docs/guides/deployment/self-hosting.md +63 -80
- package/docs/guides/deployment/vercel.mdx +31 -27
- package/docs/guides/deployment/workflow-worlds.md +100 -0
- package/docs/guides/dev-tui.md +48 -41
- package/docs/guides/dynamic-capabilities.md +49 -50
- package/docs/guides/frontend/nextjs.mdx +2 -2
- package/docs/guides/frontend/nuxt.mdx +11 -11
- package/docs/guides/frontend/overview.mdx +1 -1
- package/docs/guides/frontend/sveltekit.mdx +11 -11
- package/docs/guides/frontend/tanstack.mdx +16 -16
- package/docs/guides/frontend/use-eve-agent-svelte.mdx +21 -21
- package/docs/guides/frontend/use-eve-agent-vue.mdx +22 -22
- package/docs/guides/frontend/use-eve-agent.mdx +25 -25
- package/docs/guides/hooks.md +152 -106
- package/docs/guides/instrumentation/agent-runs.mdx +26 -30
- package/docs/guides/instrumentation/instrumentation.mdx +49 -76
- package/docs/guides/instrumentation/meta.json +1 -1
- package/docs/guides/instrumentation/otel.mdx +113 -179
- package/docs/guides/remote-agents.md +125 -187
- package/docs/guides/self-modification.md +18 -18
- package/docs/guides/session-context.md +16 -16
- package/docs/install-integrations.mdx +26 -24
- package/docs/instructions.mdx +37 -42
- package/docs/memory/custom-provider.md +35 -41
- package/docs/memory/file.md +93 -76
- package/docs/memory/overview.mdx +145 -156
- package/docs/patterns/durable-cross-channel-notifications.md +15 -19
- package/docs/patterns/dynamic-scheduling.md +19 -23
- package/docs/patterns/multi-tenant-approvals.md +17 -22
- package/docs/patterns/multi-tenant-auth.md +43 -42
- package/docs/patterns/multi-tenant-memory.md +39 -36
- package/docs/patterns/voice-notes.md +3 -3
- package/docs/protocols/acp.md +13 -13
- package/docs/protocols/ucp.mdx +7 -7
- package/docs/reference/agent-files.md +6 -6
- package/docs/reference/cli.md +99 -98
- package/docs/reference/telemetry.md +1 -1
- package/docs/reference/typescript-api.md +52 -53
- package/docs/responsible-use.md +2 -2
- package/docs/sandbox/custom-providers.mdx +60 -56
- package/docs/sandbox/default.mdx +23 -24
- package/docs/sandbox/docker.mdx +16 -10
- package/docs/sandbox/index.mdx +93 -61
- package/docs/sandbox/just-bash.mdx +17 -11
- package/docs/sandbox/troubleshooting.mdx +29 -23
- package/docs/sandbox/vercel.mdx +45 -52
- package/docs/schedules.mdx +65 -54
- package/docs/skills.mdx +74 -49
- package/docs/subagents/index.mdx +97 -136
- package/docs/tools/human-in-the-loop.md +160 -90
- package/docs/tools/meta.json +1 -1
- package/docs/tools/overview.mdx +229 -237
- package/docs/tools/tasks.md +118 -117
- package/docs/tools/workflows.mdx +447 -543
- package/docs/tutorial/connect-a-warehouse.mdx +11 -13
- package/docs/tutorial/first-agent.mdx +14 -16
- package/docs/tutorial/guard-the-spend.mdx +6 -8
- package/docs/tutorial/how-it-runs.mdx +8 -8
- package/docs/tutorial/query-sample-data.mdx +8 -8
- package/docs/tutorial/remember-definitions.mdx +4 -4
- package/docs/tutorial/run-analysis.mdx +20 -22
- package/docs/tutorial/ship-it.mdx +19 -19
- package/docs/tutorial/team-playbooks.mdx +9 -9
- package/docs/use-cases.mdx +13 -11
- package/package.json +1 -1
- package/docs/guides/instrumentation/migration.md +0 -96
- package/docs/tools/tasks-upgrade.md +0 -218
package/docs/reference/cli.md
CHANGED
|
@@ -3,7 +3,7 @@ title: "CLI"
|
|
|
3
3
|
description: "Reference for every eve CLI command."
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
|
|
6
|
+
The `eve` CLI scaffolds, runs, inspects, and deploys agents. Run it from the application root or any directory beneath it. Running `eve` with no command runs `eve init` outside an eve project and `eve dev` inside one.
|
|
7
7
|
|
|
8
8
|
## Commands
|
|
9
9
|
|
|
@@ -25,11 +25,9 @@ Relevant `eve` commands can run from the application root or any directory benea
|
|
|
25
25
|
| `eve extension <command>` | Create and build extension packages |
|
|
26
26
|
| `eve telemetry <command>` | Manage CLI telemetry collection |
|
|
27
27
|
|
|
28
|
-
When `eve build` fails on discovery errors, it prints the full diagnostics report (severity, message, source path) and the diagnostics artifact path.
|
|
29
|
-
|
|
30
28
|
## CLI telemetry
|
|
31
29
|
|
|
32
|
-
eve collects CLI telemetry by default
|
|
30
|
+
eve collects CLI telemetry by default. Run `eve telemetry disable` to turn it off for this machine, or set `EVE_TELEMETRY_DISABLED=1` for one command. See [CLI telemetry](./telemetry) for collected fields, exclusions, debug mode, and preference storage.
|
|
33
31
|
|
|
34
32
|
## `eve init`
|
|
35
33
|
|
|
@@ -37,7 +35,7 @@ eve collects CLI telemetry by default to improve the command-line interface. Run
|
|
|
37
35
|
eve init [target] [--model <provider/model-id>] [--reasoning <effort>] [--non-interactive]
|
|
38
36
|
```
|
|
39
37
|
|
|
40
|
-
Creates a new agent app or adds an agent to an existing app.
|
|
38
|
+
Creates a new agent app or adds an agent to an existing app. It always installs dependencies, and initializes Git in new directories.
|
|
41
39
|
|
|
42
40
|
| Target | What happens |
|
|
43
41
|
| ---------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
|
|
@@ -47,16 +45,18 @@ Creates a new agent app or adds an agent to an existing app. Always installs dep
|
|
|
47
45
|
| `eve init` or `eve init .` in an existing project | Adds `agent/` plus missing `eve`, `ai`, and `zod` dependencies. Requires `package.json` and no existing `agent/` files |
|
|
48
46
|
| `eve init path/to/app` | Adds an agent to the existing package at `path/to/app` |
|
|
49
47
|
|
|
50
|
-
|
|
48
|
+
In non-interactive environments, a new project needs a directory name such as `eve init my-agent`. A nested path such as `eve init apps/my-agent` creates missing parent directories.
|
|
49
|
+
|
|
50
|
+
In an interactive terminal, eve opens the TUI after scaffolding. Pass `-n` or `--non-interactive` to return instead; dependency installation and Git setup still run. Non-interactive and coding-agent invocations always return without starting a session.
|
|
51
51
|
|
|
52
|
-
|
|
52
|
+
New projects use the parent workspace's package manager, or the one that launched `eve init` when there is no workspace.
|
|
53
53
|
|
|
54
54
|
| Flag | Type | Default | Description |
|
|
55
55
|
| ----------------------- | ------ | ---------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
|
|
56
56
|
| `--model <model>` | string | `openai/gpt-6-luna-fast` | Set the root agent's AI Gateway model ID. |
|
|
57
57
|
| `--reasoning <effort>` | enum | `high` without `--model`; otherwise provider default | Set reasoning to `none`, `minimal`, `low`, `medium`, `high`, or `xhigh`. `provider-default` leaves the field unauthored. |
|
|
58
58
|
| `--agents <names>` | string | unset | Create a new workspace with comma-separated agent names, such as `support,research`, or add members to an existing workspace. |
|
|
59
|
-
| `-y, --yes` | flag | off |
|
|
59
|
+
| `-y, --yes` | flag | off | Has no effect and prints a warning. |
|
|
60
60
|
| `-n, --non-interactive` | flag | off | Scaffold and install dependencies without starting development. |
|
|
61
61
|
|
|
62
62
|
## `eve extension`
|
|
@@ -77,8 +77,7 @@ Creates a new extension package, installs dependencies, and initializes Git. Pri
|
|
|
77
77
|
| `eve extension init .` | Scaffold in the current empty directory |
|
|
78
78
|
| No target | Same as `.` for humans; coding agents get a short setup guide |
|
|
79
79
|
|
|
80
|
-
|
|
81
|
-
`-y` and `--yes` are accepted for compatibility; they warn and have no effect.
|
|
80
|
+
It cannot target a directory that already has a `package.json`. `-y` and `--yes` have no effect and print a warning.
|
|
82
81
|
|
|
83
82
|
See [Extensions](/docs/extensions) for authoring and mount details.
|
|
84
83
|
|
|
@@ -88,33 +87,24 @@ See [Extensions](/docs/extensions) for authoring and mount details.
|
|
|
88
87
|
eve extension build
|
|
89
88
|
```
|
|
90
89
|
|
|
91
|
-
Builds the
|
|
90
|
+
Builds the extension's agent files into its configured `dist` root. It also writes type declarations and compatibility metadata, and fills the package `exports` map. The original TypeScript source is not required in the published package.
|
|
92
91
|
|
|
93
92
|
## Set model settings
|
|
94
93
|
|
|
95
|
-
|
|
94
|
+
`eve set model` changes the root agent's AI Gateway model, reasoning effort, or both, without opening the dev TUI:
|
|
96
95
|
|
|
97
96
|
```bash
|
|
98
97
|
eve set model openai/gpt-6-sol --reasoning high
|
|
99
98
|
eve set model --reasoning medium
|
|
100
99
|
```
|
|
101
100
|
|
|
102
|
-
|
|
103
|
-
the optional model argument to keep the current model. When you set both, eve
|
|
104
|
-
writes them to `agent/agent.ts` in one source edit. `--reasoning` accepts
|
|
105
|
-
`provider-default`, `none`, `minimal`, `low`, `medium`, `high`, or `xhigh`;
|
|
106
|
-
`provider-default` removes the authored `reasoning` field.
|
|
101
|
+
Omit the model argument to keep the current model. eve writes both settings to `agent/agent.ts` in one source edit. `--reasoning` accepts `provider-default`, `none`, `minimal`, `low`, `medium`, `high`, or `xhigh`; `provider-default` removes the authored `reasoning` field.
|
|
107
102
|
|
|
108
|
-
The command
|
|
109
|
-
the local dev TUI. It does not configure model credentials. The `model`
|
|
110
|
-
argument cannot rewrite models defined with `defineDynamic`, an environment expression,
|
|
111
|
-
or a provider-authored SDK model; change those models in `agent.ts`.
|
|
112
|
-
`--reasoning` can still update an editable root config when its model comes from
|
|
113
|
-
an SDK call.
|
|
103
|
+
The command validates and edits like `/model` in the dev TUI, and doesn't configure model credentials. It can't rewrite a model defined with `defineDynamic`, an environment expression, or a provider SDK model; change those in `agent.ts`. `--reasoning` still updates the root config when its model comes from an SDK call.
|
|
114
104
|
|
|
115
105
|
## Registry items
|
|
116
106
|
|
|
117
|
-
|
|
107
|
+
`eve add` and `eve registry` install and discover [shadcn registry](https://ui.shadcn.com/docs/registry) items. Official items use a kind and slug, such as `extension/agent-browser`; URLs and configured registry addresses also work.
|
|
118
108
|
|
|
119
109
|
```bash
|
|
120
110
|
eve add extension/agent-browser
|
|
@@ -129,13 +119,13 @@ eve registry view @acme/my-extension
|
|
|
129
119
|
eve add @acme/my-extension
|
|
130
120
|
```
|
|
131
121
|
|
|
132
|
-
`eve add` asks before running
|
|
122
|
+
`eve add` asks before running an official item's declared setup, and runs multiple flows in declaration order. Interactive Vercel-backed setup signs in and creates or links a project when needed. `--yes` accepts detected or recommended answers.
|
|
133
123
|
|
|
134
|
-
Coding agents should
|
|
124
|
+
Coding agents should run `eve add <item> --non-interactive --yes`. This mode never prompts. When a setup decision is missing, the final NDJSON event includes a stable question key and a continuation command. Add the answer to that command as a repeatable `--answer 'key=<JSON value>'` option, which takes precedence over `--yes`. Follow a reported `eve link` prerequisite before retrying Vercel Connect setup. Don't put secrets in answers; use the integration's documented environment variable or secret store.
|
|
135
125
|
|
|
136
|
-
When setup is skipped, cancelled, or needs more input
|
|
126
|
+
When setup is skipped, cancelled, or needs more input, eve prints or returns an `eve add <item> --skip-install` continuation. It reruns the item's setup flows without reinstalling registry files.
|
|
137
127
|
|
|
138
|
-
`eve registry add` records
|
|
128
|
+
`eve registry add` records sources in `package.json#registries`. `eve registry list` shows the official catalog and all configured sources. `eve registry search` also searches [skills.sh](https://skills.sh) as `@skills`, and groups results by source with each source's result count. Search returns up to 10 matches per source; pass `--limit <count>` for 1 to 100. Pass `--registry` to list or search one URL or namespace. Official and other universal items with explicit file targets don't need shadcn project configuration.
|
|
139
129
|
|
|
140
130
|
## `eve info`
|
|
141
131
|
|
|
@@ -147,11 +137,11 @@ eve info [--json]
|
|
|
147
137
|
| -------- | ---- | ------- | ------------ |
|
|
148
138
|
| `--json` | flag | off | Emit as JSON |
|
|
149
139
|
|
|
150
|
-
Run
|
|
140
|
+
Run `eve info` first when something behaves unexpectedly. It shows which files eve found and what the agent includes, and reports discovery diagnostics without starting the dev server. Static instructions appear in source order with their `system` or `user` role; dynamic instructions are runtime-only and don't appear.
|
|
151
141
|
|
|
152
142
|
### JSON output
|
|
153
143
|
|
|
154
|
-
`eve info --json` prints one JSON object
|
|
144
|
+
`eve info --json` prints one JSON object, so scripts and CI checks don't need to read files under `.eve/`:
|
|
155
145
|
|
|
156
146
|
| Field | Type | Description |
|
|
157
147
|
| ------------------ | ---------------- | ----------------------------------------------------------------------------------------- |
|
|
@@ -171,7 +161,13 @@ Run this first when something behaves unexpectedly. It confirms a file was disco
|
|
|
171
161
|
| `messaging` | object | Session route patterns: `{ create, messages, stream }` |
|
|
172
162
|
| `artifacts` | object or `null` | Paths to the compiled manifest, discovery manifest, diagnostics, module map, and metadata |
|
|
173
163
|
|
|
174
|
-
`toolInputSchemas.root` maps each root agent tool name
|
|
164
|
+
`toolInputSchemas.root` maps each root agent tool name, including namespaced extension tools, to its JSON Schema. `toolInputSchemas.subagents` holds the same map for each declared subagent, keyed by its path from the root. For example, a `reviewer` that `forecaster` declares is `forecaster/reviewer`.
|
|
165
|
+
|
|
166
|
+
Each schema is the form eve sends to the model:
|
|
167
|
+
|
|
168
|
+
- Validation-library schemas such as Zod set `additionalProperties: false` on closed objects.
|
|
169
|
+
- Plain JSON Schema stays as written.
|
|
170
|
+
- Tools that run as `serve` tasks, including agent tools, include the optional `taskId` input.
|
|
175
171
|
|
|
176
172
|
```json
|
|
177
173
|
{
|
|
@@ -200,7 +196,7 @@ Run this first when something behaves unexpectedly. It confirms a file was disco
|
|
|
200
196
|
}
|
|
201
197
|
```
|
|
202
198
|
|
|
203
|
-
`toolInputSchemas` covers only tools compiled from tool files. It
|
|
199
|
+
`toolInputSchemas` covers only tools compiled from tool files. It omits provider-managed tools such as `web_search`, dynamic tools, connection tools, the runtime-generated subagent and remote agent tools, and `eve__task_wait` and `eve__task_cancel`. It also doesn't reflect transformations a model provider applies before the model reads a schema.
|
|
204
200
|
|
|
205
201
|
## `eve build`
|
|
206
202
|
|
|
@@ -208,41 +204,38 @@ Run this first when something behaves unexpectedly. It confirms a file was disco
|
|
|
208
204
|
eve build [--profile <path>] [--skip-sandbox-prewarm]
|
|
209
205
|
```
|
|
210
206
|
|
|
211
|
-
Compiles and bundles
|
|
207
|
+
Compiles and bundles the agent, prepares sandbox artifacts, writes the host output, and prints its path. When discovery fails, it prints the full diagnostics report (severity, message, source path) and the diagnostics artifact path.
|
|
212
208
|
|
|
213
|
-
|
|
214
|
-
`-C`, or `NODE_OPTIONS`, so compilation and the bundle resolve each package to the same export.
|
|
215
|
-
For example, `NODE_OPTIONS="--conditions=react-server" eve build` selects the `react-server`
|
|
216
|
-
export of packages that publish one.
|
|
209
|
+
Pass `--skip-sandbox-prewarm` when you only need compiled output, such as before a separate typecheck. Don't deploy that output, because it might not start its configured sandbox.
|
|
217
210
|
|
|
218
|
-
|
|
219
|
-
|
|
220
|
-
|
|
211
|
+
Bundles preserve custom Node.js resolution conditions from `--conditions`, `-C`, or `NODE_OPTIONS`, so compilation and the bundle resolve each package to the same export. For example, `NODE_OPTIONS="--conditions=react-server" eve build` selects the `react-server` export of packages that publish one.
|
|
212
|
+
|
|
213
|
+
eve loads `server-only` and `client-only` imports as empty modules. Code shared with a Next.js app can keep them without a resolution condition or a dependency on either package.
|
|
221
214
|
|
|
222
215
|
| Flag | Type | Default | Description |
|
|
223
216
|
| ------------------------ | ------ | ------- | --------------------------------------------------------------------------------------------- |
|
|
224
217
|
| `--profile <path>` | string | off | Best-effort versioned JSON report with build-phase timings and final output-size measurements |
|
|
225
218
|
| `--skip-sandbox-prewarm` | flag | off | Skip sandbox preparation; the output might not be deployable |
|
|
226
219
|
|
|
227
|
-
Use a profile
|
|
220
|
+
Use a profile to establish a baseline before changing the build pipeline:
|
|
228
221
|
|
|
229
222
|
```bash
|
|
230
223
|
eve build --profile .eve/build-profiles/baseline.json
|
|
231
224
|
```
|
|
232
225
|
|
|
233
|
-
|
|
226
|
+
eve writes the profile only after a successful build. It records total time, phase timings, and the output's file count, raw bytes, and per-file gzip bytes. Vercel output adds a subtotal for each `.func` directory, so app and flow bundles compare separately. Self-hosted output adds `deploymentId`, the content-derived build identity. eve passes it to the Workflow World as `WORKFLOW_DEPLOYMENT_ID` when that variable isn't set. The profile path resolves from the app root; keep it outside the published output directory. A collection or write failure emits a warning without failing the build.
|
|
234
227
|
|
|
235
|
-
|
|
228
|
+
Builds can run while a dev server is active and alongside other builds. A failed build leaves the last successful `.output/` and agent summary untouched.
|
|
236
229
|
|
|
237
|
-
|
|
230
|
+
Inspection and development flows write these stable artifacts under `.eve/`:
|
|
238
231
|
|
|
239
|
-
| Artifact | Description
|
|
240
|
-
| ---------------------------------------------- |
|
|
241
|
-
| `.eve/discovery/agent-discovery-manifest.json` | What eve found on disk
|
|
242
|
-
| `.eve/discovery/diagnostics.json` | Authored-shape errors and warnings
|
|
243
|
-
| `.eve/compile/compiled-agent-manifest.json` | The
|
|
244
|
-
| `.eve/compile/compile-metadata.json` | Build-time metadata and paths
|
|
245
|
-
| `.eve/compile/module-map.mjs` | Compiled module entrypoints eve imports at runtime
|
|
232
|
+
| Artifact | Description |
|
|
233
|
+
| ---------------------------------------------- | -------------------------------------------------- |
|
|
234
|
+
| `.eve/discovery/agent-discovery-manifest.json` | What eve found on disk |
|
|
235
|
+
| `.eve/discovery/diagnostics.json` | Authored-shape errors and warnings |
|
|
236
|
+
| `.eve/compile/compiled-agent-manifest.json` | The compiled agent definition eve loads at runtime |
|
|
237
|
+
| `.eve/compile/compile-metadata.json` | Build-time metadata and paths |
|
|
238
|
+
| `.eve/compile/module-map.mjs` | Compiled module entrypoints eve imports at runtime |
|
|
246
239
|
|
|
247
240
|
## `eve start`
|
|
248
241
|
|
|
@@ -256,13 +249,13 @@ eve start [--host <host>] [--port <port>] [--no-schedules]
|
|
|
256
249
|
| `--port <port>` | number | `$PORT`, then 3000 | Port to listen on |
|
|
257
250
|
| `--no-schedules` | flag | schedules on | Start without running authored cron schedules |
|
|
258
251
|
|
|
259
|
-
Serves the
|
|
252
|
+
Serves the built output and prints the listening URL.
|
|
260
253
|
|
|
261
|
-
Set `EVE_SCHEDULES_DISABLED=1` or `true` (case-insensitive) to disable authored cron schedules at runtime
|
|
254
|
+
Set `EVE_SCHEDULES_DISABLED=1` or `true` (case-insensitive) to disable authored cron schedules at runtime. This also applies when you run `node .output/server/index.mjs` directly. Other values leave schedules on. HTTP requests and workflow jobs still run, and eve prints a `schedules disabled` line. `--no-schedules` sets the variable to `1` for the spawned server only; omit it to keep any value you set.
|
|
262
255
|
|
|
263
|
-
Use this setting when [scaling self-hosted replicas](../guides/deployment/self-
|
|
256
|
+
Use this setting when [scaling self-hosted replicas](../guides/deployment/self-hosted-operations#run-schedules). It also disables authored cron dispatch on Vercel if set there, but not explicit schedule dispatch in `eve dev`.
|
|
264
257
|
|
|
265
|
-
For self-hosted deployments, copy the app source, `.output/`, and installed dependencies together.
|
|
258
|
+
For self-hosted deployments, copy the app source, `.output/`, and installed dependencies together. Preserve the relative layout of workspace packages, because startup loads sandbox modules from the deployed source. The deployment directory can differ from the build directory.
|
|
266
259
|
|
|
267
260
|
## `eve dev`
|
|
268
261
|
|
|
@@ -289,39 +282,41 @@ Starts a local development server and terminal UI. To connect the UI to an exist
|
|
|
289
282
|
| `--context-size <tokens>` | number | none | Model context window size |
|
|
290
283
|
| `--logs <mode>` | enum | `error` | Display `none`, `error`, `warn`, `debug`, or `all` logs |
|
|
291
284
|
|
|
292
|
-
`localDev()` refuses callers
|
|
285
|
+
`localDev()` refuses callers connecting from another machine. When `--host` binds another interface, such as `0.0.0.0`, those callers need another authenticator in the channel's `auth` list. A same-machine tunnel or reverse proxy, such as ngrok, cloudflared, or a local nginx, connects locally. eve authenticates every caller it forwards as `local-dev`, so put an authenticator in front of any dev server you expose that way.
|
|
293
286
|
|
|
294
|
-
|
|
287
|
+
Bundled development extensions mount without adding files to your project; pass `--no-default-extensions` to disable them. See [Self-Modification](../guides/self-modification).
|
|
295
288
|
|
|
296
|
-
A fresh `eve init` opens the TUI and reuses an available model connection or opens `/login
|
|
289
|
+
A fresh `eve init` opens the TUI and reuses an available model connection or opens `/login`; chat needs no Vercel project, channels, or integrations. Use `/model` to change models and settings, and `/add` to install an addition. `--input` text stays editable in the prompt. See [Terminal UI](../guides/dev-tui) for credential precedence and login options.
|
|
297
290
|
|
|
298
291
|
### Local development lifecycle
|
|
299
292
|
|
|
300
|
-
|
|
293
|
+
A second interactive `eve dev` for the same app root reconnects to the running server when it is on loopback and healthy. Each terminal UI gets a fresh client session on the shared server. Passing `--host`, `--port`, or a `PORT` value skips reconnection and reports the running server instead.
|
|
294
|
+
|
|
295
|
+
Each rebuild saves a snapshot of the built code under `.eve/dev-runtime/snapshots/`. In-flight turns finish on the code they started with, and new turns use the latest rebuild. The terminal REPL keeps its session across rebuilds, so the next turn continues the conversation. `/new` ends that session and clears the transcript; the next prompt starts a fresh session with a new sandbox.
|
|
301
296
|
|
|
302
|
-
|
|
297
|
+
With any Workflow World, eve keeps each replaced snapshot for at least 30 minutes, and keeps the five most recently replaced snapshots. It never prunes the active snapshot. eve prunes old snapshots and local sandbox templates in the background, and a turn left unfinished past the retention window can't resume. To clean up manually, stop `eve dev` before deleting `.eve/dev-runtime/snapshots/` or `.eve/sandbox-cache/local/templates/`.
|
|
303
298
|
|
|
304
|
-
Local
|
|
299
|
+
Local dev records traces under `.eve/traces/`, bounded by age, size, and a keep-newest floor. Configure the store with `EVE_TRACES*` in `.env.local`, or disable it with `agent/instrumentation/local.ts`; see [`eve traces`](#retention).
|
|
305
300
|
|
|
306
|
-
`eve acp` reserves stdin and stdout for newline-delimited JSON-RPC and sends diagnostics to stderr. Without a URL, it supervises an isolated local development server. With a URL, it bridges ACP to that server's existing eve HTTP API. See [Agent Client Protocol (ACP)](../protocols/acp) for client configuration and
|
|
301
|
+
`eve acp` reserves stdin and stdout for newline-delimited JSON-RPC and sends diagnostics to stderr. Without a URL, it supervises an isolated local development server. With a URL, it bridges ACP to that server's existing eve HTTP API. See [Agent Client Protocol (ACP)](../protocols/acp) for client configuration and supported features.
|
|
307
302
|
|
|
308
303
|
### Local workflow recovery
|
|
309
304
|
|
|
310
|
-
With the built-in local Workflow World, a new `eve dev` server leaves previous invocations
|
|
305
|
+
With the built-in local Workflow World, a new `eve dev` server leaves runs from previous invocations dormant. Their timers and hooks don't fire. A message or control request to a dormant conversation fails instead of being accepted without a response; the HTTP channel reports its usual request failure. Start a new conversation, or restart with `eve dev --resume`. Already-open event streams are unaffected, and rebuilds and worker restarts within one server keep current runs eligible.
|
|
311
306
|
|
|
312
|
-
|
|
307
|
+
`eve dev --resume` attempts to recover unfinished runs from previous invocations that have a retained snapshot with readable metadata. Framework or workflow source changes don't block the attempt, but replay can fail and leave the run terminally failed after executing some work.
|
|
313
308
|
|
|
314
|
-
Runs with malformed
|
|
309
|
+
Runs with malformed snapshot metadata stay stored and dormant for that server invocation, and their later timers and hooks don't fire. `--resume` reports why it skipped them without blocking other runs. Restore the metadata from a backup or start a new session.
|
|
315
310
|
|
|
316
|
-
|
|
311
|
+
eve decides which runs to recover at startup. Hot reload doesn't recheck recovered runs against the latest workflow sources, so changing a workflow body while it runs can cause replay failure.
|
|
317
312
|
|
|
318
|
-
With the built-in local Workflow World, `eve dev` cancels unfinished runs whose
|
|
313
|
+
With the built-in local Workflow World, `eve dev` cancels unfinished runs whose snapshots are missing, at startup and after pruning. This includes waiting conversations and session timeout workflows. The reason goes in the run history without a terminal warning. Stopping `eve dev` doesn't cancel runs whose snapshots remain, but recovering them requires `--resume`.
|
|
319
314
|
|
|
320
|
-
|
|
315
|
+
`eve dev --resume`:
|
|
321
316
|
|
|
322
|
-
-
|
|
323
|
-
-
|
|
324
|
-
-
|
|
317
|
+
- Rejects custom Workflow Worlds, which don't use this cleanup and recovery policy.
|
|
318
|
+
- Refuses to attach to an already running local server.
|
|
319
|
+
- Recovers workflows, not the terminal transcript or a particular TUI conversation.
|
|
325
320
|
|
|
326
321
|
## `eve remote`
|
|
327
322
|
|
|
@@ -333,7 +328,7 @@ eve remote connect --url https://agent.example.com --print "Summarize station te
|
|
|
333
328
|
eve remote info --url https://agent.example.com
|
|
334
329
|
```
|
|
335
330
|
|
|
336
|
-
|
|
331
|
+
Remote commands never start a local application.
|
|
337
332
|
|
|
338
333
|
### `eve remote connect`
|
|
339
334
|
|
|
@@ -342,11 +337,11 @@ eve remote connect --url <url> [--input <text>] [-H "Name: value"]
|
|
|
342
337
|
eve remote connect --url <url> --print <prompt> [-H "Name: value"]
|
|
343
338
|
```
|
|
344
339
|
|
|
345
|
-
Without `--print`, `connect`
|
|
340
|
+
Without `--print`, `connect` opens the interactive UI and requires a terminal. With `--print <prompt>`, it sends one message, writes only the final assistant text to stdout, and exits. It exits nonzero with an error on stderr if the turn fails, is cancelled, or needs input or authorization. It also fails if the stream ends before the turn finishes. The error includes the session ID once the server accepted the message. Each `--print` starts a new conversation and can't answer pending requests; use the `eve/client` API for that or for multi-turn scripts. `--input` pre-fills the interactive UI and can't be combined with `--print`.
|
|
346
341
|
|
|
347
342
|
Interactive `connect` accepts the same display flags as [`eve dev`](#eve-dev): `--show-tools`, `--show-reasoning`, `--show-subagents`, `--show-connection-auth`, `--assistant-response-stats`, `--context-size`, and `--logs`. The `--show-*` flags control rendering, not model reasoning effort. Set effort with `eve set model --reasoning <effort>` or `eve init --reasoning <effort>`.
|
|
348
343
|
|
|
349
|
-
Use `-H, --header <header>` for a bearer token or another
|
|
344
|
+
Use `-H, --header <header>` for a bearer token or another request header; repeat it for multiple headers. For HTTP Basic authentication, put credentials in the URL; eve sends them as a Basic `Authorization` header and removes them from the target URL.
|
|
350
345
|
|
|
351
346
|
### `eve remote info`
|
|
352
347
|
|
|
@@ -366,15 +361,15 @@ eve logs --dump # prepend the log's environment dump
|
|
|
366
361
|
eve logs --events # interleave session events from the local workflow store
|
|
367
362
|
```
|
|
368
363
|
|
|
369
|
-
Each interactive `eve dev` process writes a private diagnostic log under `.eve/logs
|
|
364
|
+
Each interactive `eve dev` process writes a private JSON Lines diagnostic log under `.eve/logs/`, whatever the transcript shows. It captures stderr, stdout (including sandbox and rebuild lines), tool failures, workflow errors, and eve framework log records. Each line is one JSON record with `at` and `source` fields.
|
|
370
365
|
|
|
371
|
-
A log id is the file name without `.log
|
|
366
|
+
A log id is the file name without `.log`, such as `dev-2026-07-15T12-00-00.000Z-123`. `eve logs show <logid>` also accepts the file name or the `.eve/logs/...` path printed in the dev transcript. It also accepts an unambiguous id prefix with or without `dev-`, so `eve logs 2026-07-15` works when one log matches. An ambiguous prefix fails and lists the candidates.
|
|
372
367
|
|
|
373
|
-
`eve logs` prints
|
|
368
|
+
`eve logs` prints only records, with no path banner on either stream, so `eve logs 2>&1 | jq -c .` always parses. Find ids and paths with `eve logs list`; `--json` emits an array with `id`, `path`, `startedAt`, and `sizeBytes`.
|
|
374
369
|
|
|
375
|
-
`eve logs --events`
|
|
370
|
+
`eve logs --events` reads session events (`session.started`, `turn.settled`, content deltas, …) from the local workflow store. It interleaves them by timestamp as `source: "event"` records. It selects events by the log's time window (its start through the next log's start), so events from concurrent `eve dev` processes can appear.
|
|
376
371
|
|
|
377
|
-
Each log has a
|
|
372
|
+
Each log has a `.dump` sibling with environment diagnostics and session stats as one JSON document. `eve logs --dump` prepends it to the log body, producing a JSON value stream (`eve logs --dump | jq -c .`) to attach to an issue. When a log has no dump, the flag does nothing.
|
|
378
373
|
|
|
379
374
|
## `eve traces`
|
|
380
375
|
|
|
@@ -387,33 +382,35 @@ eve traces --verbose # expand every span with all attributes and events
|
|
|
387
382
|
eve traces --json # dump the full trace as JSON
|
|
388
383
|
```
|
|
389
384
|
|
|
390
|
-
|
|
385
|
+
`eve traces` reads the trace store under `.eve/traces/v1`, so `eve dev` need not be running. It accepts a full trace id, a `gen_ai.conversation.id`, or an unambiguous prefix of either. Malformed trace files don't hide valid spans from the same trace.
|
|
391
386
|
|
|
392
|
-
Span rows
|
|
387
|
+
Span rows show `↑input`/`↓output` token counts, gateway cost, and the tool name for `execute_tool` spans when recorded. The header lists the trace's models, sums token usage and cost from step spans, and counts error spans. `--json` prints the same records, one object per selected trace. `--verbose` expands each span with:
|
|
393
388
|
|
|
394
|
-
|
|
389
|
+
- Its status, error message, timing, and ids.
|
|
390
|
+
- Every attribute, with prompts, responses, and tool payloads shown as transcripts or pretty-printed JSON.
|
|
391
|
+
- Every span event, with its offset from span start.
|
|
395
392
|
|
|
396
|
-
Each
|
|
393
|
+
Each root agent turn starts a new trace. With local caller trace context, the first turn of a local subagent joins the caller's trace as a child of the dispatch span. A remote child starts a separate root trace and links its first turn to the dispatch with `eve.link.type=agent.dispatch`. Later child turns start new traces. Related sessions share a `gen_ai.conversation.id`, and `agent.subagent.name` identifies the subagent. Pass the conversation ID to show all related traces, oldest first. A turn keeps one trace even when its worker is replaced.
|
|
397
394
|
|
|
398
|
-
|
|
395
|
+
Each workflow tool call has one `execute_tool <tool>` span. The first turn of each local session that the tool opens with `ctx.agent` is a child of that span. A remote session links to the span from its own trace. A `ctx.agent` call has no separate dispatch span; only agent execution uses `invoke_agent`.
|
|
399
396
|
|
|
400
|
-
|
|
397
|
+
Outbound MCP `tools/call` requests add MCP semantic attributes to the matching `execute_tool` span, or create a `CLIENT` `tools/call <tool>` span when there is none. Each `tools/list` discovery has a `CLIENT` span. eve injects configured OpenTelemetry propagation fields into MCP `params._meta`. It skips injection, and sends the request unchanged, when the JSON-RPC body exceeds 1 MiB or the propagation metadata exceeds 8 KiB. It removes its audience and session-lineage baggage before forwarding, and keeps the content-capture policy local.
|
|
401
398
|
|
|
402
|
-
|
|
399
|
+
A call through `eve__tool` or `eve__skill` is traced like a direct call to the entry it names. Its `execute_tool` span carries that entry's name and input, such as `execute_tool linear__list_issues`. A skill load has an `execute_tool eve:load-skill` span. The AI SDK's own tracing channel, which eve doesn't filter, still reports the `eve__tool` or `eve__skill` call.
|
|
403
400
|
|
|
404
|
-
|
|
401
|
+
A turn's root `invoke_agent` span is written when the turn ends, so a running turn shows only its steps.
|
|
405
402
|
|
|
406
403
|
Model, `execute_tool`, and memory spans retain their content by default. Set `EVE_TRACES_CONTENT=off` to omit system prompts, prompt messages, and response text for models; call arguments and results for tools; and recalled memory records. Each captured value is capped at 32 KB. When a model call's prompt messages exceed the cap, the oldest are dropped first and `agent.input.messages.omitted` records how many.
|
|
407
404
|
|
|
408
|
-
Step spans carry token counts under `agent.usage.*`, and cost when Vercel AI Gateway served the call. Model spans also expose `gen_ai.usage.*`
|
|
405
|
+
Step spans carry token counts under `agent.usage.*`, and cost when Vercel AI Gateway served the call. Model spans also expose `gen_ai.usage.*` counters. The CLI sums step-level counters only, so totals aren't counted twice.
|
|
409
406
|
|
|
410
407
|
### Retention
|
|
411
408
|
|
|
412
|
-
eve
|
|
409
|
+
eve prunes the store as turns write traces, when a session finishes, and when the dev server starts. Pruning evicts the oldest traces past the bounds below. It keeps active traces, the newest traces, and anything written in the last five minutes, so the store can exceed its size budget. An open conversation doesn't pin its completed turns' traces. Set the bounds in `.env.local`, which `eve dev` loads automatically; each accepts `off`.
|
|
413
410
|
|
|
414
411
|
| Variable | Default | Effect |
|
|
415
412
|
| ---------------------------- | -------------------- | ------------------------------------------------------------------------------------------------- |
|
|
416
|
-
| `EVE_TRACES` | on | `off` stops writing traces and stops
|
|
413
|
+
| `EVE_TRACES` | on | `off` stops writing traces and stops pruning |
|
|
417
414
|
| `EVE_TRACES_CONTENT` | on | `off` omits model prompt/response, tool input/output, and memory-record attributes on local spans |
|
|
418
415
|
| `EVE_TRACES_MAX_AGE_MS` | `604800000` (7d) | Age after which a trace may be evicted |
|
|
419
416
|
| `EVE_TRACES_MAX_TOTAL_BYTES` | `536870912` (512 MB) | Size budget for the whole store |
|
|
@@ -426,9 +423,9 @@ eve link
|
|
|
426
423
|
eve link --non-interactive --project <name-or-id> [--team <team-id-or-slug>]
|
|
427
424
|
```
|
|
428
425
|
|
|
429
|
-
Links the current directory to a Vercel project. After
|
|
426
|
+
Links the current directory to a Vercel project. After you select a team, create a project named for the agent or link an existing one. The picker shows recent projects; type a name and choose **Search for `'<name>'`** to search the rest of the team's projects. eve verifies the linked project ID, then pulls the project's environment so an AI Gateway credential (`VERCEL_OIDC_TOKEN` or `AI_GATEWAY_API_KEY`) lands in `.env.local`. Running it again re-links with fresh pickers.
|
|
430
427
|
|
|
431
|
-
For CI or an agent, pass `--non-interactive` and `--project`. `--project` accepts
|
|
428
|
+
For CI or an agent, pass `--non-interactive` and `--project`. Like `vercel link`, `--project` accepts a Vercel project name or ID, and `--team` accepts a team ID or slug. This mode never opens a picker or browser. A running `eve dev` reloads env files automatically after the pull.
|
|
432
429
|
|
|
433
430
|
## `eve deploy`
|
|
434
431
|
|
|
@@ -437,9 +434,9 @@ eve deploy
|
|
|
437
434
|
eve deploy --non-interactive --yes [--project <name-or-id>] [--team <team-id-or-slug>]
|
|
438
435
|
```
|
|
439
436
|
|
|
440
|
-
Deploys the agent to Vercel production (`vercel deploy --prod`), installing dependencies first and pulling environment variables after.
|
|
437
|
+
Deploys the agent to Vercel production (`vercel deploy --prod`), installing dependencies first and pulling environment variables after. A linked project deploys with or without a TTY. In a terminal, an unlinked project signs in to Vercel if needed and runs the `eve link` pickers.
|
|
441
438
|
|
|
442
|
-
For CI or an agent, pass `--non-interactive --yes
|
|
439
|
+
For CI or an agent, pass `--non-interactive --yes`; `--yes` confirms the production deployment. `--project` links that Vercel project and pulls its environment before deploying, and `--team` works as in `eve link`. Without `--project`, the directory must already be linked. This mode never opens a picker, browser, or login flow.
|
|
443
440
|
|
|
444
441
|
## `eve eval`
|
|
445
442
|
|
|
@@ -447,9 +444,15 @@ For CI or an agent, pass `--non-interactive --yes`. `--yes` explicitly confirms
|
|
|
447
444
|
eve eval [evalId...] [--url <url>] [options]
|
|
448
445
|
```
|
|
449
446
|
|
|
450
|
-
Runs all discovered evals when
|
|
447
|
+
Runs the given evals, or all discovered evals when you omit ids. Ids match exactly or by directory prefix, so `eve eval weather` runs everything under `evals/weather/`.
|
|
451
448
|
|
|
452
|
-
|
|
449
|
+
| Exit code | Meaning |
|
|
450
|
+
| --------- | ------------------------------------------------------------------------ |
|
|
451
|
+
| `0` | Every eval passed |
|
|
452
|
+
| `1` | An eval failed: a failed check, an execution error, or a `--strict` miss |
|
|
453
|
+
| `2` | Configuration error |
|
|
454
|
+
|
|
455
|
+
Without `--url`, `eve eval` starts its own local server on a free port with state under `.eve/eval-servers/<run id>/`, removed after the run unless you pass `--keep-state`. A kept directory, including Workflow data in `.workflow-data/`, stays until a later `eve eval` in the same app cleans it up. The server runs beside an `eve dev` session for the same agent without touching it.
|
|
453
456
|
|
|
454
457
|
| Flag | Type | Default | Description |
|
|
455
458
|
| ------------------------ | ------ | ------- | -------------------------------------------------------------- |
|
|
@@ -477,8 +480,6 @@ See [Evals](../evals/overview) for authoring evals.
|
|
|
477
480
|
4. `eve build` before shipping.
|
|
478
481
|
5. `eve start` to smoke-test the built output locally.
|
|
479
482
|
|
|
480
|
-
Related: [Agent Files](/docs/reference/agent-files) · [Instrumentation](../observability/instrumentation).
|
|
481
|
-
|
|
482
483
|
## What to read next
|
|
483
484
|
|
|
484
485
|
- [Agent Files](/docs/reference/agent-files): what `eve info` discovers
|
|
@@ -5,7 +5,7 @@ description: "Learn what eve CLI telemetry collects and how to control it."
|
|
|
5
5
|
|
|
6
6
|
# CLI telemetry
|
|
7
7
|
|
|
8
|
-
eve collects usage data
|
|
8
|
+
eve collects CLI usage data to improve its commands and development experience. You can turn telemetry off at any time.
|
|
9
9
|
|
|
10
10
|
## What eve collects
|
|
11
11
|
|