eve 0.54.0 → 0.54.3

package/docs/guides/instrumentation.md

@@ -48,13 +48,13 @@ Use the `setup` callback to register your OTel provider (for example `registerOT
 
 Any OTel-compatible backend works (Braintrust, PostHog, Sentry, Raindrop, Arize, Honeycomb, Datadog, Jaeger). Install the exporter package you need and configure it in the callback. The [PostHog AI Observability integration](/integrations/posthog-instrumentation) provides a ready-to-install exporter and optional user identification. The [Sentry integration](/integrations/sentry-instrumentation) provides a ready-to-install OTLP exporter that sends traces to Sentry without a Sentry SDK.
 
-Three more fields control what the AI SDK records inside those spans (see the AI SDK's [telemetry reference](https://ai-sdk.dev/docs/ai-sdk-core/telemetry)):
+Three more fields control what eve and the AI SDK record inside those spans (see the AI SDK's [telemetry reference](https://ai-sdk.dev/docs/ai-sdk-core/telemetry)):
 
-- `recordInputs` records full message history on each step span. It defaults to `false`; set it to `true` to include input content.
-- `recordOutputs` records model outputs on spans. It defaults to `false`; set it to `true` to include output content.
+- `recordInputs` records full message history on each step span and recalled records on memory spans. It defaults to `false`; set it to `true` to include input content.
+- `recordOutputs` records model outputs. It defaults to `false`; set it to `true` to include output content.
 - `functionId` overrides the function name on spans (defaults to the agent name).
 
-eve records metadata without model or tool inputs and outputs by default. Enable either content category only after reviewing the exporter and its data-retention path.
+eve records metadata without model, tool, or memory-record content by default. Enable either content category only after reviewing the exporter and its data-retention path.
 
 In the provider layout, eve stamps each span with `gen_ai.conversation.id`, which stays fixed across local and remote activations, including independent remote root workflows. Query this attribute to find the conversation's exported, retained traces; it does not grant access or control trace parenting. On Vercel, `vercel.session_id` additionally identifies the current Workflow run. See [Query exported traces](#query-exported-traces) for the cross-backend workflow.
 
@@ -103,19 +103,28 @@ not mark the active span as failed.
 The built-in OpenTelemetry provider preserves each span's OTel name and adds
 `operation.name` and `resource.name` for Datadog's operation/resource mapping:
 
-| OTel span name                                                          | `operation.name`  | `resource.name`        |
-| ----------------------------------------------------------------------- | ----------------- | ---------------------- |
-| `invoke_agent weather`                                                  | `invoke_agent`    | `invoke_agent weather` |
-| `execute_tool search`                                                   | `execute_tool`    | `execute_tool search`  |
-| `chat <model>`                                                          | `chat`            | `chat <model>`         |
-| `agent.step`, `agent.action`, `agent.approval`, `agent.channel.request` | Same as span name | Same as span name      |
+| OTel span name                                                          | `operation.name`  | `resource.name`          |
+| ----------------------------------------------------------------------- | ----------------- | ------------------------ |
+| `invoke_agent weather`                                                  | `invoke_agent`    | `invoke_agent weather`   |
+| `invoke_workflow deploy`                                                | `invoke_workflow` | `invoke_workflow deploy` |
+| `execute_tool search`                                                   | `execute_tool`    | `execute_tool search`    |
+| `chat <model>`                                                          | `chat`            | `chat <model>`           |
+| `search_memory`, `upsert_memory`                                        | Same as span name | Same as span name        |
+| `agent.step`, `agent.action`, `agent.approval`, `agent.channel.request` | Same as span name | Same as span name        |
 
-These attributes apply to eve-owned spans in local tracing and the
+These rows apply to eve-owned spans in local tracing and the
 [instrumentation provider layout](./instrumentation-providers). They do not
 rename Workflow, AI SDK, or other third-party spans, or change trace IDs,
-parenting, sampling, or session grouping. Legacy `instrumentation.ts` setup
-still owns its exporter configuration and [authored trace
-hierarchy](#authored-trace-hierarchy).
+parenting, or session grouping. Legacy `instrumentation.ts` setup still owns
+its exporter configuration and [authored trace hierarchy](#authored-trace-hierarchy).
+
+Workflow action spans enter the sampler as `agent.action`, with
+`gen_ai.operation.name` and `gen_ai.workflow.name` already present. After
+sampling, eve changes the exported span name to `invoke_workflow <tool>`.
+Existing name-based samplers therefore keep their `agent.action` behavior;
+attribute-based samplers can select GenAI workflow operations explicitly.
+Review custom attribute rules when upgrading because the new workflow
+attributes may change their decisions.
 
 In Datadog APM, `operation_name:invoke_agent resource_name:"invoke_agent weather"`
 selects named agent invocations. Operation-based dashboards and monitors may
@@ -137,25 +146,47 @@ that discard span events, including Sentry's [direct OTLP
 intake](https://docs.sentry.io/concepts/otlp/direct/traces/). These attributes
 remain available when model and tool content is redacted.
 
+## Memory spans
+
+eve records [OpenTelemetry GenAI memory spans](https://opentelemetry.io/docs/specs/semconv/gen-ai/gen-ai-spans/#memory) for provider calls. Recalls at `turn.started` and `compaction.completed` use `search_memory`; capture handlers use `upsert_memory`. They are client spans, following the GenAI memory convention for a call to a memory system.
+
+Every memory span includes `gen_ai.operation.name` and `gen_ai.memory.store.id`. The store ID is eve's opaque `memory.scope.key`, which identifies the resolved scope without exposing the namespace or scope values. Recall spans set `gen_ai.memory.record.count` to their result count.
+
+`gen_ai.memory.records` contains recalled record content only when `recordInputs` is enabled. eve classifies recalled records as input content because they become part of the model context. eve does not set `gen_ai.memory.query.text` because a memory provider receives structured conversation messages, not a standalone search-query string. The `agent.memory.slot` and `agent.memory.phase` attributes identify the eve slot and lifecycle boundary without adding either to the span name.
+
+Messages in `gen_ai.input.messages` include a `kind` for user-role entries.
+New human input uses `user`; framework-authored input uses namespaced kinds
+such as `context.instruction` and `execution.background_task`. When resuming
+history saved before eve 0.54, entries without a kind use `legacy.unknown`:
+the old format did not reliably distinguish human input from framework input.
+Their content and metadata remain unchanged, and already classified entries
+retain their kind. Unknown legacy entries are not replayed as the latest human
+request after compaction.
+
 ## Agent trace contract
 
 The provider layout and zero-config local tracing emit the following spans.
 The legacy `instrumentation.ts` layout still uses its authored OTel setup.
 
-| Span                    | Meaning                                                  |
-| ----------------------- | -------------------------------------------------------- |
-| `invoke_agent <agent>`  | One agent activation in its own trace                    |
-| `agent.step`            | One model attempt                                        |
-| `chat <model>`          | One model call beneath its step                          |
-| `agent.action`          | Durable action lifecycle, including dispatch and waiting |
-| `execute_tool <tool>`   | In-process tool execution beneath its action             |
-| `agent.approval`        | Approval waiting beneath its action                      |
-| `agent.channel.request` | Optional HTTP request span in the provider layout        |
+| Span                     | Meaning                                                  |
+| ------------------------ | -------------------------------------------------------- |
+| `invoke_agent <agent>`   | One agent activation in its own trace                    |
+| `agent.step`             | One model attempt                                        |
+| `chat <model>`           | One model call beneath its step                          |
+| `invoke_workflow <tool>` | One workflow tool run that coordinated a nested agent    |
+| `agent.action`           | Durable action lifecycle, including dispatch and waiting |
+| `execute_tool <tool>`    | In-process tool execution beneath its action             |
+| `agent.approval`         | Approval waiting beneath its action                      |
+| `search_memory`          | Recall memory records before a turn or after compaction  |
+| `upsert_memory`          | Automatic memory capture                                 |
+| `agent.channel.request`  | Optional HTTP request span in the provider layout        |
 
 For background tools and subagents, the AI SDK's `execute_tool` span ends when
 the model receives the task receipt. The enclosing `agent.action` span remains
-open until the background task completes, fails, or is cancelled. Its duration,
-outcome, and usage describe the background task rather than the receipt.
+open until the background task completes, fails, or is cancelled. When a
+workflow tool coordinates a nested `ctx.agent()` call, eve exports that span as
+`invoke_workflow` instead. Its duration, outcome, and usage describe the
+background task rather than the receipt.
 Background tool results follow the output-content policy. Recorded task failure
 details become bounded exception and status messages; redacted spans retain only
 the failure outcome, error status, and error type. The initiating turn can
@@ -163,10 +194,14 @@ finish or be cancelled while the action remains open. Ending the session closes
 an action whose task never reported a terminal result.
 
 Schema v4 removes the session-long `agent.session` root and duplicate agent session and lineage attributes. Every eve span carries `agent.trace.schema.version=4` and `gen_ai.conversation.id`; Vercel deployments additionally carry `vercel.session_id`.
-Only activations use the `invoke_agent` operation. Dispatch lifecycle spans use
-`agent.action` with `agent.invocation.role=caller`; the built-in `agent` tool
-executes under `execute_tool agent`. Turn IDs such as `turn_0` are local to a session,
-so correlate turns by session ID and turn ID together.
+Only activations use the `invoke_agent` operation. A workflow tool invocation
+that coordinates at least one nested agent uses `invoke_workflow`, with its
+path-derived tool name in `gen_ai.workflow.name`. Durable workflow tools without
+agent operations, including `sleep`, remain `agent.action` spans. Dispatch
+lifecycle spans use `agent.action` with
+`agent.invocation.role=caller`; the built-in `agent` tool executes under
+`execute_tool agent`. Turn IDs such as `turn_0` are local to a session, so
+correlate turns by session ID and turn ID together.
 
 A conversation remains durable state; `gen_ai.conversation.id` joins the activations that operate on it.
 
@@ -373,7 +408,7 @@ Without an `instrumentation.ts`, `eve dev` records spans to disk with one bounde
 - [`/traces`](dev-tui#logs-and-traces) in the dev TUI: a live trace viewer that replays captured content as a conversation.
 - [`eve traces`](../reference/cli#eve-traces): a span tree in the terminal, `eve traces ls` to list. Works after `eve dev` exits.
 
-Local traces omit model and tool inputs and outputs by default. Set `EVE_TRACES_CONTENT=on` in `.env.local` to capture that content.
+Local traces omit model, tool, and memory-record content by default. Set `EVE_TRACES_CONTENT=on` in `.env.local` to capture that content.
 
 Writing `instrumentation.ts` replaces this: your `setup` takes over and nothing is recorded locally. For span attributes, retention, and the `EVE_TRACES*` variables, see [`eve traces`](../reference/cli#eve-traces).
 

package/docs/reference/cli.md

@@ -310,13 +310,13 @@ Span rows carry inline metrics when the span recorded them — `↑input`/`↓ou
 
 Every subagent activation starts its own trace. The first child's `invoke_agent` root links to the dispatching caller with `eve.link.type=agent.dispatch`; remote agents carry that caller context over `traceparent`. Later turns also start fresh traces without repeating the initial caller link. All related sessions retain the same `gen_ai.conversation.id`, and `agent.subagent.name` labels the child invocation.
 
-Each `agent()` call inside an authored workflow has its own `agent.action` caller span, including sequential, parallel, and background calls. The workflow tool keeps its own `agent.action` and `execute_tool` spans. Only agent execution uses `invoke_agent`.
+Each `agent()` call inside an authored workflow has its own `agent.action` caller span, including sequential, parallel, and background calls. A workflow tool that coordinates one of those calls has an enclosing `invoke_workflow <tool>` span; a workflow tool without agent calls remains `agent.action`. The tool also keeps its `execute_tool <tool>` span. Only agent execution uses `invoke_agent`.
 
 A durable conversation produces one bounded trace per turn. Worker replacements reuse the prepared context for the same turn, while a later turn or an independently replayed attempt starts a fresh trace. Passing the conversation ID shows every trace it produced, oldest first.
 
 Every span carries a real duration. A turn's root `invoke_agent` span is written when the turn settles, so a running turn shows only its steps.
 
-Model and `execute_tool` spans omit their inputs and outputs by default. Set `EVE_TRACES_CONTENT=on` to capture system prompts, prompt messages, and response text for models, plus call arguments and results for tools. Each captured value is capped at 32 KB.
+Model, `execute_tool`, and memory spans omit their content by default. Set `EVE_TRACES_CONTENT=on` to capture system prompts, prompt messages, and response text for models; call arguments and results for tools; and recalled memory records. Each captured value is capped at 32 KB.
 
 Step spans carry token counts under `agent.usage.*`, and cost when Vercel AI Gateway served the call. Model spans also expose `gen_ai.usage.*` token counters. The CLI sums step-level counters only, so model and delegated-call totals are not counted twice.
 
@@ -324,13 +324,13 @@ Step spans carry token counts under `agent.usage.*`, and cost when Vercel AI Gat
 
 eve sweeps the store when an activation's writes finish, when a session finishes, and when the dev server starts. An open conversation does not pin every completed turn's trace. Sweeps evict oldest-first past the bounds below, except that active traces, the newest traces, and anything written in the last five minutes are kept. A sweep can therefore exceed the size budget. Set the bounds in `.env.local`, which `eve dev` loads automatically; each accepts `off` to disable it individually.
 
-| Variable                     | Default              | Effect                                                                              |
-| ---------------------------- | -------------------- | ----------------------------------------------------------------------------------- |
-| `EVE_TRACES`                 | on                   | `off` stops writing traces and stops sweeping                                       |
-| `EVE_TRACES_CONTENT`         | off                  | `on` captures model prompt/response and tool input/output attributes on local spans |
-| `EVE_TRACES_MAX_AGE_MS`      | `604800000` (7d)     | Age after which a trace may be evicted                                              |
-| `EVE_TRACES_MAX_TOTAL_BYTES` | `536870912` (512 MB) | Size budget for the whole store                                                     |
-| `EVE_TRACES_RETAIN_COUNT`    | `20`                 | Newest traces kept regardless of age or size                                        |
+| Variable                     | Default              | Effect                                                                                              |
+| ---------------------------- | -------------------- | --------------------------------------------------------------------------------------------------- |
+| `EVE_TRACES`                 | on                   | `off` stops writing traces and stops sweeping                                                       |
+| `EVE_TRACES_CONTENT`         | off                  | `on` captures model prompt/response, tool input/output, and memory-record attributes on local spans |
+| `EVE_TRACES_MAX_AGE_MS`      | `604800000` (7d)     | Age after which a trace may be evicted                                                              |
+| `EVE_TRACES_MAX_TOTAL_BYTES` | `536870912` (512 MB) | Size budget for the whole store                                                                     |
+| `EVE_TRACES_RETAIN_COUNT`    | `20`                 | Newest traces kept regardless of age or size                                                        |
 
 ## `eve link`
 

package/docs/reference/typescript-api.md

@@ -192,16 +192,20 @@ Sign in directly from eve; the Codex CLI is not required:
 2. Complete sign-in in the browser. If the browser does not open, use the URL printed in the terminal.
 3. Return to eve after the terminal confirms that your subscription is connected. Normal token expiry is refreshed automatically.
 
-eve stores this session in `~/.eve/auth/chatgpt.json` with owner-only file permissions on Unix. It is separate from any Codex login and is never written to your project. Keep this file private. To remove the local eve login, stop your eve processes and delete the file. Existing Codex users must sign in once through eve after upgrading.
+eve stores your refresh token and account details in your operating system's credential store through [just-secrets](https://github.com/vercel-labs/just-secrets): the login Keychain on macOS, Credential Manager on Windows, or Secret Service on Linux. Access tokens stay in process memory; a new eve process refreshes the saved session when it first needs a token. The login is separate from Codex and is never written to your project.
 
-Over SSH, or if localhost port 1455 is occupied, eve shows a device code instead. Open the displayed link in a browser and enter the code. Device sign-in requires enabling device code authorization in **ChatGPT Settings → Security**, or having a workspace admin enable it in workspace permissions. Sign-in times out after five minutes; press **Ctrl+C** to cancel sooner.
+If you previously signed in through Codex or used eve's `~/.eve/auth/chatgpt.json` file, sign in once through eve after upgrading. eve removes the old plaintext file after successfully saving the new session. It does not fall back to file storage if the OS credential store is unavailable.
+
+Linux, including WSL, requires `/usr/bin/secret-tool` (commonly provided by `libsecret-tools`), a session D-Bus, and an unlocked Secret Service keyring. On macOS, unlock your login keychain and allow credential access if prompted. On Windows, PowerShell and Credential Manager must be available in your user session. OS credential storage protects secrets at rest; it does not guarantee isolation from malicious processes running as your OS user.
+
+Over SSH, or if localhost port 1455 is occupied, eve shows a device code instead. Open the displayed link in a browser and enter the code. Device sign-in requires enabling device code authorization in **ChatGPT Settings → Security**, or having a workspace admin enable it in workspace permissions. Sign-in times out after five minutes; press **Ctrl+C** to cancel sooner. Device sign-in still requires an available OS credential store; use an API-key model in headless environments without one.
 
 ChatGPT subscription credentials are local user credentials. `eve deploy` blocks agents whose active model is `chatgpt()` because those credentials are not uploaded to a deployment. Use an environment branch with a deployable model, or switch to an AI Gateway model before deploying.
 
 Troubleshooting:
 
 - **`chatgpt-sub login`**: open `/model` and select **Provider** → **ChatGPT subscription** to sign in again. The running dev session picks up the new login.
-- **`chatgpt-sub unavailable`**: check your network connection and retry from `/model`. If eve reports an invalid credential file, remove `~/.eve/auth/chatgpt.json` and sign in again.
+- **`chatgpt-sub unavailable`**: follow the reported OS credential-store recovery steps, or check your network connection if token refresh failed. Retry from `/model`. If eve reports an invalid stored session, sign in again to replace it.
 - **Model rejected by the backend**: model availability depends on the signed-in ChatGPT account. Pick another supported OpenAI model.
 - **Device sign-in unavailable**: enable device code authorization in ChatGPT security settings, or sign in from a local terminal with port 1455 available.
 

package/docs/subagents/index.mdx

@@ -7,13 +7,18 @@ eve supports two ways to delegate work: the root-only built-in `agent` tool, whi
 
 ## Completion batching
 
-eve automatically combines adjacent successful completions already queued from
-tasks launched in the same parent turn. Every result is retained, and the parent
-responds to the batch in one turn. No configuration is required.
-
-There is no debounce timer or waiting for unfinished tasks. Failures, input
-requests, explicit updates, user messages, and different task cohorts remain
-separate delivery boundaries.
+Overlapping background work owned by a session forms a cohort. Tasks launched in
+later user turns join the open cohort while earlier work is still pending or its
+successful results await delivery. eve holds successful completion notifications
+until every task in that cohort has completed, failed, or been cancelled, then
+delivers the successful results together in one parent turn. Partial completions
+do not invoke the parent model. Work started after the cohort settles forms a new
+cohort. No configuration or debounce timer is required.
+
+User messages, input requests, authorization events, failures, and cancellation
+are handled without waiting for the cohort. Child lifecycle events are processed
+before completion delivery so usage accounting and handle cleanup stay ordered.
+To follow work in progress, subscribe to the child session streams.
 
 ## The built-in `agent` tool
 
@@ -27,7 +32,7 @@ The root session receives `agent` by default. The model calls it to delegate a t
 }
 ```
 
-The copy uses the root's instructions, connections, auth, and sandbox. It receives the same tools except for the root-only `agent` and `Workflow`, and starts with fresh conversation history and fresh state. Its file writes are immediately visible to the root. The built-in `agent` always runs in the background and needs no configuration: each call returns `{ status: "working", taskId, agentId }`, then task notifications wake the parent with updates or the final result. Give parallel children non-overlapping write scopes.
+The copy uses the root's instructions, connections, auth, and sandbox. It receives the same tools except for the root-only `agent` and `Workflow`, and starts with fresh conversation history and fresh state. Its file writes are immediately visible to the root. The built-in `agent` always runs in the background and needs no configuration: each call returns `{ status: "working", taskId, agentId }`, then task notifications wake the parent with completion, failure, or cancellation. Give parallel children non-overlapping write scopes.
 
 `agent` is intentionally root-only. Copies created by it cannot call `agent`, and declared subagents never receive the built-in tool. If a stale or forced recursive call reaches execution, eve rejects it instead of starting another child session.
 
@@ -56,12 +61,43 @@ export default defineAgent({
 });
 ```
 
-`description` is required. The parent reads it to decide whether to delegate, so the compiler rejects any subagent whose `agent.ts` leaves it out. Every declared local or remote subagent runs as a durable background task: the call returns `{ status: "working", taskId, agentId }` immediately, then task notifications wake the parent with updates, completion, failure, or cancellation. Human input requests surface separately on the parent session.
+`description` is required. The parent reads it to decide whether to delegate, so the compiler rejects any subagent whose `agent.ts` leaves it out. Every declared local or remote subagent runs as a durable background task: the call returns `{ status: "working", taskId, agentId }` immediately, then task notifications wake the parent with completion, failure, or cancellation. Human input requests surface separately on the parent session.
 
-A child running as a background task receives the framework `task_update` tool. It uses `task_update` to report progress to its parent. `task_cancel` is available to sessions that own background tasks, including a child that starts nested background work.
+`task_cancel` is available to sessions that own background tasks, including a child that starts nested background work.
 
 A mounted extension can also contribute declared subagents from `extension/subagents/`. The mount namespace prefixes the subagent visible to the consuming agent node: mounting an extension as `crm` exposes its `reviewer` subagent as `crm__reviewer`. The contributed subagent keeps its own isolated tools, connections, skills, hooks, instructions, sandbox, and nested subagents, and its modules can read configuration from the extension handle. See [Extensions](./extensions#add-a-subagent) for the authoring and override behavior.
 
+### Vercel workspace peers
+
+In a Vercel agent workspace, expose one other workspace member as a remote subagent with `defineWorkspaceAgent`. Create an ordinary file under the caller's `agent/subagents/` directory. Its filename gives the model-visible tool name; `name` identifies the peer under `agents/`.
+
+```ts title="agents/foreman/agent/subagents/research.ts"
+import { defineWorkspaceAgent } from "eve";
+
+export default defineWorkspaceAgent({
+  name: "research",
+});
+```
+
+The helper uses the peer's root `defineAgent({ description })` value as the model-visible tool description. Pass `description` to override it for this caller. When `transport` is omitted, eve selects the built-in transport for the runtime environment. Vercel deployments route through the current deployment and authenticate with the caller's Vercel OIDC token. Outside Vercel, provide an explicit transport with `url` and optional `auth` or `headers`:
+
+```ts title="agents/foreman/agent/subagents/research.ts"
+import { defineWorkspaceAgent } from "eve";
+import { bearer } from "eve/agents/auth";
+
+export default defineWorkspaceAgent({
+  name: "research",
+  transport: {
+    url: () => process.env.RESEARCH_AGENT_URL!,
+    auth: bearer(() => process.env.RESEARCH_AGENT_TOKEN!),
+  },
+});
+```
+
+An explicit transport replaces the environment default completely. The receiving peer must still accept the transport's credentials through its channel authentication policy. Set `forwardPrincipal: true` only when the peer trusts the caller to forward user identity, as described in [Remote agents](./guides/remote-agents#forward-the-callers-identity).
+
+Use the peer's directory name under `agents/`. eve requires an exact workspace-member match, so add another declared subagent file for each additional peer. `eve dev` does not provide local workspace routing; configure an explicit transport to target a separately running peer.
+
 ### Conditional availability
 
 To expose a declared subagent only for certain sessions or turns, export

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "eve",
-  "version": "0.54.0",
+  "version": "0.54.3",
   "private": false,
   "description": "Filesystem-first framework for durable backend AI agents that run anywhere.",
   "keywords": [
@@ -186,11 +186,6 @@
       "import": "./dist/src/public/tools/task-cancel.js",
       "default": "./dist/src/public/tools/task-cancel.js"
     },
-    "./tools/task_update": {
-      "types": "./dist/src/public/tools/task-update.d.ts",
-      "import": "./dist/src/public/tools/task-update.js",
-      "default": "./dist/src/public/tools/task-update.js"
-    },
     "./tools/glob": {
       "types": "./dist/src/public/tools/glob.d.ts",
       "import": "./dist/src/public/tools/glob.js",
@@ -498,6 +493,7 @@
     "jose": "6.2.3",
     "jsonc-parser": "3.3.1",
     "just-bash": "3.1.0",
+    "just-secrets": "0.0.2",
     "marked": "17.0.6",
     "microsandbox": "0.5.5",
     "next": "16.3.4",

package/dist/src/execution/tasks/child/update-step.d.ts

@@ -1,6 +0,0 @@
-import type { TaskInboundUpdate } from "#tasks/types.js";
-/** Forwards a local task-owned child's progress update to its active parent hook. */
-export declare function forwardLocalTaskUpdateStep(input: {
-    readonly parentContinuationToken: string;
-    readonly update: TaskInboundUpdate;
-}): Promise<void>;

package/dist/src/execution/tasks/child/update-step.js

@@ -1 +0,0 @@
-import{resumeHook}from"#internal/workflow/runtime.js";async function forwardLocalTaskUpdateStep(e){"use step";await resumeHook(e.parentContinuationToken,e.update)}export{forwardLocalTaskUpdateStep};

package/dist/src/execution/tasks/child/update.d.ts

@@ -1,8 +0,0 @@
-import type { ChannelAdapter } from "#channel/adapter.js";
-import type { TaskInboundUpdate } from "#tasks/types.js";
-/** Delivers a task update through the local child adapter or remote callback. */
-export declare function deliverTaskUpdate(input: {
-    readonly adapter?: ChannelAdapter;
-    readonly callback: unknown;
-    readonly update: TaskInboundUpdate;
-}): Promise<string | undefined>;

package/dist/src/execution/tasks/child/update.js

@@ -1 +0,0 @@
-import{fireTaskUpdateCallbackStep}from"#subagents/callback-step.js";import{forwardLocalTaskUpdateStep}from"#execution/tasks/child/update-step.js";import{SUBAGENT_ADAPTER_KIND,isSubagentAdapterState}from"#subagents/adapter-state.js";async function deliverTaskUpdate(e){let t=e.adapter?.state;return e.adapter?.kind===SUBAGENT_ADAPTER_KIND&&isSubagentAdapterState(t)&&t.taskId!==void 0?(await forwardLocalTaskUpdateStep({parentContinuationToken:t.parentContinuationToken,update:e.update}),t.taskId):await fireTaskUpdateCallbackStep({callback:e.callback,callId:e.update.callId,message:e.update.message,updateEpoch:e.update.updateEpoch,updateIndex:e.update.updateIndex})}export{deliverTaskUpdate};

package/dist/src/public/tools/task-update.d.ts

@@ -1 +0,0 @@
-export { taskUpdate, taskUpdate as default } from "#tools/framework/task-update.js";

package/dist/src/public/tools/task-update.js

@@ -1 +0,0 @@
-import{taskUpdate,taskUpdate as task_update_default}from"#tools/framework/task-update.js";export{task_update_default as default,taskUpdate};

package/dist/src/tools/framework/task-update.d.ts

@@ -1,5 +0,0 @@
-export declare const TASK_UPDATE_SESSION_INSTRUCTION = "Background task updates\nYou are running as a background task. For multi-step work, use `task_update` at meaningful milestones to briefly state what you are currently doing. Keep updates terse and activity-focused; do not include preliminary findings or results. Do not wait for a response, and return your final result normally.";
-export declare const taskUpdate: import("#tools/native-definition.js").NativeToolDefinition<{
-    message: string;
-}, unknown>;
-export default taskUpdate;

package/dist/src/tools/framework/task-update.js

@@ -1 +0,0 @@
-import{TASK_UPDATE_INPUT_SCHEMA}from"#tools/framework/task-contract.js";import{defineNativeTool}from"#tools/native-definition.js";const TASK_UPDATE_SESSION_INSTRUCTION="Background task updates\nYou are running as a background task. For multi-step work, use `task_update` at meaningful milestones to briefly state what you are currently doing. Keep updates terse and activity-focused; do not include preliminary findings or results. Do not wait for a response, and return your final result normally.",taskUpdate=defineNativeTool({description:`Briefly tell the parent agent what this background task is currently doing. Report activity, not preliminary findings or results.`,inputSchema:TASK_UPDATE_INPUT_SCHEMA},{availability:[`delegated-task-child`],handling:{action:`task-update`,kind:`dispatch`}});export{TASK_UPDATE_SESSION_INSTRUCTION,taskUpdate as default,taskUpdate};