Skip to content

feat(eve): ingest session notifications inline in the callback route#1204

Closed
ruiconti wants to merge 2 commits into
rui/remote-terminal-callbackfrom
rui/notification-consumer-prototype
Closed

feat(eve): ingest session notifications inline in the callback route#1204
ruiconti wants to merge 2 commits into
rui/remote-terminal-callbackfrom
rui/notification-consumer-prototype

Conversation

@ruiconti

Copy link
Copy Markdown
Contributor

Relay lane for #1170. Stacked on #1202 (terminal/control lane); the research doc PR stacks on top of this one. Recreated after a stack reparent flipped the prior PR to a false MERGED state and auto-deleted its branch — nothing reached main.

What

Notification-class child events (authorization.*) reach the channel and the stream with no run, no hook, no queue wake — the event arrives as an HTTP callback, so the compute is already paid. POST /eve/v1/callback/<sessionId>:events:

  1. validates the reserved notification vocabulary and wraps the event as subagent.event (carrying childSessionId);
  2. loads the session entry run's channel context (world.runs.get, read-only) and runs the channel's existing adapter event handler against it — push channels render with zero authoring changes;
  3. appends the wrapped event to the session's durable stream (world.streams.write) for followers.

Best-effort per the lane's fire-once contract: a finished session logs and drops; nothing retries. Activates the "notification" status that #1202 reserved on the wire.

Two-lane split

Relay lane (fire-once, drop-ok, rendering-only) — counterpart to #1202's control lane (exactly-once, never-drop, durable resume).

Known-incomplete (prototype)

  • Caller-side ingestion only. The callee-side forwarder that sends authorization.* to :events isn't in this PR yet (lives in feat(eve): propagate remote-callee authorization events to the caller #1167's commit, needs adapting), so nothing produces on the lane end-to-end until it lands; the fixture + evals come with it.
  • childSessionId on SubagentChildEventStreamEvent trips the rule-36 capability-epoch ceremony (additive; not run), so guard:invariants fails on this branch.
  • Default stream name (strm_<id>_user) is a vendored-engine naming contract.

Typecheck clean; route + unit tests green.

…1170)

Notification-class child events (authorization.required/completed) reach
the caller's stream without a run, a hook, or a queue wake: the event
arrives as an HTTP callback, so the compute is already paid. The route
(POST /eve/v1/callback/<sessionId>:events) validates the closed
notification vocabulary, wraps the event as subagent.event (carrying
childSessionId), runs the channel's existing adapter event handler
against it, and appends it to the session's durable stream for
followers.

Both effects use world-level ops callable from plain runtime code:
world.runs.get loads the session entry's serialized channel context
read-only (no dedicated persistence), and world.streams.write appends by
the run-derived stream name. Both are best-effort per the lane's
fire-once contract — a finished session logs and drops; nothing retries.

Adds childSessionId to SubagentChildEventStreamEvent so the wrapper
carries the correlation the current re-emit drops. Prototype for
issue #1170; the sidecar-run alternative is retained in the research doc
as the graduated tier for event classes that need cursor semantics,
ordering, or consumer-held state.

Signed-off-by: Rui Conti <ruiconti@gmail.com>
@vercel

vercel Bot commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
eve-docs Ready Ready Preview, Comment, Open in v0 Jul 25, 2026 1:39am
2 Skipped Deployments
Project Deployment Actions Updated (UTC)
eve-docs-1644 Skipped Skipped Open in v0 Jul 25, 2026 1:39am
eve-docs-4759 Skipped Skipped Open in v0 Jul 25, 2026 1:39am

@github-actions

Copy link
Copy Markdown
Contributor

Bundle + Package Summary: apps/fixtures/weather-agent

Key takeaways

  • No notable deltas vs rui/remote-terminal-callback (8be5119).

Delta vs rui/remote-terminal-callback (8be5119)

Area Metric Baseline Current Delta
Package Packed tarball 4.05 MB 4.05 MB -800 B ✅
Package Unpacked publish size 14.71 MB 14.71 MB +5.8 kB ⚠️
Package Installed footprint 53.86 MB 53.87 MB +5.8 kB ⚠️
Package Published files 2745 2749 +4
Package Installed files 5985 5989 +4
Runtime Unique function payloads 2 2 0
Runtime Total function bytes 11.67 MB 11.68 MB +9.3 kB ⚠️
Runtime Public routes 10 10 0
Changed function payloads vs rui/remote-terminal-callback (8be5119) (2)
Function Status Baseline Current Delta Route changes
functions/__server.func changed 4.40 MB 4.41 MB +5.3 kB ⚠️ none
functions/.well-known/workflow/v1/flow.func changed 7.26 MB 7.27 MB +4.0 kB ⚠️ none

eve init install

Metric Baseline Current Delta
Installed footprint 92.27 MB 92.27 MB +5.8 kB ⚠️
Installed packages 122 122 0
dependencies 4 4 0
devDependencies 2 2 0
Dependency package bytes 28.99 MB 29.00 MB +5.8 kB ⚠️
devDependency package bytes 5.04 MB 5.04 MB 0 B ➖
Build Metadata
  • Preset: vercel
  • Nitro: nitro@3.0.260610-beta
  • Output directory: apps/fixtures/weather-agent/.vercel/output
  • Build metadata timestamp: 2026-07-25T01:22:23.901Z
  • Route aliases: 10 public, 1 internal (11 total aliases)
  • Vercel routes in config: 11
  • Severity legend: 🔴 dominant/large, 🟠 notable, 🟡 watch, ⚪ small
Package Drill-Down

Package Details

  • Package: eve@0.27.3
  • Package directory: packages/eve
  • Tarball: 4.05 MB (eve-0.27.3.tgz)
  • Unpacked payload: 14.71 MB across 2749 published files
  • Installed footprint: 53.87 MB across 5989 installed files
  • Installed root package: 13.43 MB
  • Installed dependencies: 40.44 MB
  • Runtime dependencies: 1
  • Peer dependencies: 5 (4 optional)

Installed footprint is measured from an isolated temporary npm install of the packed tarball.

Heavy installed dependencies

  • @rolldown/binding-linux-x64-gnu: 18.96 MB (35.2%)
  • eve: 13.43 MB (24.9%)
  • ai: 6.43 MB (11.9%)
  • zod: 5.04 MB (9.4%)
  • nitro: 2.41 MB (4.5%)
Publish payload breakdown
Published file size
🟠 dist/src/compiled/experimental-ai-sdk-code-mo... [###.....................] 1.51 MB 10.2%
🟡 dist/src/compiled/@vercel/sandbox/index.js       [#.......................] 632.4 kB 4.3%
🟡 dist/src/compiled/_chunks/workflow/undici-C2Z... [#.......................] 502.4 kB 3.4%
🟡 dist/src/compiled/@chat-adapter/slack/index.js   [#.......................] 440.5 kB 3.0%
🟡 dist/src/compiled/@vercel/oidc/index.js          [#.......................] 379.5 kB 2.6%
🔴 Other published files                            [########################] 11.25 MB 76.5%
Installed footprint breakdown
Installed package size
🔴 @rolldown/binding-linux-x64-gnu [########################] 18.96 MB 35.2%
🔴 eve                             [#################.......] 13.43 MB 24.9%
🔴 ai                              [########................] 6.43 MB 11.9%
🔴 zod                             [######..................] 5.04 MB 9.4%
🟠 nitro                           [###.....................] 2.41 MB 4.5%
🟡 @ai-sdk/provider-utils          [#.......................] 852.0 kB 1.6%
🔴 Other installed packages        [#########...............] 6.75 MB 12.5%
Runtime dependencies (1)
Package Range Notes
nitro 3.0.260610-beta
Peer dependencies (5)
Package Range Notes
@opentelemetry/api ^1.0.0 optional peer
ai catalog:
braintrust ^3.0.0 optional peer
just-bash ^3.0.0 optional peer
microsandbox ^0.5.0 optional peer
eve init install drill-down

eve init install details

  • Command: eve init my-agent
  • Package manager: npm
  • Installed footprint: 92.27 MB across 7857 installed files
  • Installed packages: 122 total (116 transitive-only)
  • dependencies: 4 direct packages totaling 29.00 MB
  • devDependencies: 2 direct packages totaling 5.04 MB
  • Other transitive package files: 58.24 MB

Installed footprint is measured from an isolated temporary eve init my-agent using the current packed eve tarball.

Heavy installed dependencies

  • @typescript/typescript-linux-x64: 27.95 MB (30.3%)
  • @rolldown/binding-linux-x64-gnu: 18.96 MB (20.5%)
  • eve: 13.43 MB (14.6%)
  • zod: 9.00 MB (9.8%)
  • ai: 6.43 MB (7.0%)
Installed footprint breakdown
Installed package size
🔴 @typescript/typescript-linux-x64 [########################] 27.95 MB 30.3%
🔴 @rolldown/binding-linux-x64-gnu  [################........] 18.96 MB 20.5%
🔴 eve                              [############............] 13.43 MB 14.6%
🔴 zod                              [########................] 9.00 MB 9.8%
🔴 ai                               [######..................] 6.43 MB 7.0%
🟠 @types/node                      [##......................] 2.54 MB 2.8%
🔴 Other installed packages         [############............] 13.97 MB 15.1%
dependencies (4)
Package Range Installed size Share
@vercel/connect 0.4.2 135.8 kB 0.1%
ai ^7.0.34 6.43 MB 7.0%
eve file:eve-0.27.3.tgz 13.43 MB 14.6%
zod 4.4.3 9.00 MB 9.8%
devDependencies (2)
Package Range Installed size Share
@types/node 24.x 2.54 MB 2.8%
typescript 7.0.2 2.50 MB 2.7%
Function Drill-Down

Payload Size Graph

Unique function payload size and share of total
🔴 functions/.well-known/workflow/v1/flow.func     [########################] 7.27 MB 62.2%
🟠 functions/__server.func                         [###############.........] 4.41 MB 37.8%

Top Function Payloads

🟠 functions/.well-known/workflow/v1/flow.func • 1 public route • 7.27 MB
Metric Value
Public routes /.well-known/workflow/v1/flow
Runtime nodejs24.x
Handler index.mjs
Payload 7.27 MB
Function files 7.27 MB across 39 files
Traced dependencies 0 B
Signal 🟠 Bundled file __eve_nitro_handler__.mjs is 2.71 MB (37.3%)

🟠 🔎 Dependency Analysis

📦 Bundled files:

Bundled file size
🟠 __eve_nitro_handler__.mjs       [########################] 2.71 MB 37.3%
🟡 _chunks/world-vercel.mjs        [########................] 903.2 kB 12.4%
🟡 _chunks/sandbox.mjs             [#######.................] 767.6 kB 10.6%
🟡 _libs/@ai-sdk/gateway+[...].mjs [####....................] 432.5 kB 6.0%
🟡 _chunks/token-util-B6qBs3-0.mjs [###.....................] 379.1 kB 5.2%
🟠 Other bundled files             [##################......] 2.08 MB 28.6%

🧾 Vercel Config

{
  "handler": "index.mjs",
  "launcherType": "Nodejs",
  "shouldAddHelpers": false,
  "supportsResponseStreaming": true,
  "runtime": "nodejs24.x",
  "environment": {
    "WORKFLOW_PRECONDITION_GUARD": "1",
    "NODE_OPTIONS": "--experimental-require-module"
  },
  "maxDuration": "max",
  "experimentalTriggers": [
    {
      "type": "queue/v2beta",
      "topic": "__eve776561746865722d6167656e74_wkf_workflow_*",
      "consumer": "default",
      "retryAfterSeconds": 5,
      "initialDelaySeconds": 0
    }
  ]
}

🟠 functions/__server.func • 9 public routes, 1 internal alias • 4.41 MB
Metric Value
Public routes /
/eve/v1/callback/[token]
/eve/v1/connections/[name]/callback/[token]
/eve/v1/health
/eve/v1/info
/eve/v1/session
/eve/v1/session/[sessionId]
/eve/v1/session/[sessionId]/cancel
/eve/v1/session/[sessionId]/stream
Internal aliases /__server
Runtime nodejs24.x
Handler index.mjs
Payload 4.41 MB
Function files 4.41 MB across 30 files
Traced dependencies 0 B
Signal 🟠 Bundled file _chunks/runtime-artifacts.mjs is 1.45 MB (33.0%)

🟠 🔎 Dependency Analysis

📦 Bundled files:

Bundled file size
🟠 _chunks/runtime-artifacts.mjs   [########################] 1.45 MB 33.0%
🟠 _chunks/world-vercel.mjs        [###############.........] 900.3 kB 20.4%
🟠 _chunks/sandbox.mjs             [#############...........] 767.6 kB 17.4%
🟡 _chunks/token-util-B6qBs3-0.mjs [######..................] 379.1 kB 8.6%
🟡 _chunks/dist-BX517Nmz.mjs       [######..................] 348.7 kB 7.9%
🟡 Other bundled files             [#########...............] 561.0 kB 12.7%

🧾 Vercel Config

{
  "handler": "index.mjs",
  "launcherType": "Nodejs",
  "shouldAddHelpers": false,
  "supportsResponseStreaming": true,
  "runtime": "nodejs24.x"
}

Build Timing: e2e/fixtures/agent-tools-sandbox

This is an informational timing measurement inside eve build, from preflight through publication. Output-size measurement and profile writing are excluded.

Build mode: deployable Vercel build with sandbox template prewarm included.

  • Build pipeline: 2.65 s -> 2.88 s (+231.8 ms) vs rui/remote-terminal-callback (8be5119).
  • Timing is informational: shared GitHub runners are too variable for a hard timing budget.
Detailed phase timings vs `rui/remote-terminal-callback (8be5119)`
Phase Baseline Current Delta
extension.check 1.1 ms 1.1 ms 0.0 ms
project.resolve 0.6 ms 0.6 ms 0.0 ms
workspace.create 0.8 ms 0.7 ms -0.1 ms
host.prepare 240.1 ms 154.6 ms -85.5 ms
vercel.service-prefix.resolve 2.3 ms 2.4 ms +0.1 ms
nitro.app.create 24.7 ms 24.3 ms -0.4 ms
nitro.app.cache.prepare 0.2 ms 0.3 ms +0.1 ms
nitro.app.prepare 0.9 ms 0.9 ms 0.0 ms
nitro.app.public-assets 0.8 ms 0.7 ms -0.1 ms
nitro.app.prerender 0.5 ms 0.6 ms +0.1 ms
nitro.app.bundle 687.9 ms 685.6 ms -2.3 ms
nitro.app.cache.write 0.3 ms 0.4 ms +0.1 ms
sandbox.prewarm 231.0 ms 605.3 ms +374.3 ms
nitro.flow.create 166.1 ms 166.7 ms +0.6 ms
nitro.flow.cache.prepare 0.2 ms 0.2 ms 0.0 ms
nitro.flow.prepare 0.8 ms 0.9 ms +0.1 ms
nitro.flow.public-assets 0.2 ms 0.1 ms -0.1 ms
nitro.flow.prerender 0.0 ms 0.0 ms 0.0 ms
nitro.flow.bundle 1.09 s 1.06 s -35.7 ms
nitro.flow.cache.write 0.4 ms 0.4 ms 0.0 ms
nitro.flow.close 0.2 ms 0.2 ms 0.0 ms
workflow.emit 189.2 ms 169.4 ms -19.8 ms
agent-summary.emit 0.5 ms 0.6 ms +0.1 ms
nitro.app.close 0.0 ms 0.1 ms +0.1 ms
output.publish 3.8 ms 3.8 ms 0.0 ms
workspace.remove 5.3 ms 5.8 ms +0.5 ms

…chema

projectWrappedNotificationEvent hand-checked callId/subagentName with
typeof and only zod-parsed the nested event, so the top-level payload
contract could drift from the event contract. Fold both into a single
notificationCallbackPayloadSchema (sessionId optional, unknown top-level
keys stripped) parsed in one pass.

Signed-off-by: Rui Conti <ruiconti@gmail.com>
@ruiconti

Copy link
Copy Markdown
Contributor Author

Closing per design correction: authorization.* is low-frequency control, not high-frequency progress, so it belongs on the main run's durable resumeHook path (handled in workflowEntry like a local subagent), not this best-effort route-direct relay. Rebuilding on #1202 as remote authorization via the durable path; the progress relay this branch prototyped is reserved until a concrete progress event type exists. See #1205 for the corrected framing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant