feat(eve): expose effective model to dynamic resolvers - #2298
Conversation
Bundle + Package Summary:
|
| Area | Metric | Baseline | Current | Delta |
|---|---|---|---|---|
| Package | Packed tarball | 8.24 MB | 8.24 MB | +826 B |
| Package | Unpacked publish size | 30.96 MB | 30.96 MB | +1.6 kB |
| Package | Installed footprint | 75.00 MB | 75.00 MB | +1.6 kB |
| Package | Published files | 3350 | 3352 | +2 |
| Package | Installed files | 7058 | 7060 | +2 |
| Package | Installed package instances | 35 | 35 | 0 |
| Package | Distinct installed package names | 34 | 34 | 0 |
| Package | Installed dependency edges | 53 | 53 | 0 |
| Package | Installed optional peer edges | 47 | 47 | 0 |
| Runtime | Unique function payloads | 2 | 2 | 0 |
| Runtime | Total function bytes | 18.05 MB | 18.05 MB | +2.3 kB |
| Runtime | Public routes | 16 | 16 | 0 |
Changed function payloads vs main (75bd9c8) (2)
| Function | Status | Baseline | Current | Delta | Route changes |
|---|---|---|---|---|---|
functions/__server.func |
changed | 9.02 MB | 9.03 MB | +1.1 kB |
none |
functions/.well-known/workflow/v1/flow.func |
changed | 9.02 MB | 9.03 MB | +1.1 kB |
none |
eve init install
| Metric | Baseline | Current | Delta |
|---|---|---|---|
| Installed footprint | 113.41 MB | 113.41 MB | +1.6 kB |
| Installed packages | 121 | 121 | 0 |
| dependencies | 4 | 4 | 0 |
| devDependencies | 2 | 2 | 0 |
| Dependency package bytes | 45.46 MB | 45.47 MB | +1.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-08-19T20:33:36.248Z
- Route aliases: 16 public, 1 internal (17 total aliases)
- Vercel routes in config: 19
- Severity legend: 🔴 dominant/large, 🟠 notable, 🟡 watch, ⚪ small
Package Drill-Down
Package Details
- Package:
eve@0.39.2 - Package directory:
packages/eve - Tarball: 8.24 MB (
eve-0.39.2.tgz) - Unpacked payload: 30.96 MB across 3352 published files
- Installed footprint: 75.00 MB across 7060 installed files
- Installed root package: 29.61 MB
- Installed dependencies: 45.39 MB
- Installed package instances: 35
- Distinct installed package names: 34
- Installed dependency edges: 53
- Installed optional peer edges: 47
- Runtime dependencies: 2
- Peer dependencies: 5 (4 optional)
Installed footprint is measured from an isolated temporary npm install of the packed tarball.
Graph metrics read only package.json files in package directories directly beneath a node_modules boundary, including nested boundaries. Each directory is one package instance; distinct names come from those manifests. Dependency edges count each unique name in dependencies or optionalDependencies per instance; optional peer edges count peerDependencies marked optional.
Heavy installed dependencies
eve: 29.61 MB (39.5%)@rolldown/binding-linux-x64-gnu: 19.91 MB (26.5%)ai: 6.69 MB (8.9%)zod: 5.07 MB (6.8%)undici: 3.50 MB (4.7%)
Publish payload breakdown
Published file size
🔴 dist/src/compiled/shadcn-registry/index.js [###############.........] 10.20 MB 32.9%
🟠 dist/src/compiled/@photon-ai/chat-adapter-ime... [####....................] 2.44 MB 7.9%
🟠 dist/src/compiled/experimental-ai-sdk-code-mo... [##......................] 1.51 MB 4.9%
🟡 dist/src/compiled/_chunks/node/undici-CUIybhQ... [#.......................] 508.8 kB 1.6%
🟡 dist/src/compiled/_chunks/workflow/undici-BBG... [#.......................] 508.8 kB 1.6%
🔴 Other published files [########################] 15.80 MB 51.0%
Installed footprint breakdown
Installed package size
🔴 eve [########################] 29.61 MB 39.5%
🔴 @rolldown/binding-linux-x64-gnu [################........] 19.91 MB 26.5%
🔴 ai [#####...................] 6.69 MB 8.9%
🔴 zod [####....................] 5.07 MB 6.8%
🟠 undici [###.....................] 3.50 MB 4.7%
🟠 nitro [##......................] 2.41 MB 3.2%
🔴 Other installed packages [######..................] 7.81 MB 10.4%
Runtime dependencies (2)
| Package | Range | Notes |
|---|---|---|
nitro |
3.0.260610-beta |
|
undici |
8.9.0 |
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: 113.41 MB across 8936 installed files
- Installed packages: 121 total (115 transitive-only)
- dependencies: 4 direct packages totaling 45.47 MB
- devDependencies: 2 direct packages totaling 5.04 MB
- Other transitive package files: 62.90 MB
Installed footprint is measured from an isolated temporary eve init my-agent using the current packed eve tarball.
Heavy installed dependencies
eve: 29.61 MB (26.1%)@typescript/typescript-linux-x64: 27.95 MB (24.6%)@rolldown/binding-linux-x64-gnu: 19.91 MB (17.6%)zod: 9.02 MB (8.0%)ai: 6.69 MB (5.9%)
Installed footprint breakdown
Installed package size
🔴 eve [########################] 29.61 MB 26.1%
🔴 @typescript/typescript-linux-x64 [#######################.] 27.95 MB 24.6%
🔴 @rolldown/binding-linux-x64-gnu [################........] 19.91 MB 17.6%
🔴 zod [#######.................] 9.02 MB 8.0%
🔴 ai [#####...................] 6.69 MB 5.9%
🟠 undici [###.....................] 3.50 MB 3.1%
🔴 Other installed packages [##############..........] 16.72 MB 14.7%
dependencies (4)
| Package | Range | Installed size | Share |
|---|---|---|---|
@vercel/connect |
0.4.3 |
141.0 kB | 0.1% |
ai |
^7.0.58 |
6.69 MB | 5.9% |
eve |
file:eve-0.39.2.tgz |
29.61 MB | 26.1% |
zod |
4.4.3 |
9.02 MB | 8.0% |
devDependencies (2)
| Package | Range | Installed size | Share |
|---|---|---|---|
@types/node |
24.x |
2.54 MB | 2.2% |
typescript |
7.0.2 |
2.50 MB | 2.2% |
Function Drill-Down
Payload Size Graph
Unique function payload size and share of total
🔴 functions/.well-known/workflow/v1/flow.func [########################] 9.03 MB 50.0%
🔴 functions/__server.func [########################] 9.03 MB 50.0%
Top Function Payloads
🟠 functions/.well-known/workflow/v1/flow.func • 1 public route • 9.03 MB
| Metric | Value |
|---|---|
| Public routes | /.well-known/workflow/v1/flow |
| Runtime | nodejs24.x |
| Handler | index.mjs |
| Payload | 9.03 MB |
| Function files | 9.03 MB across 50 files |
| Traced dependencies | 0 B |
| Signal | 🟠 Bundled file index.mjs is 2.00 MB (22.2%) |
🟠 🔎 Dependency Analysis
📦 Bundled files:
Bundled file size
🟠 index.mjs [#################.......] 2.00 MB 22.2%
🟠 _chunks/runtime-artifacts.mjs [###############.........] 1.79 MB 19.8%
🟡 _libs/undici.mjs [########................] 980.5 kB 10.9%
🟡 _chunks/sandbox.mjs [#######.................] 781.9 kB 8.7%
🟡 _chunks/frames-DoexhtxJ.mjs [######..................] 672.6 kB 7.5%
🟠 Other bundled files [########################] 2.80 MB 31.0%
🧾 Vercel Config
{
"handler": "index.mjs",
"launcherType": "Nodejs",
"shouldAddHelpers": false,
"supportsResponseStreaming": true,
"runtime": "nodejs24.x",
"maxDuration": "max",
"experimentalTriggers": [
{
"type": "queue/v2beta",
"topic": "__eve776561746865722d6167656e74_wkf_workflow_*",
"consumer": "default",
"retryAfterSeconds": 5,
"initialDelaySeconds": 0
}
],
"environment": {
"WORKFLOW_PRECONDITION_GUARD": "1"
}
}🟠 functions/__server.func • 15 public routes, 1 internal alias • 9.03 MB
| Metric | Value |
|---|---|
| Public routes | //eve/v1/callback/[token]/eve/v1/connections/[name]/callback/[attemptId]/[token]/eve/v1/connections/[name]/callback/[token]/eve/v1/health/eve/v1/info/eve/v1/session/eve/v1/session/[parentSessionId]/subagents/[callId]/[childSessionId]/stream/eve/v1/session/[sessionId]/eve/v1/session/[sessionId]/cancel/eve/v1/session/[sessionId]/clear/eve/v1/session/[sessionId]/compact/eve/v1/session/[sessionId]/reset/eve/v1/session/[sessionId]/stream/eve/v1/task-input/[token] |
| Internal aliases | /__server |
| Runtime | nodejs24.x |
| Handler | index.mjs |
| Payload | 9.03 MB |
| Function files | 9.03 MB across 50 files |
| Traced dependencies | 0 B |
| Signal | 🟠 Bundled file index.mjs is 2.00 MB (22.2%) |
🟠 🔎 Dependency Analysis
📦 Bundled files:
Bundled file size
🟠 index.mjs [#################.......] 2.00 MB 22.2%
🟠 _chunks/runtime-artifacts.mjs [###############.........] 1.79 MB 19.8%
🟡 _libs/undici.mjs [########................] 980.5 kB 10.9%
🟡 _chunks/sandbox.mjs [#######.................] 781.9 kB 8.7%
🟡 _chunks/frames-DoexhtxJ.mjs [######..................] 672.6 kB 7.5%
🟠 Other bundled files [########################] 2.80 MB 31.0%
🧾 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.27 s -> 2.15 s (-118.5 ms) vs
main (75bd9c8). - Timing is informational: shared GitHub runners are too variable for a hard timing budget.
Detailed phase timings vs `main (75bd9c8)`
| Phase | Baseline | Current | Delta |
|---|---|---|---|
extension.check |
1.1 ms | 1.1 ms | 0.0 ms |
project.resolve |
0.3 ms | 0.3 ms | 0.0 ms |
workspace.create |
0.7 ms | 0.7 ms | 0.0 ms |
host.prepare |
384.8 ms | 276.1 ms | -108.7 ms |
vercel.service-prefix.resolve |
2.3 ms | 2.8 ms | +0.5 ms |
nitro.create |
247.3 ms | 257.7 ms | +10.4 ms |
sandbox.prewarm |
213.4 ms | 199.7 ms | -13.7 ms |
nitro.cache.prepare |
0.2 ms | 0.3 ms | +0.1 ms |
nitro.prepare |
0.7 ms | 0.8 ms | +0.1 ms |
nitro.public-assets |
0.7 ms | 0.8 ms | +0.1 ms |
nitro.prerender |
0.5 ms | 0.5 ms | 0.0 ms |
nitro.bundle |
1.38 s | 1.38 s | -7.8 ms |
nitro.cache.write |
0.4 ms | 0.4 ms | 0.0 ms |
vercel.workflow-function.materialize |
25.7 ms | 26.4 ms | +0.7 ms |
agent-summary.emit |
0.5 ms | 0.5 ms | 0.0 ms |
nitro.close |
0.1 ms | 0.1 ms | 0.0 ms |
output.publish |
3.7 ms | 3.5 ms | -0.2 ms |
workspace.remove |
2.2 ms | 2.1 ms | -0.1 ms |
046d41d to
d7cbbcc
Compare
| }); | ||
| ``` | ||
|
|
||
| `ctx.model` is the parent's effective model when the resolver runs. This child |
There was a problem hiding this comment.
maybe ctx.parent.model is better?
There was a problem hiding this comment.
i like that a lot better for subagents, but this is getting exposed for all dynamic resolvers. in the case that it's a tool getting resolved, it would be the "owning" agent. is it correct to call that a parent?
There was a problem hiding this comment.
Good point. Weird that it has different meaning in different places though. In dynamic agent I would assume it is this agents model
d7cbbcc to
1e20a88
Compare
Signed-off-by: prha <prha@vercel.com>
1e20a88 to
a449bb0
Compare
Summary
Closes #2300. Related to #626. Dynamic capability resolvers need to compose with the model eve would use if they made no change; they now receive that serializable value as
ctx.model.The API deliberately calls this the effective model rather than the active model. “Active” suggests a mutable, cached record of the last selection, while “effective” names a value derived at read time from the same precedence the harness uses: step, turn, session, static model, then
null. Model resolvers see that precedence with their own event scope excluded, while other resolvers see the model selected earlier in the same event, avoiding feedback loops and drift between resolver context and the model call.Checklist
CONTRIBUTING.mdevepackagegit commit --signoff)Diff size
Docs — 3 files ·
+26 / -10Documents
ctx.modelthrough the dynamic subagent inheritance example and includes release metadata for the new resolver context field.Implementation — 12 files ·
+114 / -49Centralizes effective-model precedence in one derivation shared by resolver context and the harness. This category also includes the required producer-epoch bumps and generated extension contract metadata for the four affected capability surfaces.
Tests — 14 files ·
+207 / -23Covers precedence, the dynamic-only
nullcase, model-resolver scope exclusion, and visibility across resolver kinds. Four retained compatibility fixtures prove extensions authored against the previous resolver context continue to compile; the mounted-extension scenario tracks the new producer epoch.