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/guides/dev-tui.md
CHANGED
|
@@ -3,19 +3,15 @@ title: "Terminal UI"
|
|
|
3
3
|
description: "Use eve locally or connect to a deployed agent from an interactive terminal UI."
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
`eve dev` starts a local development server and opens an interactive terminal UI.
|
|
6
|
+
`eve dev` starts a local development server and opens an interactive terminal UI. In the UI, you talk to your agent, approve tool calls, answer its questions, and configure local development. Self-modification is on by default in a local server; see [Self-Modification](./self-modification).
|
|
7
7
|
|
|
8
8
|
```bash
|
|
9
9
|
eve dev
|
|
10
10
|
```
|
|
11
11
|
|
|
12
|
-
The footer shows the active model, reasoning level when set, speed indicator, and connection
|
|
12
|
+
The footer shows the active model, reasoning level when set, speed indicator, and connection, such as `gpt-6-luna · high · ⚡︎`. The model label drops the provider prefix and a trailing `-fast`; `⚡︎` marks a `-fast` model or **Fast** mode. A Vercel account connection shows the team slug once it resolves.
|
|
13
13
|
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
The transcript remains in your terminal scrollback after you exit. Run `/help` in the UI to see the commands available in the current session.
|
|
17
|
-
|
|
18
|
-
Before your first message, the empty composer may suggest asking your local agent to edit its instructions or add a tool or channel. The suggestion depends on the agent's current capabilities; typing replaces it without sending a message or changing files.
|
|
14
|
+
The transcript stays in your terminal scrollback after you exit. Before your first message, the empty composer may suggest a change to ask your agent for; typing replaces the suggestion.
|
|
19
15
|
|
|
20
16
|
## Commands
|
|
21
17
|
|
|
@@ -23,9 +19,9 @@ Before your first message, the empty composer may suggest asking your local agen
|
|
|
23
19
|
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
|
24
20
|
| `/model` | Choose the model, speed, and reasoning. Pass a model ID to set it directly: `/model provider/model-id`. |
|
|
25
21
|
| `/new` | Start a fresh session and clear the screen. `/reset` is an alias. |
|
|
26
|
-
| `/clear` |
|
|
22
|
+
| `/clear` | Cancel the running turn and every working task, then clear the session's model-message history and keep the session. |
|
|
27
23
|
| `/compact` | Compact the current session's context. |
|
|
28
|
-
| `/cancel` | Cancel the current turn
|
|
24
|
+
| `/cancel` | Cancel the current turn and keep the context from work that already finished. |
|
|
29
25
|
| `/login` | Connect a ChatGPT subscription, Vercel account, or provider API key. |
|
|
30
26
|
| `/add` | Select and install channels, MCP connections, extensions, and observability integrations. Pass an item address to install it directly: `/add channel/slack`. |
|
|
31
27
|
| `/deploy` | Deploy the agent to Vercel production. Installs the Vercel CLI, signs in, and links the directory if needed. |
|
|
@@ -35,15 +31,15 @@ Before your first message, the empty composer may suggest asking your local agen
|
|
|
35
31
|
| `/help` | List available commands. |
|
|
36
32
|
| `/exit` | Quit the UI. |
|
|
37
33
|
|
|
38
|
-
|
|
34
|
+
`/login`, `/model`, `/add`, `/deploy`, `/info`, and `/traces` work only in local `eve dev`, not through `eve remote connect`.
|
|
39
35
|
|
|
40
|
-
|
|
36
|
+
A [stranded session](./deployment/self-hosted-operations#recover-a-stranded-session) accepts no new messages or approvals. When a message or a stream reconnect reaches one, the TUI says why and, when known, which eve version built it. Run `/new` to end it; your next message starts a fresh session. `/clear` is refused because it would keep the stranded session. A message accepted before the upgrade is not redelivered. A session from an earlier `eve dev` process built by the same eve version is not stranded; see [local workflow recovery](../reference/cli#local-workflow-recovery).
|
|
41
37
|
|
|
42
38
|
## Set up a new agent
|
|
43
39
|
|
|
44
|
-
After interactive `eve init`, the TUI opens directly. eve keeps the
|
|
40
|
+
After interactive `eve init`, the TUI opens directly. eve keeps the connection already selected for the project, including a project OIDC connection. Without one, it checks credentials set in the environment, the saved machine default, and then the Vercel CLI's current team. With the Vercel CLI team, eve checks account access but doesn't create or link a Vercel project.
|
|
45
41
|
|
|
46
|
-
During startup,
|
|
42
|
+
During startup, a progress indicator names the connection being checked. Messages you send before the agent is ready are queued. A picker takes over input when a choice or API key is needed, then your draft returns. If setup is cancelled or fails, queued messages return to the draft.
|
|
47
43
|
|
|
48
44
|
If no connection is ready, `/login` offers:
|
|
49
45
|
|
|
@@ -53,15 +49,15 @@ If no connection is ready, `/login` offers:
|
|
|
53
49
|
4. OpenAI API Key
|
|
54
50
|
5. Anthropic API Key
|
|
55
51
|
|
|
56
|
-
Vercel account login opens a browser.
|
|
52
|
+
Vercel account login opens a browser. With several teams, `/login` shows a searchable team picker with the current project or CLI team highlighted; a sole team is selected automatically. Account-token access to Gateway depends on your account and team; if it is unavailable, choose an API key or another connection.
|
|
57
53
|
|
|
58
|
-
|
|
54
|
+
In a menu, type to filter, use the arrow keys, press `Enter` to select, or press `Esc` to return to chat. Cancelling login preserves your draft. If a connection fails, retry `/login`; eve does not switch providers on its own.
|
|
59
55
|
|
|
60
56
|
### Credentials and deployment
|
|
61
57
|
|
|
62
|
-
eve saves API keys and
|
|
58
|
+
eve saves API keys and its OAuth refresh credentials in the OS secret store, never in project files. The last successful login becomes the machine default. eve records the project's connection and team, which aren't secret, in `.eve/provider.json`. A key selected through `/login` takes precedence over the same provider's key in your shell. A project connected through environment credentials keeps using its environment. The Vercel CLI keeps its own credentials.
|
|
63
59
|
|
|
64
|
-
|
|
60
|
+
Credential discovery runs only in local development. Deployments need `AI_GATEWAY_API_KEY`, `OPENAI_API_KEY`, `ANTHROPIC_API_KEY`, or project OIDC credentials. ChatGPT subscription models are local-only. `/login` doesn't link a deployment or authenticate a remote server; `/deploy` installs the Vercel CLI and signs you in when needed.
|
|
65
61
|
|
|
66
62
|
### Models and settings
|
|
67
63
|
|
|
@@ -71,17 +67,13 @@ Local discovery runs only in development. Deployments need explicitly provisione
|
|
|
71
67
|
2. Choose **Standard** or **Fast** speed, when supported.
|
|
72
68
|
3. Choose a reasoning level, when the model supports reasoning settings. **Provider default** leaves the reasoning level to the provider.
|
|
73
69
|
|
|
74
|
-
The picker highlights your current settings
|
|
75
|
-
|
|
76
|
-
Changes apply together after the final choice, then the picker returns to chat. Cancelling leaves your model and settings unchanged.
|
|
77
|
-
|
|
78
|
-
A successful login or model change takes effect on the next prompt.
|
|
70
|
+
The picker highlights your compatible current settings and skips settings that can't change. `Enter` advances, `Esc` or `←` goes back a step or cancels at the model list, and `Ctrl+C` cancels from any step. Changes apply together after the final choice; cancelling changes nothing. A login or model change takes effect on the next prompt.
|
|
79
71
|
|
|
80
|
-
Gateway connections default to `openai/gpt-6-luna-fast
|
|
72
|
+
Gateway connections default to `openai/gpt-6-luna-fast`, OpenAI and ChatGPT to `gpt-6-luna-fast`, and Anthropic to `claude-sonnet-5`. An authored compatible model stays selected. If the default is unavailable, eve offers the connection's available models. Edit dynamic or custom model expressions in `agent.ts`.
|
|
81
73
|
|
|
82
74
|
## Add an integration
|
|
83
75
|
|
|
84
|
-
`/add` opens
|
|
76
|
+
`/add` opens a searchable catalog of channels, connections, extensions, and integrations. Press `Enter` to install an item and run its setup, then return to chat.
|
|
85
77
|
|
|
86
78
|
Pass an item address to install it directly:
|
|
87
79
|
|
|
@@ -92,21 +84,30 @@ Pass an item address to install it directly:
|
|
|
92
84
|
/add @acme/analytics
|
|
93
85
|
```
|
|
94
86
|
|
|
95
|
-
|
|
87
|
+
Press `Esc` to cancel setup; files already installed stay in the project. If dependency installation fails, rerun the `eve add` command in a terminal to see the installer output.
|
|
96
88
|
|
|
97
89
|
## Work with the agent
|
|
98
90
|
|
|
99
|
-
Type a message and press `Enter` to send it.
|
|
91
|
+
Type a message and press `Enter` to send it. Answer questions and tool approvals in the prompt the UI shows; each answer is sent as soon as you give it. With several open requests, the prompt shows its position, such as `2 of 5`, and names the task that asked. Connection authorization can open a browser; keep local `eve dev` running until the browser returns to it.
|
|
92
|
+
|
|
93
|
+
The activity line shows elapsed time and token counts when available, with one of these states:
|
|
94
|
+
|
|
95
|
+
- **Thinking**: the model reasons or waits.
|
|
96
|
+
- **Generating**: the model writes a response or tool input.
|
|
97
|
+
- **Running**: tools execute. While [tasks](../tools/tasks) work, the task drawer header replaces this line with the parent's activity, task count, and turn time. **Waiting** means the parent is waiting on tasks; **Working** means tasks remain active between turns.
|
|
98
|
+
|
|
99
|
+
A tool call shows the tool's `label`, or eve's text for a built-in tool, such as `Read README.md`. Other tools show a readable name without the extension or connection prefix, such as `List issues` for `linear__list_issues`. Approval prompts use the same name, such as `Approve Linear: List issues?`.
|
|
100
100
|
|
|
101
|
-
|
|
101
|
+
A task, such as a subagent call, writes one transcript line when it starts and one when it finishes, fails, or is stopped. The finished line shows the duration and, for a subagent, what it did, such as `Read 3 files, Ran 2 commands`.
|
|
102
102
|
|
|
103
|
-
|
|
103
|
+
While tasks work, a drawer above the prompt shows each task's name, latest tool, and elapsed time. Subagents get readable labels, such as `subagent(stock price)` for `stock-price` or `subagent(worker)` for the code extension's `code__worker`. Work started by a subagent appears beneath it. The drawer caps its height, puts tasks awaiting approval first, and yields to questions and approvals on small terminals. The model's `eve__task_wait` and `eve__task_cancel` calls appear only as the **Waiting** header and a stopped task's line.
|
|
104
104
|
|
|
105
|
-
|
|
105
|
+
The prompt stays open while the agent works, including turns started elsewhere, such as a scheduled run. Pressing `Enter` during a turn sends your message as steering, which adds it to the running turn:
|
|
106
106
|
|
|
107
|
-
|
|
107
|
+
- Before the agent starts writing its reply, steering stops the model and continues the turn with your message. Running tools finish first.
|
|
108
|
+
- After the reply starts, the streamed text stays, and your message joins the turn at its next step. See [Message delivery and steering](../concepts/execution-model-and-durability#message-delivery-and-steering).
|
|
108
109
|
|
|
109
|
-
Slash commands run immediately, even during a turn. Press `Esc` or `Ctrl+C`, or run `/cancel`, to cancel a running turn.
|
|
110
|
+
Slash commands run immediately, even during a turn. Press `Esc` or `Ctrl+C`, or run `/cancel`, to cancel a running turn. A cancel sent before the turn starts applies only to that turn, never to a later one. If the cancel doesn't finish, press `Ctrl+C` again to stop waiting and start a new session; the next `Ctrl+C` exits. At an idle prompt, press `Ctrl+C` twice to exit.
|
|
110
111
|
|
|
111
112
|
| Key | Action |
|
|
112
113
|
| ------------- | ---------------------------------------------------------------------------------------------------------- |
|
|
@@ -120,44 +121,50 @@ Slash commands run immediately, even during a turn. Press `Esc` or `Ctrl+C`, or
|
|
|
120
121
|
|
|
121
122
|
## Logs and traces
|
|
122
123
|
|
|
123
|
-
|
|
124
|
+
The UI shows severity-tagged errors by default. Run `/loglevel <mode>` or press `Ctrl+L` to change the display; bare `/loglevel` reports the current mode.
|
|
124
125
|
|
|
125
|
-
|
|
126
|
+
| Mode | Shows |
|
|
127
|
+
| ------- | --------------------------------------------------------------------------------------------------------------------- |
|
|
128
|
+
| `none` | No logs. |
|
|
129
|
+
| `error` | Errors (default). |
|
|
130
|
+
| `warn` | Errors and warnings. |
|
|
131
|
+
| `debug` | All severity-tagged records. |
|
|
132
|
+
| `all` | Also unclassified stdout, stderr, sandbox output, and Workflow SDK lines such as `[workflow-sdk]` or `[world-local]`. |
|
|
126
133
|
|
|
127
|
-
Every `eve dev` process writes diagnostic logs to `.eve/logs
|
|
134
|
+
These modes filter the display only; they don't change `EVE_LOG_LEVEL` or a dependency's debug logging. Every `eve dev` process writes diagnostic logs to `.eve/logs/` regardless of mode. Read them with [`eve logs`](../reference/cli#eve-logs).
|
|
128
135
|
|
|
129
136
|
Use `/traces` to inspect traces recorded during local development. See [Local traces](../observability/otel#local-traces) for trace capture and retention settings.
|
|
130
137
|
|
|
131
138
|
## Display options
|
|
132
139
|
|
|
133
|
-
|
|
140
|
+
`eve dev` flags control how tool calls, reasoning, subagents, connection authorization, response statistics, context usage, and logs display:
|
|
134
141
|
|
|
135
142
|
```bash
|
|
136
143
|
eve dev --show-tools full --show-reasoning collapsed --logs all
|
|
137
144
|
```
|
|
138
145
|
|
|
139
|
-
`--show-subagents` accepts `collapsed` (
|
|
146
|
+
`--show-subagents` accepts `collapsed` (default), `full`, or `hidden`. `full` also writes each subagent message and tool call to the transcript, and `hidden` leaves subagent tasks out of the transcript and the drawer.
|
|
140
147
|
|
|
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
|
|
148
|
+
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 responses as plain text instead of rendered Markdown. See the [`eve dev` CLI reference](../reference/cli#eve-dev) for the complete option list, accepted values, and defaults.
|
|
142
149
|
|
|
143
150
|
## Connect to a deployment
|
|
144
151
|
|
|
145
|
-
|
|
152
|
+
`eve remote connect` opens the terminal UI against an existing eve server instead of starting one locally:
|
|
146
153
|
|
|
147
154
|
```bash
|
|
148
155
|
eve remote connect --url https://your-app.vercel.app
|
|
149
156
|
```
|
|
150
157
|
|
|
151
|
-
|
|
158
|
+
To send credentials or custom request headers, use a URL with HTTP Basic credentials or repeat `-H, --header`:
|
|
152
159
|
|
|
153
160
|
```bash
|
|
154
161
|
eve remote connect --url https://user:pass@your-app.example.com
|
|
155
162
|
eve remote connect --url https://your-app.example.com -H 'Authorization: Bearer your_token_here'
|
|
156
163
|
```
|
|
157
164
|
|
|
158
|
-
Remote Vercel sessions reuse an
|
|
165
|
+
Remote Vercel sessions reuse an authorized Vercel CLI session. They don't open a login flow or change the local project's Vercel link or `.env.local`.
|
|
159
166
|
|
|
160
|
-
When Deployment Protection blocks startup, eve verifies the target project and
|
|
167
|
+
When Deployment Protection blocks startup, eve verifies the target project and offers to add a Trusted Sources rule. The rule grants development access to that deployment's environment, and eve then rechecks access. Cancelling preserves your draft; rerun `eve remote connect --url <url>` to try again. If you can't change the project's policy, provide `VERCEL_AUTOMATION_BYPASS_SECRET` or ask a project administrator to configure access in Deployment Protection settings.
|
|
161
168
|
|
|
162
169
|
## What to read next
|
|
163
170
|
|
|
@@ -3,26 +3,29 @@ title: "Dynamic Capabilities"
|
|
|
3
3
|
description: "Compute models, subagents, connections, tools, skills, and instructions from the session with defineDynamic."
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
|
|
6
|
+
`defineDynamic(fn)` builds a model, subagent, connection, tool, skill, or instructions from the caller, the conversation, or external data. The function returns the definition, or `null` to leave it out. Import `defineDynamic` from `eve` or from the entry point of what you define, such as `eve/tools`.
|
|
7
7
|
|
|
8
|
-
eve
|
|
8
|
+
eve runs the function before every ordinary model call, including when a turn continues after steering, a sign-in, or an approval. It doesn't run for compaction's summary call or `auto()`'s routing call. Introspection reads the values it last returned.
|
|
9
9
|
|
|
10
|
-
The module's top-level code runs
|
|
10
|
+
The module's top-level code runs at build time and at runtime, so keep caller-specific work inside the function. See [Authored module lifecycle](../reference/typescript-api#authored-module-lifecycle).
|
|
11
11
|
|
|
12
12
|
## Context and memoization
|
|
13
13
|
|
|
14
14
|
Every dynamic function receives:
|
|
15
15
|
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
16
|
+
| Field | Contents |
|
|
17
|
+
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
|
|
18
|
+
| `ctx.session` | Session ID, authenticated caller and initiator, and optional schedule and predecessor. |
|
|
19
|
+
| `ctx.session.parent` | In a delegated session: the parent session, its turn, the call that opened this session, and `rootSessionId`. Absent in a root session. |
|
|
20
|
+
| `ctx.channel` | Channel kind, continuation token, and metadata. Narrow typed metadata with `isChannel`. |
|
|
21
|
+
| `ctx.view` | Read-only view of the session so far. Read it with selectors from `eve/events`, such as `turns(ctx.view)`. |
|
|
22
|
+
| `ctx.turn` | Latest turn, with its ID, input, and status; `null` before the first turn. |
|
|
23
|
+
| `ctx.now` | Time of the latest recorded session event, as a `Date`. |
|
|
24
|
+
| `ctx.model.id` | Selected model ID. Unavailable inside the `model` field, before the model is chosen. |
|
|
25
|
+
| `await ctx.messages()` | The conversation so far, assembled only when you call it. |
|
|
26
|
+
| `await ctx.memo(key, fn)` | A saved JSON result for a key. |
|
|
24
27
|
|
|
25
|
-
Code outside a memo runs
|
|
28
|
+
Code outside a memo runs every time eve runs the function. Put a fetch or decision inside a memo when its answer should stay fixed for a key:
|
|
26
29
|
|
|
27
30
|
```ts title="agent/tools/query.ts"
|
|
28
31
|
import { defineDynamic, defineTool } from "eve/tools";
|
|
@@ -44,36 +47,36 @@ export default defineDynamic(async (ctx) => {
|
|
|
44
47
|
});
|
|
45
48
|
```
|
|
46
49
|
|
|
47
|
-
After a cold start, eve
|
|
50
|
+
After a cold start, eve runs the function again. The memo returns the saved tables without querying the database, and ordinary code rebuilds the tools and their callbacks.
|
|
48
51
|
|
|
49
52
|
### Choose a lifetime
|
|
50
53
|
|
|
51
54
|
| Key | Observation runs |
|
|
52
55
|
| ---------------------- | ------------------------------------------- |
|
|
53
|
-
| No memo | Every
|
|
56
|
+
| No memo | Every run of the function |
|
|
54
57
|
| `ctx.turn?.id ?? null` | Once per turn |
|
|
55
58
|
| `ctx.session.id` | Once per session, until a deployment change |
|
|
56
59
|
| A caller or tenant ID | When that key changes |
|
|
57
60
|
|
|
58
|
-
The key
|
|
61
|
+
The key sets a lifetime, not a dependency list. A change in context that the callback reads doesn't clear a saved result.
|
|
59
62
|
|
|
60
63
|
### Memo rules
|
|
61
64
|
|
|
62
65
|
- Keys compare as canonical JSON. A top-level `undefined` key means `null`; `undefined` inside a key is rejected. Use `tenantId ?? null` to represent a missing value explicitly. A key is at most 64 KB and a result at most 1 MB. Save plain JSON, not clients, functions, dates, or schemas.
|
|
63
|
-
- Each definition or hook retains at most 4 MB of memo JSON, including
|
|
66
|
+
- Each definition or hook retains at most 4 MB of memo JSON, including keys. Memoize a collection rather than each row, and keep IDs instead of whole records.
|
|
64
67
|
- Identity includes the session and mounted definition. Separate files do not share memo results.
|
|
65
|
-
- Give multiple memos distinct keys, usually tuples such as `["tables", tenantId]` and `["flags", ctx.turn?.id ?? null]`. Reusing a key in one
|
|
66
|
-
-
|
|
67
|
-
- A failing memo keeps no result. Successful memos survive a later error in the definition if they fit alongside its
|
|
68
|
-
- Deployment changes discard memos.
|
|
68
|
+
- Give multiple memos distinct keys, usually tuples such as `["tables", tenantId]` and `["flags", ctx.turn?.id ?? null]`. Reusing a key in one run of the function throws.
|
|
69
|
+
- eve keeps only the keys that the latest successful run used. A skipped branch loses its saved results; returning to it runs the callback again.
|
|
70
|
+
- A failing memo keeps no result. Successful memos survive a later error in the definition if they fit alongside its earlier memo results. If they don't fit within 4 MB, eve keeps the earlier results, and the new memos run again next time.
|
|
71
|
+
- Deployment changes discard memos. Memos are a cache, not a record of side effects.
|
|
69
72
|
- Memos can run concurrently with `Promise.all`, but cannot nest. Await every memo before returning.
|
|
70
|
-
-
|
|
73
|
+
- Memo results are saved privately with the session and never appear on the stream.
|
|
71
74
|
|
|
72
|
-
A memo callback receives `{ idempotencyKey, abortSignal }`. Pass
|
|
75
|
+
A memo callback receives `{ idempotencyKey, abortSignal }`. Pass `idempotencyKey` to an external service that supports idempotency, because an interrupted step can run again before eve saves its result. The key is stable per session, definition, and memo key. It repeats when a deployment change or skipped branch runs the memo again, so send your own key when a run needs a fresh response. Perform side effects in [hooks](./hooks) or tool execution, not while computing a definition.
|
|
73
76
|
|
|
74
77
|
## Dynamic models
|
|
75
78
|
|
|
76
|
-
The agent's `model` field accepts a dynamic function
|
|
79
|
+
The agent's `model` field accepts a dynamic function that returns a model ID, a provider instance, or a selection containing `model` and optional model settings. A missing or invalid model fails the turn. `ctx.model` is unavailable here.
|
|
77
80
|
|
|
78
81
|
```ts title="agent/agent.ts"
|
|
79
82
|
import { defineAgent, defineDynamic } from "eve";
|
|
@@ -110,11 +113,11 @@ export default defineDynamic((ctx) =>
|
|
|
110
113
|
);
|
|
111
114
|
```
|
|
112
115
|
|
|
113
|
-
|
|
116
|
+
The child's tools, instructions, skills, and nested subagents still build from the filesystem; the returned config supplies runtime settings. A local child config requires a string model ID. Put build settings such as `build.externalDependencies` on the root agent, because build and Workflow world settings can't be chosen at runtime.
|
|
114
117
|
|
|
115
|
-
|
|
118
|
+
A single-file remote subagent returns `defineRemoteAgent(...)` or `null`. Compute the URL string in the function. Credentials can use memo results, and later requests to the same child rebuild them from the session as it was when the child opened. See [Dynamic remote agents](./remote-agents#dynamic-remote-agents) for the rebuild rules.
|
|
116
119
|
|
|
117
|
-
|
|
120
|
+
Hiding a subagent doesn't authorize anything: sensitive child tools still need authorization and approval checks.
|
|
118
121
|
|
|
119
122
|
## Dynamic connections
|
|
120
123
|
|
|
@@ -145,47 +148,47 @@ export default defineDynamic(async (ctx) => {
|
|
|
145
148
|
});
|
|
146
149
|
```
|
|
147
150
|
|
|
148
|
-
The memo saves account metadata, not tokens
|
|
151
|
+
The memo saves account metadata, not tokens; auth and header callbacks run when needed. Set `instanceKey` to a stable, non-secret account identifier, and change it when the endpoint, account, or auth provider changes. eve rejects a waiting sign-in callback if its connection's name, URL, or `instanceKey` changed.
|
|
149
152
|
|
|
150
|
-
|
|
153
|
+
Dynamic connections take the same filtering, provided arguments, and approval options as static [MCP](../connections/mcp) and [OpenAPI](../connections/openapi) connections. Each run refreshes connection callbacks and may replace clients, so don't rely on a dynamic MCP protocol session surviving between model calls. Models discover connection tools through `eve__search` and call them through `eve__tool`.
|
|
151
154
|
|
|
152
155
|
## Dynamic tools
|
|
153
156
|
|
|
154
|
-
Return a single `defineTool(...)`, a map of tools, or `null`. Executors receive the same `ToolContext` as static
|
|
157
|
+
Return a single `defineTool(...)`, a map of tools, or `null`. Executors receive the same `ToolContext` as static tools, including `ctx.getToken` and `ctx.requireAuth`. Validators, including refinements and transformations, and an `endsTurn` function run as they do on a static tool.
|
|
155
158
|
|
|
156
159
|
### Author replayable callbacks
|
|
157
160
|
|
|
158
|
-
Build callbacks and schemas with ordinary code. Save observations in memos when a fresh process must rebuild from the same data
|
|
161
|
+
Build callbacks and schemas with ordinary code. Save observations in memos when a fresh process must rebuild from the same data, because values fetched outside a memo are fetched again. Avoid `Math.random()` and `Date.now()` in declarations unless memoized; use `ctx.now` for commit time.
|
|
159
162
|
|
|
160
163
|
### Create dynamic tools in a package
|
|
161
164
|
|
|
162
|
-
Packages can return ordinary `defineTool` values, including callbacks made by factories.
|
|
165
|
+
Packages can return ordinary `defineTool` values, including callbacks made by factories. Prefer an [extension](../extensions) when distributing a namespaced collection of capabilities.
|
|
163
166
|
|
|
164
167
|
### Identity and redeploys
|
|
165
168
|
|
|
166
|
-
A fresh process rebuilds tools
|
|
169
|
+
A fresh process rebuilds tools from their definitions and saved memo results. A deployment change discards the results and runs the new code. Approved work runs before the functions run for the next model call. Check authorization inside execution when a check must also stop already-approved work.
|
|
167
170
|
|
|
168
|
-
A call waiting for approval or sign-in runs only if its dynamic tool,
|
|
171
|
+
A call waiting for approval or sign-in runs only if its dynamic tool, connection, or subagent is unchanged. eve compares what the model was offered, a connection's target, or a subagent's selection, plus the memo results its definition used. If any changed, the call returns a tool error saying the tool changed since it was offered, and the model can request it again.
|
|
169
172
|
|
|
170
173
|
### Naming
|
|
171
174
|
|
|
172
175
|
A single tool takes the file's slug. A map uses bare keys, with no automatic file prefix: `agent/tools/tenant.ts` returning `{ query, export }` exposes `query` and `export`.
|
|
173
176
|
|
|
174
|
-
Names use ASCII letters, digits, underscores, and dashes, start with a letter, and contain at most 64 characters. `eve` and the `eve__` prefix are reserved. A connection
|
|
177
|
+
Names use ASCII letters, digits, underscores, and dashes, start with a letter, and contain at most 64 characters. `eve` and the `eve__` prefix are reserved. A connection reserves its name and its `<name>__` prefix, so tools cannot take those names.
|
|
175
178
|
|
|
176
179
|
### Conflicts
|
|
177
180
|
|
|
178
|
-
|
|
181
|
+
A dynamic tool, connection, or skill overrides a static one of the same kind and name. Two dynamic connection definitions can't emit the same name. For tools and skills, the earlier definition keeps a duplicate name and eve logs an error for the other. Dynamic tools can't take workflow-tool or subagent names. Other invalid results and name conflicts fail the turn.
|
|
179
182
|
|
|
180
183
|
<span id="events"></span>
|
|
181
184
|
|
|
182
185
|
### Steering and sign-in
|
|
183
186
|
|
|
184
|
-
|
|
187
|
+
Because eve runs dynamic functions before every model call, they see a steering message or completed sign-in without a new turn. A turn-keyed memo stays fixed until the next turn.
|
|
185
188
|
|
|
186
189
|
### Execution order
|
|
187
190
|
|
|
188
|
-
Hooks finish first, then model selection, then connections, subagents, tools, skills, and instructions.
|
|
191
|
+
Hooks finish first, then model selection, then connections, subagents, tools, skills, and instructions. Don't depend on the order in which files run; each definition computes its own value.
|
|
189
192
|
|
|
190
193
|
A tool with `deferred: true` stays out of the model's tool list. It is found with `eve__search` and called with `eve__tool`, like a [static deferred tool](../tools#keep-a-tool-out-of-the-tool-list).
|
|
191
194
|
|
|
@@ -204,20 +207,18 @@ export default defineDynamic((ctx) => {
|
|
|
204
207
|
});
|
|
205
208
|
```
|
|
206
209
|
|
|
207
|
-
A skill with only `content`
|
|
210
|
+
A skill with only `content` doesn't start a sandbox. A skill with files installs its package in the sandbox, and a changed package replaces the earlier files:
|
|
208
211
|
|
|
209
|
-
-
|
|
210
|
-
- If the
|
|
211
|
-
- When the session detects
|
|
212
|
-
- Omitting `files` from a skill that
|
|
213
|
-
|
|
214
|
-
Keep caller-specific instructions in `content`, or withdraw the skill when the caller should no longer have its files.
|
|
212
|
+
- The model call doesn't wait for the install. A tool or hook that uses the sandbox waits for it.
|
|
213
|
+
- If the install fails twice in a row, eve logs a warning and retries on the next model call.
|
|
214
|
+
- When the session detects a recreated sandbox, the next run reinstalls the package. A replacement made by a subagent or workflow step sharing the sandbox may go undetected, and then the files aren't rewritten until the package changes.
|
|
215
|
+
- Omitting `files` from a skill that stays available keeps its installed files; withdraw the skill to remove them.
|
|
215
216
|
|
|
216
217
|
`deferred: true` keeps a skill out of the announcement, while leaving it discoverable through `eve__search` and loadable with `eve__skill`.
|
|
217
218
|
|
|
218
219
|
## Dynamic instructions
|
|
219
220
|
|
|
220
|
-
Return `defineInstructions({ content, role? })` or `null`. System instructions apply while
|
|
221
|
+
Return `defineInstructions({ content, role? })` or `null`. System instructions apply while the function returns them and stay outside history. User instructions join the conversation history only when their content changes:
|
|
221
222
|
|
|
222
223
|
```ts title="agent/instructions/brief.ts"
|
|
223
224
|
import { defineDynamic, defineInstructions } from "eve/instructions";
|
|
@@ -230,15 +231,13 @@ export default defineDynamic(async (ctx) => {
|
|
|
230
231
|
});
|
|
231
232
|
```
|
|
232
233
|
|
|
233
|
-
Before a turn's first model call, new user content joins just before the turn's input
|
|
234
|
+
Before a turn's first model call, new user content joins just before the turn's input; mid-turn changes append at the current position. Returning `null` adds nothing and resets content tracking, so returning the earlier content later adds it again, but it doesn't remove earlier history. Clear, compaction, and deployment changes don't re-append unchanged content.
|
|
234
235
|
|
|
235
236
|
## Errors and recovery
|
|
236
237
|
|
|
237
|
-
An unhandled error in a dynamic function or memo fails the turn with `REACTION_FAILED`. Catch optional work
|
|
238
|
-
|
|
239
|
-
With `EVE_LOG_LEVEL=debug`, eve logs each memo run with its file, the key's digest, the reason (`new key` or `deployment change`), and its duration. Logs never include the key itself. The digest is an unsalted hash, not a secret: someone who can guess a key, such as a tenant ID, can confirm it against the digest. Each evaluation also logs whether its value changed.
|
|
238
|
+
An unhandled error in a dynamic function or memo fails the turn with `REACTION_FAILED`. Catch optional work and return `null` when it should contribute nothing. A catch around `await ctx.memo(...)` leaves the failure uncached, so a later run tries it again. A catch inside the memo that returns `null` caches that `null` for the key's lifetime. A failed turn's input is not replayed.
|
|
240
239
|
|
|
241
|
-
|
|
240
|
+
With `EVE_LOG_LEVEL=debug`, eve logs each memo run with its file, key digest, reason (`new key` or `deployment change`), and duration, and whether each run's value changed. Logs never include the key. The digest is an unsalted hash, so someone who can guess a key, such as a tenant ID, can confirm it against the digest.
|
|
242
241
|
|
|
243
242
|
## What to read next
|
|
244
243
|
|
|
@@ -276,7 +276,7 @@ Then:
|
|
|
276
276
|
3. **Load on the server.** Read the saved chat in a Server Component, and pass `events` and `session` to the Client Component as `initialEvents` and `initialSession`, with `resume: true`. Saved messages show at once, and the live reply picks up from there.
|
|
277
277
|
4. **Store `session` as eve gives it to you.** Don't compute the cursor from the number of events.
|
|
278
278
|
|
|
279
|
-
See [Resume a saved session](./use-eve-agent#resume-a-saved-session) for
|
|
279
|
+
See [Resume a saved session](./use-eve-agent#resume-a-saved-session) for how saved events and catch-up fit together.
|
|
280
280
|
|
|
281
281
|
## Call the agent from server code
|
|
282
282
|
|
|
@@ -375,7 +375,7 @@ With several agents, a root `eve build` doesn't build them for `next start`. Run
|
|
|
375
375
|
|
|
376
376
|
### Self-host
|
|
377
377
|
|
|
378
|
-
- **Vercel services:** run the app and each agent with your own process manager and proxy. See [Self-host eve](../deployment/self-
|
|
378
|
+
- **Vercel services:** run the app and each agent with your own process manager and proxy. See [Self-host eve](../deployment/self-hosted-operations#run-workspace-members).
|
|
379
379
|
- **Next.js hosting:** `next start` runs the agent for you. To run the agent yourself instead, put it behind a proxy that serves it under the private path `/_eve_internal/eve` (the `servicePrefix` option), then set `EVE_NEXT_PRODUCTION_ORIGIN` to that proxy's address when you build and start Next.js.
|
|
380
380
|
|
|
381
381
|
## Troubleshooting
|
|
@@ -3,7 +3,7 @@ title: "Nuxt"
|
|
|
3
3
|
description: "Run an eve agent and a Nuxt app as one project with the eve/nuxt module."
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
The `eve/nuxt` module runs a Nuxt frontend and an eve agent as
|
|
6
|
+
The `eve/nuxt` module runs a Nuxt frontend and an eve agent as one project, with one dev server and one Vercel deploy. The auto-imported [`useEveAgent`](./use-eve-agent-vue) composable finds the mounted routes on its own, so you configure no CORS or URL env vars.
|
|
7
7
|
|
|
8
8
|
## Prerequisites
|
|
9
9
|
|
|
@@ -80,12 +80,12 @@ async function handleSubmit() {
|
|
|
80
80
|
</template>
|
|
81
81
|
```
|
|
82
82
|
|
|
83
|
-
The browser still needs a production authentication policy. See [Authenticate browser requests](./overview#authenticate-browser-requests) for the default
|
|
83
|
+
The browser still needs a production authentication policy. See [Authenticate browser requests](./overview#authenticate-browser-requests) for the default policy, which rejects unverified requests, and for channel configuration.
|
|
84
84
|
|
|
85
85
|
## Dev vs deploy topology
|
|
86
86
|
|
|
87
|
-
- **Local dev.** `npm run dev` starts the eve dev server next to `nuxt dev` and proxies the eve routes
|
|
88
|
-
- **Vercel.** The web app and the eve runtime deploy as a single project. On Vercel builds the module adds
|
|
87
|
+
- **Local dev.** `npm run dev` starts the eve dev server next to `nuxt dev` and proxies the eve routes to it. The browser talks only to the Nuxt origin. Concurrent Nuxt processes for the same eve root share one eve dev server. Set `EVE_BASE_URL` to proxy to an eve dev server you already run instead.
|
|
88
|
+
- **Vercel.** The web app and the eve runtime deploy as a single project. On Vercel builds, the module adds an eve [service](https://vercel.com/docs/services) and routes `/eve/v1/**` to it before filesystem routing. The Nuxt app serves everything else, and no `vercel.json` is required. By default, the generated service runs the installed eve binary from the agent root, so the agent directory doesn't need its own `package.json`. When the agent needs its own build step, set `eveBuildCommand`:
|
|
89
89
|
|
|
90
90
|
```ts
|
|
91
91
|
export default defineNuxtConfig({
|
|
@@ -96,17 +96,17 @@ The browser still needs a production authentication policy. See [Authenticate br
|
|
|
96
96
|
});
|
|
97
97
|
```
|
|
98
98
|
|
|
99
|
-
- **Non-Vercel hosts.** The module
|
|
99
|
+
- **Non-Vercel hosts.** The module doesn't start eve in production; run the eve service yourself. `nuxt build` writes a proxy rule that sends `/eve/v1/**` to `EVE_NUXT_PRODUCTION_ORIGIN`, or to `http://127.0.0.1:4274` when that variable is unset. Override the local port with `EVE_NUXT_PRODUCTION_PORT`. Set these variables when you run `nuxt build`, because the destination is fixed in the build output:
|
|
100
100
|
|
|
101
101
|
```bash
|
|
102
102
|
EVE_NUXT_PRODUCTION_ORIGIN=https://agent.example.com npm run build
|
|
103
103
|
```
|
|
104
104
|
|
|
105
|
-
`eve build` and `nuxt build` both write `.output/`. When the agent lives in the Nuxt project root,
|
|
105
|
+
`eve build` and `nuxt build` both write `.output/`. When the agent lives in the Nuxt project root, the two outputs overwrite each other. Build and serve eve from a separate directory instead, and set `eveRoot` to it. See [Self-host eve](../deployment/self-hosting) for running the eve service.
|
|
106
106
|
|
|
107
107
|
## Managing vercel.json yourself
|
|
108
108
|
|
|
109
|
-
When `vercel.json` declares [`services`](https://vercel.com/docs/services), the module generates nothing and your configuration
|
|
109
|
+
When `vercel.json` declares [`services`](https://vercel.com/docs/services), the module generates nothing, and your configuration controls routing. It must include the eve service (`framework: "eve"`) and a rewrite that sends `/eve/v1/*` requests to it, or the module fails the build:
|
|
110
110
|
|
|
111
111
|
```json title="vercel.json"
|
|
112
112
|
{
|
|
@@ -118,12 +118,12 @@ When `vercel.json` declares [`services`](https://vercel.com/docs/services), the
|
|
|
118
118
|
}
|
|
119
119
|
```
|
|
120
120
|
|
|
121
|
-
###
|
|
121
|
+
### Remove `experimentalServices`
|
|
122
122
|
|
|
123
|
-
|
|
123
|
+
Vercel doesn't route the `experimentalServices` field in `vercel.json`: both services build, but every `/eve/v1/*` request returns `NOT_FOUND`. The module ignores the field and warns that `vercel.json defines experimentalServices`. Remove it in one of two ways:
|
|
124
124
|
|
|
125
|
-
- **Generated (default).** Delete `vercel.json` (or
|
|
126
|
-
- **Hand-maintained.** Replace `experimentalServices` with the
|
|
125
|
+
- **Generated (default).** Delete `vercel.json` (or its `experimentalServices` block) and set the project's Framework Preset to Nuxt.js. The module generates the eve service and its routing on every Vercel build.
|
|
126
|
+
- **Hand-maintained.** Replace `experimentalServices` with the `services` and `rewrites` shown above, and keep the "Services" Framework Preset.
|
|
127
127
|
|
|
128
128
|
## What to read next
|
|
129
129
|
|
|
@@ -144,7 +144,7 @@ return pendingRequests.map(({ interactionId, request }) => (
|
|
|
144
144
|
```
|
|
145
145
|
|
|
146
146
|
- For a free-text answer, send `{ interactionId, text }`.
|
|
147
|
-
- A prompt stays `open` until eve
|
|
147
|
+
- A prompt stays `open` until eve decides it, not when you submit an answer. If the answer is refused, the prompt stays answerable.
|
|
148
148
|
- To show how a prompt ended, read its `outcome`. Only `accepted` and `declined` mean a person decided; a prompt can also end because its turn was cancelled. See [Interactions](./use-eve-agent#interactions).
|
|
149
149
|
- A prompt about a tool call also appears on that call's `tool` part as `part.interaction`. Other prompts appear as `interaction` message parts.
|
|
150
150
|
|