eve 0.63.0 → 0.64.0

package/dist/src/shared/sandbox-session.d.ts

@@ -1,5 +1,5 @@
 import type { Experimental_SandboxSession as AiSdkSandbox } from "ai";
-import type { SandboxDeleteOptions } from "#shared/sandbox-backend.js";
+import type { SandboxDeleteOptions } from "#shared/sandbox-provider.js";
 import type { SandboxNetworkPolicy } from "#shared/sandbox-network-policy.js";
 /**
  * Options for running one command in a sandbox. Shape mirrors the AI
@@ -70,26 +70,14 @@ export interface SandboxRemovePathOptions {
  * The eight I/O methods (`run`, `spawn`, `readFile`, `readBinaryFile`,
  * `readTextFile`, `writeFile`, `writeBinaryFile`, `writeTextFile`) are
  * pulled directly from the AI SDK {@link AiSdkSandbox} type, so authored
- * code that targets either surface uses identical signatures. `id` and
- * `resolvePath` are eve-specific extensions that the runtime relies on
- * for caching and `/workspace` path anchoring.
+ * code that targets either surface uses identical signatures. `resolvePath`
+ * is an eve-specific extension for `/workspace` path anchoring.
  *
  * Relative paths resolve from `/workspace`, the live working directory
- * for every backend. Absolute paths pass through unchanged.
+ * for every provider. Absolute paths pass through unchanged.
  *
  */
 export interface SandboxSession extends Pick<AiSdkSandbox, "run" | "spawn" | "readFile" | "readBinaryFile" | "readTextFile" | "writeFile" | "writeBinaryFile" | "writeTextFile"> {
-    /**
-     * Stable identifier for the backend session this handle wraps.
-     *
-     * Persists across reconnects to the same logical session: two calls
-     * that resume the same underlying backend sandbox observe the same
-     * `id`. Template sessions constructed during bootstrap expose the
-     * template key; live sessions expose the session key assigned by the
-     * runtime. Useful as a cache key for per-session state that must
-     * outlive individual step executions.
-     */
-    readonly id: string;
     /**
      * Anchors a sandbox-relative path to `/workspace` and returns the
      * resulting absolute path.
@@ -98,21 +86,8 @@ export interface SandboxSession extends Pick<AiSdkSandbox, "run" | "spawn" | "re
      * The read and write methods already apply this internally.
      */
     resolvePath(path: string): string;
-    /**
-     * Applies a firewall network policy to this live sandbox at run time,
-     * for changing the policy *during* a turn (e.g. brokering a credential
-     * resolved mid-turn, or tightening egress after fetching data). A
-     * per-domain `transform` injects headers at the firewall so secrets
-     * never enter the sandbox process. The policy takes effect from the time
-     * the call resolves, so await it before the egress you want governed.
-     *
-     * When the policy is known at session start, prefer configuring it up
-     * front in the sandbox backend factory or `onSession`'s `use()`. The
-     * Docker backend honors only `"allow-all"` and `"deny-all"`;
-     * the just-bash backend rejects this call entirely (its network policy
-     * is fixed at sandbox creation and it runs no binaries to govern).
-     */
-    setNetworkPolicy(policy: SandboxNetworkPolicy): Promise<void>;
+    /** Applies a firewall policy when the selected provider supports mutable networking. */
+    setNetworkPolicy?(policy: SandboxNetworkPolicy): Promise<void>;
     /**
      * Removes one file or directory from the sandbox filesystem.
      *
@@ -127,37 +102,39 @@ export interface SandboxSession extends Pick<AiSdkSandbox, "run" | "spawn" | "re
  * Unlike the I/O-only session used during sandbox initialization, this handle
  * exposes provider-backed lifecycle operations.
  */
+export interface MutableNetworkSandboxSession extends SandboxSession {
+    /** Applies a firewall policy to the live sandbox. */
+    setNetworkPolicy(policy: SandboxNetworkPolicy): Promise<void>;
+}
+export type FixedNetworkSandboxSession = Omit<SandboxSession, "setNetworkPolicy">;
 export interface RuntimeSandboxSession extends SandboxSession {
-    /** Permanently deletes this sandbox and its disposable backend state. */
+    /** Permanently deletes this sandbox and its disposable provider state. */
     delete(options?: SandboxDeleteOptions): Promise<void>;
     /**
      * Stops the backing sandbox compute while preserving the durable session.
      * A later runtime callback reopens the session through its configured
-     * backend. Providers may also support resuming the same handle.
+     * provider. Providers may also support resuming the same handle.
      */
     stop(): Promise<void>;
 }
+export type RuntimeSandboxSessionFor<Session extends SandboxSession> = Session & Pick<RuntimeSandboxSession, "delete" | "stop">;
 /**
  * Internal sandbox session, used to construct the public {@link SandboxSession}.
  *
- * Backend implementers only need to provide byte-oriented file I/O and
+ * Provider implementations only need to provide byte-oriented file I/O and
  * a `spawn` primitive; the public surface (binary and text variants,
  * line-range slicing, encoding handling, the `run` wrapper) is built on
  * top of these primitives by `buildSandboxSession`.
  *
  * Each method's signature mirrors its public counterpart (and the AI
- * SDK {@link AiSdkSandbox} surface) so backends look symmetric with
+ * SDK {@link AiSdkSandbox} surface) so providers look symmetric with
  * what authored code sees. The `path` field on `readFile`/`writeFile`
  * here is the **already-resolved** path: the public-surface builder
  * calls `resolvePath` before delegating.
  */
 export interface InternalSandboxSession extends Pick<AiSdkSandbox, "spawn" | "readFile" | "writeFile"> {
-    /**
-     * Stable identifier surfaced on the public {@link SandboxSession}.
-     */
-    readonly id: string;
-    /** Removes an already-resolved path from the backend filesystem. */
+    /** Removes an already-resolved path from the provider filesystem. */
     removePath(options: SandboxRemovePathOptions): Promise<void>;
-    /** Translates a user-facing path to the backend's native path. */
+    /** Translates a user-facing path to the provider's native path. */
     resolvePath(path: string): string;
 }

package/dist/src/shared/sandbox-template-error.d.ts

@@ -0,0 +1,9 @@
+export declare class SandboxTemplateNotProvisionedError extends Error {
+    readonly providerName: string;
+    readonly templateKey: string;
+    constructor(input: {
+        readonly providerName: string;
+        readonly templateKey: string;
+    });
+    static is(error: unknown): error is SandboxTemplateNotProvisionedError;
+}

package/dist/src/shared/sandbox-template-error.js

@@ -0,0 +1 @@
+var SandboxTemplateNotProvisionedError=class SandboxTemplateNotProvisionedError extends Error{providerName;templateKey;constructor(e){super(`Sandbox template "${e.templateKey}" is not provisioned for provider "${e.providerName}". Run \`eve build\` before serving traffic.`),this.name=`SandboxTemplateNotProvisionedError`,this.providerName=e.providerName,this.templateKey=e.templateKey}static is(e){return e instanceof SandboxTemplateNotProvisionedError||typeof e==`object`&&!!e&&Reflect.get(e,`name`)===`SandboxTemplateNotProvisionedError`&&typeof Reflect.get(e,`providerName`)==`string`&&typeof Reflect.get(e,`templateKey`)==`string`}};export{SandboxTemplateNotProvisionedError};

package/dist/src/subagents/tool.d.ts

@@ -32,7 +32,7 @@ export interface SubagentSandboxGraph {
         readonly sandboxRegistry: {
             readonly sandbox: {
                 readonly definition: {
-                    readonly inheritsParent?: boolean;
+                    readonly kind: "independent" | "parent";
                 };
             } | null;
         };

package/dist/src/subagents/tool.js

@@ -1 +1 @@
-import{mintSubagentContinuationToken}from"#execution/session.js";import{formatSubagentInput,normalizeRequestedOutputSchema}from"#subagents/invocation.js";import{SUBAGENT_ADAPTER_KIND}from"#subagents/adapter-state.js";import{resolveRemainingSessionTokenLimits}from"#subagents/token-budget.js";function buildSubagentRunInput(e){let{action:t,auth:n,capabilities:r,channelMetadata:i,inheritedConversation:a,initiatorAuth:o,session:s,source:c}=e,l=mintSubagentContinuationToken(`${s.sessionId}:${t.callId}`),u=resolveRemainingSessionTokenLimits(s,e.fanoutSize),d=normalizeRequestedOutputSchema(t.input.outputSchema),f={callId:t.callId,parentContinuationToken:e.parent.continuationToken??s.continuationToken,parentSessionId:s.sessionId,subagentName:t.subagentName};e.taskId!==void 0&&(f.taskId=e.taskId),(e.graph?.nodesByNodeId.get(t.nodeId)?.sandboxRegistry.sandbox?.definition.inheritsParent===!0||e.selfAgent)&&(s.sandboxState!==void 0&&(f.parentSandboxState=s.sandboxState),f.sandboxSessionId=e.sandboxSessionId??s.sessionId);let p={adapter:{kind:SUBAGENT_ADAPTER_KIND,state:f},auth:n,capabilities:r,channelMetadata:i,inheritedConversation:a,continuationToken:l,initiatorAuth:o,input:{message:formatSubagentCallInputMessage({action:t,source:c}),outputSchema:d??c.outputSchema},limits:u,mode:`conversation`,conversationId:e.parent.conversationId,parent:e.parent.lineage,parentTraceContext:e.parent.traceContext,activityObserver:e.activityObserver};return e.taskId!==void 0&&(p.taskId=e.taskId),{childContinuationToken:l,runInput:p}}function formatSubagentCallInputMessage(e){let{message:t}=e.action.input;switch(e.source.type){case`local`:return formatSubagentInput({description:e.source.description,message:t,name:e.action.subagentName,type:`local`}).message;case`runtime`:return formatSubagentInput({message:t,name:e.action.subagentName,type:`runtime`}).message;default:return e.source}}export{buildSubagentRunInput};
+import{mintSubagentContinuationToken}from"#execution/session.js";import{formatSubagentInput,normalizeRequestedOutputSchema}from"#subagents/invocation.js";import{SUBAGENT_ADAPTER_KIND}from"#subagents/adapter-state.js";import{resolveRemainingSessionTokenLimits}from"#subagents/token-budget.js";function buildSubagentRunInput(e){let{action:t,auth:n,capabilities:r,channelMetadata:i,inheritedConversation:a,initiatorAuth:o,session:s,source:c}=e,l=mintSubagentContinuationToken(`${s.sessionId}:${t.callId}`),u=resolveRemainingSessionTokenLimits(s,e.fanoutSize),d=normalizeRequestedOutputSchema(t.input.outputSchema),f={callId:t.callId,parentContinuationToken:e.parent.continuationToken??s.continuationToken,parentSessionId:s.sessionId,subagentName:t.subagentName};e.taskId!==void 0&&(f.taskId=e.taskId),(e.graph?.nodesByNodeId.get(t.nodeId)?.sandboxRegistry.sandbox?.definition.kind===`parent`||e.selfAgent)&&(s.sandboxState!==void 0&&(f.parentSandboxState=s.sandboxState),f.sandboxSessionId=e.sandboxSessionId??s.sessionId);let p={adapter:{kind:SUBAGENT_ADAPTER_KIND,state:f},auth:n,capabilities:r,channelMetadata:i,inheritedConversation:a,continuationToken:l,initiatorAuth:o,input:{message:formatSubagentCallInputMessage({action:t,source:c}),outputSchema:d??c.outputSchema},limits:u,mode:`conversation`,conversationId:e.parent.conversationId,parent:e.parent.lineage,parentTraceContext:e.parent.traceContext,activityObserver:e.activityObserver};return e.taskId!==void 0&&(p.taskId=e.taskId),{childContinuationToken:l,runInput:p}}function formatSubagentCallInputMessage(e){let{message:t}=e.action.input;switch(e.source.type){case`local`:return formatSubagentInput({description:e.source.description,message:t,name:e.action.subagentName,type:`local`}).message;case`runtime`:return formatSubagentInput({message:t,name:e.action.subagentName,type:`runtime`}).message;default:return e.source}}export{buildSubagentRunInput};

package/dist/src/svelte/index.js

@@ -1,3 +1,3 @@
-import { n as defaultMessageReducer, t as useEveAgent } from "../chunks/use-eve-agent-CVWk5KKy.js";
+import { n as defaultMessageReducer, t as useEveAgent } from "../chunks/use-eve-agent-IIuxkn6y.js";
 
 export { defaultMessageReducer, useEveAgent };

package/dist/src/svelte/use-eve-agent.js

@@ -1,3 +1,3 @@
-import { t as useEveAgent } from "../chunks/use-eve-agent-CVWk5KKy.js";
+import { t as useEveAgent } from "../chunks/use-eve-agent-IIuxkn6y.js";
 
 export { useEveAgent };

package/dist/src/tasks/delivery-context.d.ts

@@ -1,8 +1,9 @@
-import type { DeliverHookPayload } from "#channel/types.js";
+import type { TaskDeliveryPolicy, DeliverHookPayload } from "#channel/types.js";
 import type { SessionStateMap, StepInput } from "#harness/types.js";
 export declare const TASK_DELIVERY_CONTEXT_LABEL = "[Task state]";
 export declare const TASK_DELIVERY_INITIATING_INSTRUCTION = "Background task reporting: launch acknowledgement\nThe latest [Task state] message is runtime-authored and lists background tasks accepted so far from the current turn. They continue independently after this turn.\n\nContinue carrying out the user's request, including starting any remaining background work. When no further tool calls are needed in this turn, send one brief user-facing acknowledgement that the background work has started. Do not wait for results or report results that are not available yet. End the turn after the acknowledgement.";
-export declare const TASK_DELIVERY_SETTLED_INSTRUCTION = "Background task reporting\nThis turn was triggered by background task activity. The accompanying [Task state] message is runtime-authored and lists overlapping background tasks in the same cohort, potentially started across different user turns, all settled, with every available terminal output. Do not reply with <eve-empty-delivery/>. Send one user-facing response that combines their useful results.";
+export declare const TASK_DELIVERY_SETTLED_INSTRUCTION = "Background task reporting\nFor this background-task update, the accompanying [Task state] message is runtime-authored and lists the settled tasks in this cohort and their available terminal outputs. Report their useful results together in one user-facing response without repeating results already reported. Do not reply with <eve-empty-delivery/>.";
+export declare const TASK_DELIVERY_AUTO_INSTRUCTION = "Background task reporting\nFor this background-task update, the accompanying [Task state] message is runtime-authored and lists the whole cohort, including pending tasks and every available terminal output. A received result has not necessarily been reported to the user. Report new results only when they are useful independently of unfinished work. When that work settles, combine its results with any previously withheld results. If there is nothing new and useful to report, reply with exactly <eve-empty-delivery/>. Do not repeat results already reported or send an acknowledgement just to say you are waiting.";
 type BackgroundTaskDelivery = DeliverHookPayload & {
     readonly taskDeliveryId: string;
 };
@@ -10,10 +11,11 @@ type BackgroundTaskDelivery = DeliverHookPayload & {
 export declare function getBackgroundTaskDelivery(input: unknown): BackgroundTaskDelivery | undefined;
 /** Marks a task-produced user message before the harness coalesces delivery results. */
 export declare function markBackgroundTaskStepInput(input: StepInput): StepInput;
-/** Groups overlapping tasks without changing the delivered task's activity root. */
+/** Projects the report group without changing the delivered task's activity root. */
 export declare function resolveTaskDeliveryContext(input: {
     readonly state: SessionStateMap | undefined;
-    readonly taskDeliveryId: string;
+    readonly taskDeliveryIds: readonly string[];
+    readonly taskDeliveryPolicy: TaskDeliveryPolicy;
 }): {
     readonly context: string;
     readonly phase: "pending" | "settled";

package/dist/src/tasks/delivery-context.js

@@ -1,4 +1,4 @@
 import{markFrameworkStepInput}from"#harness/messages.js";import{getBackgroundWorkflowToolRuns,readWorkflowTaskView}from"#harness/workflow-tool-runs.js";import{getTaskCohortId}from"#tasks/session-task-cohorts.js";import{EMPTY_DELIVERY_SENTINEL}from"#shared/empty-delivery.js";const TASK_DELIVERY_CONTEXT_LABEL=`[Task state]`,TASK_DELIVERY_INITIATING_INSTRUCTION=`Background task reporting: launch acknowledgement
 The latest ${TASK_DELIVERY_CONTEXT_LABEL} message is runtime-authored and lists background tasks accepted so far from the current turn. They continue independently after this turn.
 
-Continue carrying out the user's request, including starting any remaining background work. When no further tool calls are needed in this turn, send one brief user-facing acknowledgement that the background work has started. Do not wait for results or report results that are not available yet. End the turn after the acknowledgement.`,TASK_DELIVERY_SETTLED_INSTRUCTION=`Background task reporting\nThis turn was triggered by background task activity. The accompanying ${TASK_DELIVERY_CONTEXT_LABEL} message is runtime-authored and lists overlapping background tasks in the same cohort, potentially started across different user turns, all settled, with every available terminal output. Do not reply with ${EMPTY_DELIVERY_SENTINEL}. Send one user-facing response that combines their useful results.`;function getBackgroundTaskDelivery(e){if(typeof e!=`object`||!e)return;let t=e;return t.kind===`deliver`&&typeof t.taskDeliveryId==`string`?e:void 0}function markBackgroundTaskStepInput(e){return e.message===void 0?e:markFrameworkStepInput(e,`execution.background_task`)}function resolveTaskDeliveryContext(e){let t=getBackgroundWorkflowToolRuns(e.state),n=t.find(t=>e.taskDeliveryId.startsWith(`${t.task.taskId}:`));return n===void 0?void 0:{...projectTaskCohort(t.filter(e=>getTaskCohortId(e.task)===getTaskCohortId(n.task))),rootTurnId:n.origin.turnId}}function resolveInitiatingTaskContext(e){let t=getBackgroundWorkflowToolRuns(e.state).filter(t=>t.origin.turnId===e.turnId);if(t.some(e=>e.task.outcome===void 0))return{...projectTaskCohort(t),phase:`initiating`}}function projectTaskCohort(e){let t=e.every(e=>e.task.outcome!==void 0),n=e.map(e=>{let n=readWorkflowTaskView(e.task);return{name:e.task.metadata.name,output:t?n?.lastOutput:void 0,status:n?.status??`pending`,taskId:e.task.taskId}});return{context:`${TASK_DELIVERY_CONTEXT_LABEL}\n${JSON.stringify({tasks:n})}`,phase:t?`settled`:`pending`}}export{TASK_DELIVERY_CONTEXT_LABEL,TASK_DELIVERY_INITIATING_INSTRUCTION,TASK_DELIVERY_SETTLED_INSTRUCTION,getBackgroundTaskDelivery,markBackgroundTaskStepInput,resolveInitiatingTaskContext,resolveTaskDeliveryContext};
+Continue carrying out the user's request, including starting any remaining background work. When no further tool calls are needed in this turn, send one brief user-facing acknowledgement that the background work has started. Do not wait for results or report results that are not available yet. End the turn after the acknowledgement.`,TASK_DELIVERY_SETTLED_INSTRUCTION=`Background task reporting\nFor this background-task update, the accompanying ${TASK_DELIVERY_CONTEXT_LABEL} message is runtime-authored and lists the settled tasks in this cohort and their available terminal outputs. Report their useful results together in one user-facing response without repeating results already reported. Do not reply with ${EMPTY_DELIVERY_SENTINEL}.`,TASK_DELIVERY_AUTO_INSTRUCTION=`Background task reporting\nFor this background-task update, the accompanying ${TASK_DELIVERY_CONTEXT_LABEL} message is runtime-authored and lists the whole cohort, including pending tasks and every available terminal output. A received result has not necessarily been reported to the user. Report new results only when they are useful independently of unfinished work. When that work settles, combine its results with any previously withheld results. If there is nothing new and useful to report, reply with exactly ${EMPTY_DELIVERY_SENTINEL}. Do not repeat results already reported or send an acknowledgement just to say you are waiting.`;function getBackgroundTaskDelivery(e){if(typeof e!=`object`||!e)return;let t=e;return t.kind===`deliver`&&typeof t.taskDeliveryId==`string`?e:void 0}function markBackgroundTaskStepInput(e){return e.message===void 0?e:markFrameworkStepInput(e,`execution.background_task`)}function resolveTaskDeliveryContext(e){let t=e.taskDeliveryIds[0];if(t===void 0)return;let n=getBackgroundWorkflowToolRuns(e.state),r=n.find(e=>t.startsWith(`${e.task.taskId}:`));return r===void 0?void 0:{...projectTaskCohort(n.filter(e=>getTaskCohortId(e.task)===getTaskCohortId(r.task)),e.taskDeliveryPolicy===`auto`),rootTurnId:r.origin.turnId}}function resolveInitiatingTaskContext(e){let t=getBackgroundWorkflowToolRuns(e.state).filter(t=>t.origin.turnId===e.turnId);if(t.some(e=>e.task.outcome===void 0))return{...projectTaskCohort(t,!1),phase:`initiating`}}function projectTaskCohort(e,t){let n=e.every(e=>e.task.outcome!==void 0),r=e.map(e=>{let r=readWorkflowTaskView(e.task);return{name:e.task.metadata.name,output:n||t?r?.lastOutput:void 0,status:r?.status??`pending`,taskId:e.task.taskId}});return{context:`${TASK_DELIVERY_CONTEXT_LABEL}\n${JSON.stringify({tasks:r})}`,phase:n?`settled`:`pending`}}export{TASK_DELIVERY_AUTO_INSTRUCTION,TASK_DELIVERY_CONTEXT_LABEL,TASK_DELIVERY_INITIATING_INSTRUCTION,TASK_DELIVERY_SETTLED_INSTRUCTION,getBackgroundTaskDelivery,markBackgroundTaskStepInput,resolveInitiatingTaskContext,resolveTaskDeliveryContext};

package/dist/src/tasks/delivery-policy.d.ts

@@ -1,3 +1,4 @@
+import type { TaskDeliveryPolicy } from "#channel/types.js";
 export interface DeliveryPolicy {
     readonly allowsEmptyDelivery: boolean;
     readonly instruction?: string;
@@ -8,5 +9,6 @@ export declare function resolveDeliveryPolicy(input: {
     readonly isChild: boolean;
     readonly isFirstTurn: boolean;
     readonly hasScheduleProvenance: boolean;
+    readonly taskDeliveryPolicy: TaskDeliveryPolicy | undefined;
     readonly taskDeliveryPhase: "none" | "initiating" | "pending" | "settled" | undefined;
 }): DeliveryPolicy;

package/dist/src/tasks/delivery-policy.js

@@ -1 +1 @@
-import{TASK_DELIVERY_INITIATING_INSTRUCTION,TASK_DELIVERY_SETTLED_INSTRUCTION}from"#tasks/delivery-context.js";import{CONDITIONAL_DELIVERY_INSTRUCTION}from"#shared/empty-delivery.js";const POLICIES={conditional:{allowsEmptyDelivery:!0,instruction:CONDITIONAL_DELIVERY_INSTRUCTION},initiating:{allowsEmptyDelivery:!1,instruction:TASK_DELIVERY_INITIATING_INSTRUCTION},normal:{allowsEmptyDelivery:!1},pending:{allowsEmptyDelivery:!0},settled:{allowsEmptyDelivery:!1,instruction:TASK_DELIVERY_SETTLED_INSTRUCTION}};function resolveDeliveryPolicy(e){return e.hasOutputSchema||e.isChild?POLICIES.normal:e.taskDeliveryPhase===`pending`?POLICIES.pending:e.taskDeliveryPhase===`settled`?POLICIES.settled:e.isFirstTurn&&e.hasScheduleProvenance?POLICIES.conditional:e.taskDeliveryPhase===`initiating`?POLICIES.initiating:POLICIES.normal}export{resolveDeliveryPolicy};
+import{TASK_DELIVERY_AUTO_INSTRUCTION,TASK_DELIVERY_INITIATING_INSTRUCTION,TASK_DELIVERY_SETTLED_INSTRUCTION}from"#tasks/delivery-context.js";import{CONDITIONAL_DELIVERY_INSTRUCTION}from"#shared/empty-delivery.js";const POLICIES={auto:{allowsEmptyDelivery:!0,instruction:TASK_DELIVERY_AUTO_INSTRUCTION},conditional:{allowsEmptyDelivery:!0,instruction:CONDITIONAL_DELIVERY_INSTRUCTION},initiating:{allowsEmptyDelivery:!1,instruction:TASK_DELIVERY_INITIATING_INSTRUCTION},normal:{allowsEmptyDelivery:!1},pending:{allowsEmptyDelivery:!0},settled:{allowsEmptyDelivery:!1,instruction:TASK_DELIVERY_SETTLED_INSTRUCTION}};function resolveDeliveryPolicy(e){return e.hasOutputSchema||e.isChild?POLICIES.normal:e.taskDeliveryPolicy===`auto`&&(e.taskDeliveryPhase===`pending`||e.taskDeliveryPhase===`settled`)?POLICIES.auto:e.taskDeliveryPhase===`pending`?POLICIES.pending:e.taskDeliveryPhase===`settled`?POLICIES.settled:e.isFirstTurn&&e.hasScheduleProvenance?POLICIES.conditional:e.taskDeliveryPhase===`initiating`?POLICIES.initiating:POLICIES.normal}export{resolveDeliveryPolicy};

package/dist/src/tools/framework/agent-contract.js

@@ -1 +1 @@
-import{z}from"#compiled/zod/index.js";const AGENT_TOOL_NAME=`agent`,AGENT_TOOL_DESCRIPTION=["Delegate a focused subtask to a copy of yourself, or continue or steer a previous delegation with `agentId`.",`Use it to isolate complex work or split a large task into independent pieces.`,"Issue multiple `agent` calls in one response to run a small fixed set in parallel.","A new child has fresh history and state but shares your tools and sandbox, so include essential context in `message` and give parallel writers non-overlapping scopes."].join(` `),SUBAGENT_TOOL_INPUT_SCHEMA=z.strictObject({agentId:z.string().nullable().describe(`The id of an existing agent from the <agents> list or a task receipt. A message to a busy agent steers it: its previous task is cancelled and the updated work runs in the same child session. Omit this field (or pass null or an empty string) to start a new agent.`).optional(),message:z.string().describe(`The message to send to the subagent. Provide all context the subagent needs to complete the task; the subagent does not see the parent's history.`),outputSchema:z.looseObject({}).describe(`Only provide a non-empty JSON Schema when the caller explicitly requests structured output; otherwise omit this field. The subagent must match a provided schema, and that structured output becomes the tool result.`).optional()});export{AGENT_TOOL_DESCRIPTION,AGENT_TOOL_NAME,SUBAGENT_TOOL_INPUT_SCHEMA};
+import{z}from"#compiled/zod/index.js";const AGENT_TOOL_NAME=`agent`,AGENT_TOOL_DESCRIPTION=["Delegate a focused subtask to a copy of yourself, or continue or steer a previous delegation with `agentId`.",`Use it to isolate complex work or split a large task into independent pieces.`,"Issue multiple `agent` calls in one response to run a small fixed set in parallel.","A new child has fresh history and state but reuses your tools and sandbox, so include essential context in `message` and give parallel writers non-overlapping scopes."].join(` `),SUBAGENT_TOOL_INPUT_SCHEMA=z.strictObject({agentId:z.string().nullable().describe(`The id of an existing agent from the <agents> list or a task receipt. A message to a busy agent steers it: its previous task is cancelled and the updated work runs in the same child session. Omit this field (or pass null or an empty string) to start a new agent.`).optional(),message:z.string().describe(`The message to send to the subagent. Provide all context the subagent needs to complete the task; the subagent does not see the parent's history.`),outputSchema:z.looseObject({}).describe(`Only provide a non-empty JSON Schema when the caller explicitly requests structured output; otherwise omit this field. The subagent must match a provided schema, and that structured output becomes the tool result.`).optional()});export{AGENT_TOOL_DESCRIPTION,AGENT_TOOL_NAME,SUBAGENT_TOOL_INPUT_SCHEMA};

package/dist/src/vue/index.js

@@ -1,3 +1,3 @@
-import { n as defaultMessageReducer, t as useEveAgent } from "../chunks/use-eve-agent-C5-yqRuq.js";
+import { n as defaultMessageReducer, t as useEveAgent } from "../chunks/use-eve-agent-BdKlQF32.js";
 
 export { defaultMessageReducer, useEveAgent };

package/dist/src/vue/use-eve-agent.js

@@ -1,3 +1,3 @@
-import { t as useEveAgent } from "../chunks/use-eve-agent-C5-yqRuq.js";
+import { t as useEveAgent } from "../chunks/use-eve-agent-BdKlQF32.js";
 
 export { useEveAgent };

package/docs/README.md

@@ -12,32 +12,28 @@ Important naming note:
 
 ## Find the page for your task
 
-| To do this                                               | Read this                                                                                                                    |
-| -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
-| Organize agents, subagents, and browser application code | [Project Structure](./concepts/project-structure.mdx)                                                                        |
-| Create a project and run your first agent                | [Getting Started](./getting-started.mdx)                                                                                     |
-| Look up agent files and discovery rules                  | [Agent Files](./reference/agent-files.md)                                                                                    |
-| Set the model, reasoning, or other agent-wide config     | [Agents](./agent-config.md)                                                                                                  |
-| Choose an agent model automatically for each request     | [Automatic Model Selection](./guides/evaluate.md)                                                                            |
-| Change what the agent does and how it behaves            | [Instructions](./instructions.mdx)                                                                                           |
-| Give the agent a typed capability it can call            | [Tools](./tools/overview.mdx)                                                                                                |
-| Require approval, or ask the user something mid-turn     | [Human in the Loop](./tools/human-in-the-loop.md)                                                                            |
-| Call an external HTTP API or MCP server                  | [Connections](./connections/overview.mdx)                                                                                    |
-| Add a messaging surface (Slack, Discord, iMessage, …)    | [Channels](./channels/overview.mdx)                                                                                          |
-| Expose your own HTTP route as a conversation surface     | [Custom Channels](./channels/custom.mdx)                                                                                     |
-| Package a procedure the agent loads only when it applies | [Skills](./skills.mdx)                                                                                                       |
-| Carry state across turns, or shape what the model sees   | [State](./concepts/state.md), [Context Control](./concepts/context-control.md)                                               |
-| Run commands or untrusted code in isolation              | [Sandboxes](./sandbox.mdx)                                                                                                   |
-| Delegate work to a specialist child agent                | [Subagents](./subagents/index.mdx)                                                                                           |
-| Run work on a recurring schedule                         | [Schedules](./schedules.mdx)                                                                                                 |
-| Install an existing integration instead of writing one   | [Add Integrations](./install-integrations.mdx)                                                                               |
-| Link a Vercel project and deploy to production           | [Deploy to Vercel](./guides/deployment/vercel.mdx)                                                                           |
-| Self-host, or compare hosting strategies                 | [Deployment](./guides/deployment/overview.md)                                                                                |
-| Authorize routes, sessions, and per-user access          | [Authentication](./guides/auth-and-route-protection.md)                                                                      |
-| Add a browser application                                | [Next.js](./guides/frontend/nextjs.mdx), [Nuxt](./guides/frontend/nuxt.mdx), or [SvelteKit](./guides/frontend/sveltekit.mdx) |
-| Build a custom web UI, or stream a session to a client   | [Client SDK](./guides/client/overview.mdx), [Frontend](./guides/frontend/overview.mdx)                                       |
-| Test the agent's behavior                                | [Evals](./evals/overview.mdx)                                                                                                |
-| Look up a CLI command or an exported type                | [CLI](./reference/cli.md), [TypeScript API](./reference/typescript-api.md)                                                   |
+| To do this                                               | Read this                                                                              |
+| -------------------------------------------------------- | -------------------------------------------------------------------------------------- |
+| Create a project, or understand the file layout          | [Getting Started](./getting-started.mdx)                                               |
+| Set the model, reasoning, or other agent-wide config     | [Agents](./agent-config.md)                                                            |
+| Change what the agent does and how it behaves            | [Instructions](./instructions.mdx)                                                     |
+| Give the agent a typed capability it can call            | [Tools](./tools/overview.mdx)                                                          |
+| Require approval, or ask the user something mid-turn     | [Human in the Loop](./tools/human-in-the-loop.md)                                      |
+| Call an external HTTP API or MCP server                  | [Connections](./connections/overview.mdx)                                              |
+| Add a messaging surface (Slack, Discord, iMessage, …)    | [Channels](./channels/overview.mdx)                                                    |
+| Expose your own HTTP route as a conversation surface     | [Custom Channels](./channels/custom.mdx)                                               |
+| Package a procedure the agent loads only when it applies | [Skills](./skills.mdx)                                                                 |
+| Carry state across turns, or shape what the model sees   | [State](./concepts/state.md), [Context Control](./concepts/context-control.md)         |
+| Run commands or untrusted code in isolation              | [Sandboxes](./sandbox/index.mdx)                                                       |
+| Delegate work to a specialist child agent                | [Subagents](./subagents/index.mdx)                                                     |
+| Run work on a recurring schedule                         | [Schedules](./schedules.mdx)                                                           |
+| Install an existing integration instead of writing one   | [Add Integrations](./install-integrations.mdx)                                         |
+| Link a Vercel project and deploy to production           | [Deploy to Vercel](./guides/deployment/vercel.mdx)                                     |
+| Self-host, or compare hosting strategies                 | [Deployment](./guides/deployment/overview.md)                                          |
+| Authorize routes, sessions, and per-user access          | [Authentication](./guides/auth-and-route-protection.md)                                |
+| Build a web UI, or stream a session to a client          | [Client SDK](./guides/client/overview.mdx), [Frontend](./guides/frontend/overview.mdx) |
+| Test the agent's behavior                                | [Evals](./evals/overview.mdx)                                                          |
+| Look up a CLI command or an exported type                | [CLI](./reference/cli.md), [TypeScript API](./reference/typescript-api.md)             |
 
 ## Legal and safeguards
 
@@ -58,25 +54,24 @@ Unless you configure stricter controls, eve agents may operate with permissive s
 For a full picture rather than a single task, read in this order:
 
 1. [Getting Started](./getting-started.mdx)
-2. [Project Structure](./concepts/project-structure.mdx)
-3. [Tutorial](./tutorial/first-agent.mdx)
-4. [Agents](./agent-config.md)
-5. [TypeScript API Reference](./reference/typescript-api.md)
-6. [Context Control](./concepts/context-control.md)
-7. [Skills](./skills.mdx)
-8. [Tools](./tools/overview.mdx)
-9. [Connections](./connections/overview.mdx)
-10. [Sandboxes](./sandbox.mdx)
-11. [Channels](./channels/overview.mdx)
-12. [Session Context](./guides/session-context.md)
-13. [Sessions and Streaming](./concepts/sessions-runs-and-streaming.md)
-14. [Client SDK](./guides/client/overview.mdx)
-15. [Subagents](./subagents/index.mdx)
-16. [Schedules](./schedules.mdx)
-17. [Evals](./evals/overview.mdx)
-18. [Authentication](./guides/auth-and-route-protection.md)
-19. [Deployment](./guides/deployment/overview.md)
-20. [CLI](./reference/cli.md)
+2. [Tutorial](./tutorial/first-agent.mdx)
+3. [Agents](./agent-config.md)
+4. [TypeScript API Reference](./reference/typescript-api.md)
+5. [Context Control](./concepts/context-control.md)
+6. [Skills](./skills.mdx)
+7. [Tools](./tools/overview.mdx)
+8. [Connections](./connections/overview.mdx)
+9. [Sandboxes](./sandbox/index.mdx)
+10. [Channels](./channels/overview.mdx)
+11. [Session Context](./guides/session-context.md)
+12. [Sessions and Streaming](./concepts/sessions-runs-and-streaming.md)
+13. [Client SDK](./guides/client/overview.mdx)
+14. [Subagents](./subagents/index.mdx)
+15. [Schedules](./schedules.mdx)
+16. [Evals](./evals/overview.mdx)
+17. [Authentication](./guides/auth-and-route-protection.md)
+18. [Deployment](./guides/deployment/overview.md)
+19. [CLI](./reference/cli.md)
 
 ## The public mental model
 

package/docs/agent-config.md

@@ -1,5 +1,5 @@
 ---
-title: "Agents"
+title: "Agent Configuration"
 description: "Configure an eve agent's model, reasoning effort, compaction, limits, and runtime behavior in agent.ts."
 ---
 
@@ -21,7 +21,7 @@ For a static AI Gateway model ID, you can make the same source change from the
 project root with `eve set --model anthropic/claude-opus-4.8` or from the local
 dev TUI with `/model anthropic/claude-opus-4.8`.
 
-The root `agent.ts` can be omitted when no runtime config is needed. eve then selects its default `agent.ts` source at the same slot, configured with `openai/gpt-5.6-luna-fast`; authoring the file replaces that source.
+The root `agent.ts` can be omitted when no runtime config is needed. eve then selects its default `agent.ts` source at the same slot, configured with `spacexai/grok-4.7`; authoring the file replaces that source.
 When `agent.ts` is present, `model` is required.
 
 A config that selects a static Gateway model is compile-only. A config that contains a dynamic model or a direct-provider `LanguageModel` remains a runtime entry because eve must resolve that authored value while the agent runs. See [Authored module lifecycle](./reference/typescript-api#authored-module-lifecycle).

package/docs/channels/eve.mdx

@@ -34,7 +34,7 @@ The default eve channel inspects the agent, creates sessions, accepts callbacks
 
 The session routes use only durable session IDs. Create a session explicitly, then put its returned ID in every follow-up, control, and stream path.
 
-`GET /eve/v1/health` is public and returns `{ ok: true, status: "ready", workflowId: string }`. `GET /eve/v1/info` uses the channel's auth policy and returns agent-info version 4. The TypeScript client validates both successful payloads: malformed health JSON throws `HealthResponseError`, malformed inspection JSON throws `AgentInfoResponseError`, and a non-success response from either route throws `ClientError`.
+`GET /eve/v1/health` is public and returns `{ ok: true, status: "ready", workflowId: string }`. `GET /eve/v1/info` uses the channel's auth policy and returns agent-info version 6. The TypeScript client validates both successful payloads: malformed health JSON throws `HealthResponseError`, malformed inspection JSON throws `AgentInfoResponseError`, and a non-success response from either route throws `ClientError`.
 
 ### Start and continue a session
 

package/docs/channels/overview.mdx

@@ -76,6 +76,54 @@ When eve doesn't ship a channel for your surface, build one with `defineChannel`
 
 A cross-channel `send(...)` supplies input to the agent and invokes the model on the destination channel. eve does not currently provide a direct cross-channel provider-message queue. To post without starting a turn, use the provider API. See [Durable cross-channel notifications](../patterns/durable-cross-channel-notifications) when delivery also needs application-managed retries and deduplication.
 
+## Background task results
+
+Pass `taskDeliveryPolicy` to `send(...)` to choose how the session reports background results:
+
+- `"auto"` (default for new channel sessions): ready results can invoke the parent while other tasks continue. The parent reports results that are useful independently and stays silent when a useful answer needs unfinished work.
+- `"cohort"`: wait for overlapping tasks to settle, then deliver their terminal outcomes together.
+
+```ts title="agent/channels/reports.ts"
+import { defineChannel, POST } from "eve/channels";
+import { localDev, routeAuth } from "eve/channels/auth";
+
+export default defineChannel({
+  routes: [
+    POST("/reports", async (request, { from }) => {
+      const auth = await routeAuth(request, localDev());
+      if (auth instanceof Response) return auth;
+      const session = await from("daily-report").send("Prepare the daily reports.", {
+        auth,
+        taskDeliveryPolicy: "cohort",
+      });
+      return Response.json({ sessionId: session.id });
+    }),
+  ],
+});
+```
+
+The option is available on channel-local `from(...).send(...)`, cross-channel
+`to(...).send(...)`, fixed-session `send(...)`, Chat SDK `bridge.send(...)`, and client
+sends. An explicit value
+updates the session's policy, including pending background tasks; later sends that
+omit it preserve that policy. A cross-channel send carries its setting through the
+receiver's `from(...).send(...)` unless that call supplies an explicit value.
+
+[Schedules](../schedules#background-task-results) default new sessions to `"cohort"`.
+A schedule handler can pass `taskDeliveryPolicy: "auto"` to `send(...)` to override
+that default. Child sessions use their own policy.
+
+With `"auto"`, a model call may finish without a user-visible message. Results
+already queued from the same cohort may share a turn. Each reporting turn receives
+the whole cohort, including pending tasks and available outputs, so previously
+withheld results remain available for a later combined report.
+
+Input requests and explicit task messages remain eligible for delivery under
+either policy. Failure and cancellation update task state immediately; their
+automatic reports follow the selected policy. User messages follow `turnPolicy`.
+See [Completion batching](../subagents#completion-batching) for cohort membership
+and result ordering.
+
 ## Relationship to the Chat SDK
 
 eve uses the [Chat SDK's card-builder components](https://chat-sdk.dev/docs/api/cards) (Cards, Buttons, Actions, etc.) for composing rich Slack messages. When you build a card with the [Slack channel](./slack), the underlying primitives come from the Chat SDK and get converted to Slack Block Kit at post time.

package/docs/concepts/execution-model-and-durability.mdx

@@ -56,7 +56,7 @@ that has not reached its next turn dispatch has not migrated yet.
 Transparent rollback to the former execution model is unsupported. Retire and
 restart affected sessions before rolling back.
 
-Nitro hosts the HTTP routes and workflow entrypoints. It does not supply the workflow state store or the sandbox runtime. Those are separate adapters: Workflow uses the active world implementation, and Sandbox uses the backend from `agent/sandbox` or `defaultBackend()`.
+Nitro hosts the HTTP routes and workflow entrypoints. It does not supply the workflow state store or the sandbox runtime. Those are separate adapters: Workflow uses the active world implementation, and Sandbox uses the backend from `agent/sandbox` or the default sandbox environment.
 
 For advanced self-hosted deployments, the root `agent.ts` can select the installed Workflow world package to use with `experimental.workflow.world`:
 

package/docs/concepts/sessions-runs-and-streaming.md

@@ -214,7 +214,7 @@ With one question-only batch, an exact option match or permitted freeform respon
 
 A structured response matches any currently pending request by ID, not only the newest batch. It becomes stale only after that request was answered, cleared, or cancelled. eve delivers a stale response to the model as a new user message, and the model decides whether the old selection still matters. A stale approval never authorizes the earlier tool call; the model must request the action and approval again if they are still needed.
 
-One delivery can answer requests from several batches. eve resumes approval-bearing batches in durable order and carries later answers forward until each batch can resume.
+One delivery can answer requests from several batches. eve resumes approval-bearing batches in durable order and carries later answers forward until each batch can resume. If you answer only some approvals in a batch, eve saves those responses until the remaining approvals are answered. Meanwhile, unrelated messages can run tools and receive a completed reply. The saved partial responses neither block that reply nor trigger another model call after it.
 
 Multiple steering messages retain their durable arrival order and may be folded into one input at the next boundary. A message accepted after turn settlement starts the next turn. See [message delivery and steering](./execution-model-and-durability#message-delivery-and-steering).
 
@@ -301,7 +301,7 @@ Start with the [Client SDK](../guides/client/overview) guide. It covers basic us
 
 ## Inspect the agent over HTTP
 
-`GET /eve/v1/info` returns agent-info version 4, a JSON inspection snapshot of the effective compiled agent. It reports the selected config; active tools, instructions, memory slots, skills, channels, schedules, sandbox, connections, hooks, and instrumentation with explicit source ownership; dynamic resolvers separately from their session-specific output; local and remote agents in separate collections; prepared built-in effects; and shadowed or disabled source diagnostics. Memory tool wrappers include their selected memory-source dependency. Channel routes appear in the same effective order used by the HTTP host. Static instructions remain an ordered array whose entries expose `content` and `role`.
+`GET /eve/v1/info` returns agent-info version 6, a JSON inspection snapshot of the effective compiled agent. It reports the selected config; active tools, instructions, memory slots, skills, channels, schedules, sandbox, connections, hooks, and instrumentation with explicit source ownership; dynamic resolvers separately from their session-specific output; local and remote agents in separate collections; prepared built-in effects; and shadowed or disabled source diagnostics. Memory tool wrappers include their selected memory-source dependency. Channel routes appear in the same effective order used by the HTTP host. Static instructions remain an ordered array whose entries expose `content` and `role`. Sandbox inspection exposes the opaque `revisionHash` that identifies its compiler-discovered environment inputs.
 
 The info route belongs to the selected `channels/eve.ts` source and uses its resolved auth policy. Without an authored replacement, eve selects the default channel source with Vercel OIDC, local development access, and the production placeholder. Replacing or disabling that source replaces or removes the info route too; no native fallback serves it.
 
@@ -309,7 +309,7 @@ The info route belongs to the selected `channels/eve.ts` source and uses its res
 curl http://127.0.0.1:2000/eve/v1/info
 ```
 
-With the default auth chain (`[vercelOidc(), localDev(), placeholderAuth()]`), a Vercel OIDC bearer takes precedence, an `eve dev` or `vercel dev` server authenticates local requests, and everything else is rejected. A deployed Vercel target requires a valid OIDC bearer, with a same-project bypass for in-deployment callers. See [auth & route protection](../guides/auth-and-route-protection).
+With the default auth chain (`[vercelOidc(), localDev(), placeholderAuth()]`), a Vercel OIDC bearer takes precedence, `localDev()` accepts requests to an `eve dev` or `vercel dev` server, and everything else is rejected. A deployed Vercel target requires a valid OIDC bearer, with a same-project bypass for in-deployment callers. See [auth & route protection](../guides/auth-and-route-protection).
 
 ## Dispatch order
 

package/docs/dynamic-configuration/meta.json

@@ -0,0 +1,5 @@
+{
+  "title": "Dynamic Capabilities",
+  "defaultOpen": false,
+  "pages": ["../guides/dynamic-capabilities", "../guides/evaluate"]
+}

package/docs/evals/overview.mdx

@@ -58,6 +58,49 @@ export default defineEvalConfig({
 
 Everything is optional. `judge` sets the default model for [LLM-as-judge](./judge) assertions (`t.judge(...)`); omit it to use the default evaluator, `typesafe-ai/jev`. Deterministic evals make no judge requests. `reporters`, `maxConcurrency`, and `timeoutMs` round out the defaults. Config `reporters` observe every eval in the run, so set one `Braintrust()` here instead of adding it to each eval. CLI flags (`--max-concurrency`, `--timeout`) and per-eval values take precedence over the config defaults.
 
+### Run setup and teardown
+
+Use `setup` to start shared resources or run migrations before eve starts the local agent server. Return shared context directly from `setup`, then release resources in `teardown`:
+
+```ts title="evals/evals.config.ts"
+import { defineEvalConfig } from "eve/evals";
+import { startTestDatabase } from "./database.js";
+
+export default defineEvalConfig({
+  async setup() {
+    const database = await startTestDatabase();
+    return { database };
+  },
+  async teardown(context) {
+    await context?.database.close();
+  },
+});
+```
+
+`context` is inferred from the setup return value. To use that type in an eval file, pass the config's type to `defineEval`:
+
+```ts title="evals/database.eval.ts"
+import { defineEval } from "eve/evals";
+import { equals } from "eve/evals/expect";
+import type config from "./evals.config.js";
+
+export default defineEval<typeof config>({
+  async test(t) {
+    const result = await t.context.database.query("SELECT 1 AS value");
+    await t.require(result.rows[0]?.value, equals(1));
+  },
+});
+```
+
+Setup, eval bodies, and teardown share the same context object in the runner process. Class instances and functions keep their identity; context is neither serialized nor sent to the agent server. Concurrent evals share these resources, so isolate any database records they modify.
+
+`setup` can also return nothing.
+
+- Setup runs once per `eve eval` invocation, after discovery and config loading, before target startup.
+- Teardown runs after the local server and its sandbox handles shut down, including after setup, startup, or eval failures. Cleanup failures fail the command.
+
+`teardown` receives `undefined` when setup returns no context or throws before returning. In that case, setup must clean up resources that only it can access. Teardown can also be used without setup. The per-eval `timeoutMs` does not apply to setup or teardown.
+
 ## Deterministic fixture models
 
 Use `mockModel` when an eval fixture needs to exercise eve's runtime without calling a model provider. A static fixture can be one line:

package/docs/getting-started.mdx

@@ -50,7 +50,7 @@ npx eve@latest init my-agent --model openai/gpt-5.6-terra --reasoning high
 
 ## Run the agent
 
-The terminal UI opens after interactive initialization. To return later, enter the project and run:
+The [terminal UI](/docs/guides/dev-tui) opens after interactive initialization. To return later, enter the project and run:
 
 ```bash
 cd my-agent

package/docs/guides/client/overview.mdx

@@ -34,7 +34,7 @@ The client requires the successful response to match `{ ok: true, status: "ready
 
 ## Inspect an agent
 
-Use `info()` to inspect an agent. The client requires the complete agent-info version 4 response before returning it:
+Use `info()` to inspect an agent. The client requires the complete agent-info version 6 response before returning it:
 
 ```ts
 const info = await client.info();

package/docs/guides/deployment/overview.md

@@ -3,7 +3,7 @@ title: "Overview"
 description: "Choose a deployment strategy and prepare an eve agent for production."
 ---
 
-Deploy eve to Vercel or run it as a Node service on your own infrastructure. Your deployment strategy determines the build output, workflow storage, sandbox backend, and routing. The agent’s filesystem-based configuration remains portable across these strategies.
+Deploy eve to Vercel or run it as a Node service on your own infrastructure. Your deployment strategy determines the build output, workflow storage, sandbox provider, and routing. The agent’s filesystem-based configuration remains portable across these strategies.
 
 ## Choose a deployment strategy