Skip to content

feat(eve): remote authorization events via the durable resumeHook path#1207

Open
ruiconti wants to merge 1 commit into
rui/remote-terminal-callbackfrom
rui/remote-authorization-durable
Open

feat(eve): remote authorization events via the durable resumeHook path#1207
ruiconti wants to merge 1 commit into
rui/remote-terminal-callbackfrom
rui/remote-authorization-durable

Conversation

@ruiconti

Copy link
Copy Markdown
Contributor

Replaces the closed #1204. For #1170. Stacked on #1202 (terminal envelope).

What changed and why

#1204 relayed a remote callee's authorization.* through a best-effort route-direct side channel (world.streams.write, drop-ok). That was the wrong lane. Authorization events are low-frequency control — a handful per session, gated by human sign-ins — so they belong on the main run's durable path, exactly where a local subagent's authorization events already go.

This PR does that:

  • The callee forwards each authorization.required/authorization.completed to the caller's session-callback URL as a status: "notification" event (session-callback-notification.ts).
  • The caller's callback route projects it into a subagent-authorization-event hook payload and resumeHook(continuationToken)s the parked parent turn — the same durable resume the terminal callback uses.
  • The turn workflow handles it identically to a local subagent's authorization event (turn-workflow.tsrunProxySubagentEventStep → re-emit on the parent stream). Zero new handling in workflowEntry; it reuses the local path.

So local and remote authorization now converge on one mechanism, and nothing rides a lossy side channel.

The lane split (see #1205)

The separate high-frequency progress lane — the one that must stay off the main run's replay journal — remains reserved. It has no concrete event type yet, so it's future work; "working"/"input_required" stay reserved on the wire.

Not yet here

  • e2e verification. The fixture + evals aren't ported onto this branch yet. This branch re-emits authorization events raw on the parent stream (the durable proxy path), so the evals need feat(eve): propagate remote-callee authorization events to the caller #1167's top-level authorization.* assertions with the interactive-connection fixture (since the eve/tools export is dropped) — an adaptation, not a copy. Tracked as the next step; unit coverage (route projection + callee forwarder, 24 tests) is green in the meantime.
  • Remote input.required (proxied HITL) — shelved follow-up.

Unit suite 5367 green, lint + guard clean.

#1170)

A remote callee's authorization.required/completed events reach the
caller and ride the same durable path a local subagent's do: the callee
forwards each to the caller's session-callback URL as a
status: "notification" event; the caller route projects it into a
subagent-authorization-event and resumeHook()s the parked parent turn,
where the turn workflow proxies it onto the parent stream. No best-effort
side channel — authorization is low-frequency control, so it belongs on
the main run's journal, handled in workflowEntry exactly as local.

The high-frequency progress-relay lane (issue #1170) stays reserved: it
is the one that must avoid the main run's replay cost, and it has no
concrete event type yet.

Built on #1202's terminal envelope. Restores the forwarding stripped
when that PR isolated the terminal half.

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:56am
eve-docs-1644 Ready Ready Preview, Comment, Open in v0 Jul 25, 2026 1:56am
eve-docs-4759 Ready Ready Preview, Comment, Open in v0 Jul 25, 2026 1:56am

@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.04 MB -1.0 kB ✅
Package Unpacked publish size 14.71 MB 14.71 MB +3.0 kB ⚠️
Package Installed footprint 53.86 MB 53.87 MB +3.0 kB ⚠️
Package Published files 2745 2747 +2
Package Installed files 5985 5987 +2
Runtime Unique function payloads 2 2 0
Runtime Total function bytes 11.67 MB 11.67 MB +2.4 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/.well-known/workflow/v1/flow.func changed 7.26 MB 7.27 MB +1.8 kB ⚠️ none
functions/__server.func changed 4.40 MB 4.41 MB +635 B ⚠️ none

eve init install

Metric Baseline Current Delta
Installed footprint 92.27 MB 92.27 MB +3.0 kB ⚠️
Installed packages 122 122 0
dependencies 4 4 0
devDependencies 2 2 0
Dependency package bytes 28.99 MB 28.99 MB +3.0 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:57:19.640Z
  • 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.04 MB (eve-0.27.3.tgz)
  • Unpacked payload: 14.71 MB across 2747 published files
  • Installed footprint: 53.87 MB across 5987 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 7855 installed files
  • Installed packages: 122 total (116 transitive-only)
  • dependencies: 4 direct packages totaling 28.99 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.3%
🟠 functions/__server.func                         [###############.........] 4.41 MB 37.7%

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.41 MB (32.1%)

🟠 🔎 Dependency Analysis

📦 Bundled files:

Bundled file size
🟠 _chunks/runtime-artifacts.mjs   [########################] 1.41 MB 32.1%
🟠 _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             [##########..............] 597.9 kB 13.6%

🧾 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.71 s -> 2.68 s (-35.5 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.2 ms 1.2 ms 0.0 ms
project.resolve 0.6 ms 0.7 ms +0.1 ms
workspace.create 0.8 ms 0.8 ms 0.0 ms
host.prepare 230.0 ms 191.8 ms -38.2 ms
vercel.service-prefix.resolve 2.0 ms 2.1 ms +0.1 ms
nitro.app.create 26.1 ms 28.0 ms +1.9 ms
nitro.app.cache.prepare 0.2 ms 0.3 ms +0.1 ms
nitro.app.prepare 0.9 ms 1.0 ms +0.1 ms
nitro.app.public-assets 0.7 ms 0.8 ms +0.1 ms
nitro.app.prerender 0.6 ms 0.6 ms 0.0 ms
nitro.app.bundle 722.6 ms 737.2 ms +14.6 ms
nitro.app.cache.write 0.4 ms 0.4 ms 0.0 ms
sandbox.prewarm 294.4 ms 291.0 ms -3.4 ms
nitro.flow.create 172.8 ms 178.5 ms +5.7 ms
nitro.flow.cache.prepare 0.2 ms 0.2 ms 0.0 ms
nitro.flow.prepare 0.7 ms 1.0 ms +0.3 ms
nitro.flow.public-assets 0.2 ms 0.2 ms 0.0 ms
nitro.flow.prerender 0.0 ms 0.0 ms 0.0 ms
nitro.flow.bundle 1.07 s 1.06 s -17.9 ms
nitro.flow.cache.write 0.4 ms 0.3 ms -0.1 ms
nitro.flow.close 0.2 ms 0.2 ms 0.0 ms
workflow.emit 173.3 ms 174.4 ms +1.1 ms
agent-summary.emit 0.7 ms 0.6 ms -0.1 ms
nitro.app.close 0.1 ms 0.1 ms 0.0 ms
output.publish 3.9 ms 3.7 ms -0.2 ms
workspace.remove 5.7 ms 5.8 ms +0.1 ms

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