Uh oh!
There was an error while loading. Please reload this page.
feat(eve): identify eve on AI Gateway, Workflow, and Sandbox requests - #939
Merged
Conversation
…ery fails getVercelSandboxGetOptions only attached the fetch override in the credential-discovery success branch, so on the catch path Sandbox.get() fell back to the SDK's bare global fetch. Move the fetch into the shared base options so both branches use it. Signed-off-by: Rui Conti <ruiconti@gmail.com>
Append an eve/<installed version> User-Agent product token to every
Vercel-service request eve makes, so receiving services can attribute
traffic to eve and its version without new headers or protocols:
- AI Gateway: model generation and compaction (tool-loop), autoeval
judge calls, the model catalog and setup catalog fetches, CLI model
lookup, and API-key validation. Gateway-routed models are detected via
isGatewayModel (bare ids and gateway.* instances).
- Workflow: generated world-vercel startup code passes the token via
createWorld({ headers }). Inert until the vendored @workflow/world-vercel
ships the caller User-Agent append (currently 5.0.0-beta.31, which
discards caller UA) — requests degrade to today's behavior, no failure.
- Sandbox: the SDK fetch decoration is generalized from the eve-specific
helper to appendPackageUserAgent.
The token is appended per the RFC 9110 User-Agent grammar (whitespace-
delimited products), never replacing existing products, idempotent on
re-append. Receivers parse it with whitespace-token scanners, so joining
uses spaces, not Headers.append() comma-combination.
Signed-off-by: Rui Conti <ruiconti@gmail.com>Contributor
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Bundle + Package Summary: |
| Area | Metric | Baseline | Current | Delta |
|---|---|---|---|---|
| Package | Packed tarball | 3.80 MB | 3.81 MB | +636 B |
| Package | Unpacked publish size | 13.77 MB | 13.78 MB | +3.6 kB |
| Package | Installed footprint | 52.88 MB | 52.89 MB | +3.6 kB |
| Package | Published files | 2722 | 2724 | +2 |
| Package | Installed files | 5962 | 5964 | +2 |
| Runtime | Unique function payloads | 2 | 2 | 0 |
| Runtime | Total function bytes | 9.75 MB | 9.75 MB | +3 B |
| Runtime | Public routes | 10 | 10 | 0 |
Changed function payloads vs main (d034e01) (2)
| Function | Status | Baseline | Current | Delta | Route changes |
|---|---|---|---|---|---|
functions/.well-known/workflow/v1/flow.func | changed | 6.28 MB | 6.28 MB | +191 B | none |
functions/__server.func | changed | 3.47 MB | 3.47 MB | -188 B ✅ | none |
eve init install
| Metric | Baseline | Current | Delta |
|---|---|---|---|
| Installed footprint | 91.29 MB | 91.29 MB | +3.6 kB |
| Installed packages | 122 | 122 | 0 |
| dependencies | 4 | 4 | 0 |
| devDependencies | 2 | 2 | 0 |
| Dependency package bytes | 28.02 MB | 28.03 MB | +3.6 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-20T23:51:17.985Z
- 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.26.1 - Package directory:
packages/eve - Tarball: 3.81 MB (
eve-0.26.1.tgz) - Unpacked payload: 13.78 MB across 2724 published files
- Installed footprint: 52.89 MB across 5964 installed files
- Installed root package: 12.50 MB
- Installed dependencies: 40.39 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.8%)eve: 12.50 MB (23.6%)ai: 6.39 MB (12.1%)zod: 5.04 MB (9.5%)nitro: 2.41 MB (4.6%)
Publish payload breakdown
Published file size
🟠 dist/src/compiled/experimental-ai-sdk-code-mo... [###.....................] 1.51 MB 10.9%
🟡 dist/src/compiled/@vercel/sandbox/index.js [#.......................] 622.2 kB 4.5%
🟡 dist/src/compiled/_chunks/workflow/undici-fb5... [#.......................] 502.4 kB 3.6%
🟡 dist/src/compiled/@chat-adapter/slack/index.js [#.......................] 433.3 kB 3.1%
🟡 dist/src/compiled/_chunks/workflow/dist-CSfKN... [#.......................] 277.8 kB 2.0%
🔴 Other published files [########################] 10.44 MB 75.7%
Installed footprint breakdown
Installed package size
🔴 @rolldown/binding-linux-x64-gnu [########################] 18.96 MB 35.8%
🔴 eve [################........] 12.50 MB 23.6%
🔴 ai [########................] 6.39 MB 12.1%
🔴 zod [######..................] 5.04 MB 9.5%
🟠 nitro [###.....................] 2.41 MB 4.6%
🟡 @ai-sdk/provider-utils [#.......................] 847.6 kB 1.6%
🔴 Other installed packages [#########...............] 6.74 MB 12.7%
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: 91.29 MB across 7832 installed files
- Installed packages: 122 total (116 transitive-only)
- dependencies: 4 direct packages totaling 28.03 MB
- devDependencies: 2 direct packages totaling 5.04 MB
- Other transitive package files: 58.22 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.6%)@rolldown/binding-linux-x64-gnu: 18.96 MB (20.8%)eve: 12.50 MB (13.7%)zod: 9.00 MB (9.9%)ai: 6.39 MB (7.0%)
Installed footprint breakdown
Installed package size
🔴 @typescript/typescript-linux-x64 [########################] 27.95 MB 30.6%
🔴 @rolldown/binding-linux-x64-gnu [################........] 18.96 MB 20.8%
🔴 eve [###########.............] 12.50 MB 13.7%
🔴 zod [########................] 9.00 MB 9.9%
🔴 ai [#####...................] 6.39 MB 7.0%
🟠 @types/node [##......................] 2.54 MB 2.8%
🔴 Other installed packages [############............] 13.95 MB 15.3%
dependencies (4)
| Package | Range | Installed size | Share |
|---|---|---|---|
@vercel/connect | 0.4.0 | 135.4 kB | 0.1% |
ai | ^7.0.26 | 6.39 MB | 7.0% |
eve | file:eve-0.26.1.tgz | 12.50 MB | 13.7% |
zod | 4.4.3 | 9.00 MB | 9.9% |
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 [########################] 6.28 MB 64.4%
🟠 functions/__server.func [#############...........] 3.47 MB 35.6%
Top Function Payloads
🟠 functions/.well-known/workflow/v1/flow.func • 1 public route • 6.28 MB
| Metric | Value |
|---|---|
| Public routes | /.well-known/workflow/v1/flow |
| Runtime | nodejs24.x |
| Handler | index.mjs |
| Payload | 6.28 MB |
| Function files | 6.28 MB across 37 files |
| Traced dependencies | 0 B |
| Signal | 🟠 Bundled file __eve_nitro_handler__.mjs is 2.21 MB (35.2%) |
🟠 🔎 Dependency Analysis
📦 Bundled files:
Bundled file size
🟠 __eve_nitro_handler__.mjs [########################] 2.21 MB 35.2%
🟡 _chunks/world-vercel.mjs [#########...............] 826.3 kB 13.2%
🟡 _chunks/sandbox.mjs [########................] 754.9 kB 12.0%
🟡 _libs/@ai-sdk/gateway+[...].mjs [#####...................] 430.4 kB 6.9%
🟡 _libs/zod.mjs [####....................] 376.1 kB 6.0%
🟠 Other bundled files [##################......] 1.68 MB 26.8%
🧾 Vercel Config
{
"handler": "index.mjs",
"launcherType": "Nodejs",
"shouldAddHelpers": false,
"supportsResponseStreaming": true,
"runtime": "nodejs24.x",
"environment": {
"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 • 3.47 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 | 3.47 MB |
| Function files | 3.47 MB across 28 files |
| Traced dependencies | 0 B |
| Signal | 🟠 Bundled file _chunks/runtime-artifacts.mjs is 949.0 kB (27.3%) |
🟠 🔎 Dependency Analysis
📦 Bundled files:
Bundled file size
🟠 _chunks/runtime-artifacts.mjs [########################] 949.0 kB 27.3%
🟠 _chunks/world-vercel.mjs [#####################...] 823.4 kB 23.7%
🟠 _chunks/sandbox.mjs [###################.....] 754.9 kB 21.8%
🟡 _chunks/dist-CSfKNxQW.mjs [#########...............] 348.5 kB 10.0%
⚪ _libs/zod.mjs [###.....................] 114.2 kB 3.3%
🟡 Other bundled files [############............] 480.2 kB 13.8%
🧾 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.41 s -> 2.38 s (-36.9 ms) vs
main (d034e01). - Timing is informational: shared GitHub runners are too variable for a hard timing budget.
Detailed phase timings vs `main (d034e01)`
| Phase | Baseline | Current | Delta |
|---|---|---|---|
extension.check | 1.1 ms | 0.9 ms | -0.2 ms |
project.resolve | 0.7 ms | 0.6 ms | -0.1 ms |
workspace.create | 0.9 ms | 0.7 ms | -0.2 ms |
host.prepare | 230.6 ms | 230.3 ms | -0.3 ms |
vercel.service-prefix.resolve | 2.1 ms | 2.1 ms | 0.0 ms |
nitro.app.create | 24.3 ms | 24.2 ms | -0.1 ms |
nitro.app.cache.prepare | 0.2 ms | 0.2 ms | 0.0 ms |
nitro.app.prepare | 0.9 ms | 0.8 ms | -0.1 ms |
nitro.app.public-assets | 0.7 ms | 0.7 ms | 0.0 ms |
nitro.app.prerender | 0.5 ms | 0.5 ms | 0.0 ms |
nitro.app.bundle | 547.7 ms | 554.9 ms | +7.2 ms |
nitro.app.cache.write | 0.5 ms | 0.4 ms | -0.1 ms |
sandbox.prewarm | 278.3 ms | 260.6 ms | -17.7 ms |
nitro.flow.create | 185.2 ms | 178.8 ms | -6.4 ms |
nitro.flow.cache.prepare | 0.2 ms | 0.2 ms | 0.0 ms |
nitro.flow.prepare | 0.9 ms | 0.9 ms | 0.0 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 | 952.2 ms | 935.9 ms | -16.3 ms |
nitro.flow.cache.write | 0.3 ms | 0.3 ms | 0.0 ms |
nitro.flow.close | 0.2 ms | 0.2 ms | 0.0 ms |
workflow.emit | 173.9 ms | 170.9 ms | -3.0 ms |
agent-summary.emit | 0.6 ms | 0.5 ms | -0.1 ms |
nitro.app.close | 0.0 ms | 0.0 ms | 0.0 ms |
output.publish | 3.7 ms | 3.7 ms | 0.0 ms |
workspace.remove | 5.7 ms | 5.8 ms | +0.1 ms |
createWorkflowWorldPluginSource encoded the world selection three times: a nested ternary for the createWorld statement, a repeated condition for the runtime imports, and another for the vendored module specifier. The pieces co-vary — a world constructed through an explicit createWorld(config) call must not import createWorldFromModule — so hiding that invariant across three expressions made every new world branch risky to add. resolveWorkflowWorldWiring now owns all four facts per world; the caller is pure assembly. Generated output is byte-identical for the world-local, world-vercel, and passthrough branches (verified by rendering both versions and comparing). Signed-off-by: Rui Conti <ruiconti@gmail.com>
gateway.ts exported its internals — buildGatewayURL, addGatewayUA, buildGatewayUA, isGatewayModel — and every call site reassembled them: URLs were rebuilt locally, and model-conditional header logic leaked as isGatewayModel(...) ? Object.fromEntries(addGatewayUA(...)) : undefined. The module now owns the decisions instead of the parts: - AI_GATEWAY_MODELS_URL / AI_GATEWAY_MODELS_CATALOG_URL live in gateway.ts. - getVercelGatewayFetch() returns a UA-decorated fetch, mirroring the Sandbox binding's getVercelSandboxFetch — call sites get a transport, not header plumbing. validate-gateway-key routes its provider fetch through it instead of construction headers. - resolveProviderHeaders(model) answers "which headers does this model's provider need" directly; isGatewayModel is private again. The generic fetch decoration moves from the sandbox-named withSandboxUserAgent to withPackageUserAgent in internal/user-agent.ts (the sandbox binding and the gateway both wrap it). Its default now resolves globalThis.fetch per request instead of capturing it at wrap time, so globally installed fetch instrumentation still applies. Signed-off-by: Rui Conti <ruiconti@gmail.com>
The world-wiring branches built their return values from inline
expressions and join("\n") arrays. Name the intermediates and write the
generated snippets as leading-newline template literals (trimStart keeps
the emitted text starting at the statement), so each branch reads as: the
specifiers, the code it emits, the wiring object.
Generated output is byte-identical for all three branches (verified by
rendering the HEAD version and this one against the same inputs).
Signed-off-by: Rui Conti <ruiconti@gmail.com>withPackageUserAgent resolves globalThis.fetch per request when no inner fetch is given, so later-installed global fetch instrumentation still applies. Passing globalThis.fetch explicitly here captured it at options-build time, quietly opting the sandbox path out of that contract while the gateway path honored it. Signed-off-by: Rui Conti <ruiconti@gmail.com>
…ever casts ai/test's mock satisfies the LanguageModel contract, so the resolveProviderHeaders tests no longer need to cast partial objects. Same pattern tool-loop.test.ts already uses. Signed-off-by: Rui Conti <ruiconti@gmail.com>
Uh oh!
There was an error while loading. Please reload this page.
Comment on lines
+5
to
+6
| const { name, version } = resolveInstalledPackageInfo(); | ||
| return `${name}/${version}`; |
Collaborator
There was a problem hiding this comment.
Should we include agent name as well?
ContributorAuthor
There was a problem hiding this comment.
We can infer project via deploymentId which is already part of User-Agent. Unless you were thinking of some other use for it
getVercelGatewayFetch() mirrored the Sandbox binding's factory shape, but unlike getVercelSandboxFetch(createOptions) it had nothing to construct — call sites read getVercelGatewayFetch()(url). withPackageUserAgent late-binds globalThis.fetch per request, so a module-level const is safe and the call sites become plain vercelGatewayFetch(url). Signed-off-by: Rui Conti <ruiconti@gmail.com>
…ification Signed-off-by: Rui Conti <ruiconti@gmail.com> # Conflicts: # packages/eve/src/setup/boxes/select-model.test.ts # packages/eve/src/setup/boxes/select-model.ts
AndrewBarba
approved these changes
Jul 20, 2026
AndrewBarba
enabled auto-merge (squash)
July 20, 2026 23:49
Uh oh!
There was an error while loading. Please reload this page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Vercel services can't tell eve traffic from any other AI SDK app today. This appends an
eve/<installed version>User-Agent product token to every service request eve makes, so receivers can attribute traffic to eve and its version — segmenting by framework during incidents and, later, controlling traffic keyed on the same token.What
internal/user-agent.ts: builds theeve/<version>product token, appends it to aHeaderswithout touching existing products (idempotent, space-joined per the RFC 9110 UA grammar — notHeaders.append(), whose comma-combination breaks whitespace-delimited parsers), and exposeswithPackageUserAgent(fetch), the generic UA-decorating fetch wrapper both the Gateway and Sandbox transports build on.internal/gateway.tsowns the Gateway transport surface: the/v1/modelsand/v1/models/catalogURLs,getVercelGatewayFetch()(a UA-decorated fetch, mirroring the Sandbox binding'sgetVercelSandboxFetch), andresolveProviderHeaders(model)— headers for Gateway-routed models (bare ids andgateway.*instances),undefinedfor direct providers.createWorld({ headers }), with the per-world wiring dispatched in one place (resolveWorkflowWorldWiring).withPackageUserAgent. A separate commit fixes a real gap here:Sandbox.get()lost the custom fetch on the credential-discovery failure path.Wire format
Captured against a local server through the real
ai/@ai-sdk/gatewaypackages — existing products stay intact:The Workflow leg is inert until a vendored bump
The vendored
@workflow/world-vercel@5.0.0-beta.31overwrites caller User-Agents, so the header this PR passes is dropped on the wire today (requests degrade to current behavior — nothing fails). vercel/workflow#2998 fixes the append; a follow-up bump of the vendored package lights this leg up.Compaction attribution fix
Gateway attribution headers for compaction were previously computed from the main model; they now derive from the compaction model itself, since the two can differ.