Skip to content

feat(eve): memory - add first-class provider lifecycle - #1700

Open
AndrewBarba wants to merge 1 commit into
barba/research-memory-extension-apifrom
barba/first-class-memory
Open

feat(eve): memory - add first-class provider lifecycle#1700
AndrewBarba wants to merge 1 commit into
barba/research-memory-extension-apifrom
barba/first-class-memory

Conversation

@AndrewBarba

@AndrewBarba AndrewBarba commented Aug 5, 2026

Copy link
Copy Markdown
Collaborator

Description

Implements first-class memory end to end on the eve side. Agents can author one memory.ts slot or named memory/*.ts slots with a trusted scope resolver and a provider-owned lifecycle for compaction, turn preparation/completion, transient prompt context, and slot-qualified model tools.

The implementation carries memory through discovery, versioned manifests, compilation, module loading, root/subagent runtime resolution, durable workflow state, prompt/tool assembly, and provider-tool bundling. It intentionally ships no production storage provider; the integration suite uses a process-local Map to prove cross-session recall and principal isolation.

Stacked on #1581. Closes #1510.

How did you test your changes?

  • pnpm fmt
  • pnpm lint
  • pnpm typecheck
  • pnpm guard:invariants
  • pnpm test:unit (5,892 passed; 1 skipped)
  • pnpm test:integration (579 passed)
  • pnpm docs:check
  • pnpm --filter eve exec vitest run --config vitest.scenario.config.ts test/scenarios/compile-agent.scenario.test.ts (23 passed)

PR Checklist

  • I linked an issue with prior discussion confirming this change is wanted
  • I ran the relevant checks from CONTRIBUTING.md
  • I added tests and documentation where relevant
  • I added a changeset if this touches the published eve package
  • DCO sign-off passes for every commit (git commit --signoff)

@vercel

vercel Bot commented Aug 5, 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 Aug 5, 2026 10:10pm
eve-docs-4759 Ready Ready Preview, v0 Aug 5, 2026 10:10pm

@AndrewBarba AndrewBarba changed the title feat(eve): add first-class memory feat(eve): memory - add first-class provider lifecycle Aug 5, 2026
Signed-off-by: Andrew Barba <barba@hey.com>
@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

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

Key takeaways

  • No notable deltas vs barba/research-memory-extension-api (e705b4c).

Delta vs barba/research-memory-extension-api (e705b4c)

Area Metric Baseline Current Delta
Package Packed tarball 7.66 MB 7.66 MB +6.6 kB ⚠️
Package Unpacked publish size 28.69 MB 28.72 MB +34.0 kB ⚠️
Package Installed footprint 72.02 MB 72.05 MB +34.0 kB ⚠️
Package Published files 3036 3047 +11
Package Installed files 6735 6746 +11
Runtime Unique function payloads 2 2 0
Runtime Total function bytes 16.99 MB 17.02 MB +30.8 kB ⚠️
Runtime Public routes 13 13 0
Changed function payloads vs barba/research-memory-extension-api (e705b4c) (2)
Function Status Baseline Current Delta Route changes
functions/__server.func changed 8.49 MB 8.51 MB +15.4 kB ⚠️ none
functions/.well-known/workflow/v1/flow.func changed 8.49 MB 8.51 MB +15.4 kB ⚠️ none

eve init install

Metric Baseline Current Delta
Installed footprint 110.43 MB 110.46 MB +34.0 kB ⚠️
Installed packages 121 121 0
dependencies 4 4 0
devDependencies 2 2 0
Dependency package bytes 43.10 MB 43.14 MB +34.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-08-05T22:11:22.754Z
  • Route aliases: 13 public, 1 internal (14 total aliases)
  • Vercel routes in config: 16
  • Severity legend: 🔴 dominant/large, 🟠 notable, 🟡 watch, ⚪ small
Package Drill-Down

Package Details

  • Package: eve@0.30.8
  • Package directory: packages/eve
  • Tarball: 7.66 MB (eve-0.30.8.tgz)
  • Unpacked payload: 28.72 MB across 3047 published files
  • Installed footprint: 72.05 MB across 6746 installed files
  • Installed root package: 27.37 MB
  • Installed dependencies: 44.68 MB
  • Runtime dependencies: 2
  • Peer dependencies: 5 (4 optional)

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

Heavy installed dependencies

  • eve: 27.37 MB (38.0%)
  • @rolldown/binding-linux-x64-gnu: 19.35 MB (26.9%)
  • ai: 6.60 MB (9.2%)
  • zod: 5.07 MB (7.0%)
  • undici: 3.50 MB (4.9%)
Publish payload breakdown
Published file size
🔴 dist/src/compiled/shadcn-registry/index.js       [################........] 9.68 MB 33.7%
🟠 dist/src/compiled/@photon-ai/chat-adapter-ime... [####....................] 2.42 MB 8.4%
🟠 dist/src/compiled/experimental-ai-sdk-code-mo... [###.....................] 1.51 MB 5.2%
🟡 dist/src/compiled/_chunks/node/undici-DWL_MYm... [#.......................] 502.4 kB 1.7%
🟡 dist/src/compiled/_chunks/workflow/undici-DWL... [#.......................] 502.4 kB 1.7%
🔴 Other published files                            [########################] 14.11 MB 49.1%
Installed footprint breakdown
Installed package size
🔴 eve                             [########################] 27.37 MB 38.0%
🔴 @rolldown/binding-linux-x64-gnu [#################.......] 19.35 MB 26.9%
🔴 ai                              [######..................] 6.60 MB 9.2%
🔴 zod                             [####....................] 5.07 MB 7.0%
🟠 undici                          [###.....................] 3.50 MB 4.9%
🟠 nitro                           [##......................] 2.41 MB 3.3%
🔴 Other installed packages        [#######.................] 7.76 MB 10.8%
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: 110.46 MB across 8622 installed files
  • Installed packages: 121 total (115 transitive-only)
  • dependencies: 4 direct packages totaling 43.14 MB
  • devDependencies: 2 direct packages totaling 5.04 MB
  • Other transitive package files: 62.29 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 (25.3%)
  • eve: 27.37 MB (24.8%)
  • @rolldown/binding-linux-x64-gnu: 19.35 MB (17.5%)
  • zod: 9.02 MB (8.2%)
  • ai: 6.60 MB (6.0%)
Installed footprint breakdown
Installed package size
🔴 @typescript/typescript-linux-x64 [########################] 27.95 MB 25.3%
🔴 eve                              [########################] 27.37 MB 24.8%
🔴 @rolldown/binding-linux-x64-gnu  [#################.......] 19.35 MB 17.5%
🔴 zod                              [########................] 9.02 MB 8.2%
🔴 ai                               [######..................] 6.60 MB 6.0%
🟠 undici                           [###.....................] 3.50 MB 3.2%
🔴 Other installed packages         [##############..........] 16.67 MB 15.1%
dependencies (4)
Package Range Installed size Share
@vercel/connect 0.4.3 141.0 kB 0.1%
ai ^7.0.38 6.60 MB 6.0%
eve file:eve-0.30.8.tgz 27.37 MB 24.8%
zod 4.4.3 9.02 MB 8.2%
devDependencies (2)
Package Range Installed size Share
@types/node 24.x 2.54 MB 2.3%
typescript 7.0.2 2.50 MB 2.3%
Function Drill-Down

Payload Size Graph

Unique function payload size and share of total
🔴 functions/.well-known/workflow/v1/flow.func     [########################] 8.51 MB 50.0%
🔴 functions/__server.func                         [########################] 8.51 MB 50.0%

Top Function Payloads

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

🟠 🔎 Dependency Analysis

📦 Bundled files:

Bundled file size
🟠 index.mjs                       [#######################.] 2.33 MB 27.3%
🟠 _chunks/runtime-artifacts.mjs   [################........] 1.62 MB 19.0%
🟡 _libs/undici.mjs                [##########..............] 980.5 kB 11.5%
🟡 _chunks/sandbox.mjs             [########................] 769.0 kB 9.0%
🟡 _libs/@ai-sdk/gateway+[...].mjs [####....................] 432.8 kB 5.1%
🟠 Other bundled files             [########################] 2.38 MB 28.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 • 12 public routes, 1 internal alias • 8.51 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]/clear
/eve/v1/session/[sessionId]/compact
/eve/v1/session/[sessionId]/reset
/eve/v1/session/[sessionId]/stream
Internal aliases /__server
Runtime nodejs24.x
Handler index.mjs
Payload 8.51 MB
Function files 8.51 MB across 43 files
Traced dependencies 0 B
Signal 🟠 Bundled file index.mjs is 2.33 MB (27.3%)

🟠 🔎 Dependency Analysis

📦 Bundled files:

Bundled file size
🟠 index.mjs                       [#######################.] 2.33 MB 27.3%
🟠 _chunks/runtime-artifacts.mjs   [################........] 1.62 MB 19.0%
🟡 _libs/undici.mjs                [##########..............] 980.5 kB 11.5%
🟡 _chunks/sandbox.mjs             [########................] 769.0 kB 9.0%
🟡 _libs/@ai-sdk/gateway+[...].mjs [####....................] 432.8 kB 5.1%
🟠 Other bundled files             [########################] 2.38 MB 28.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: 1.99 s -> 2.24 s (+252.7 ms) vs barba/research-memory-extension-api (e705b4c).
  • Timing is informational: shared GitHub runners are too variable for a hard timing budget.
Detailed phase timings vs `barba/research-memory-extension-api (e705b4c)`
Phase Baseline Current Delta
extension.check 6.8 ms 8.6 ms +1.8 ms
project.resolve 1.4 ms 3.4 ms +2.0 ms
workspace.create 2.3 ms 1.3 ms -1.0 ms
host.prepare 175.6 ms 187.3 ms +11.7 ms
vercel.service-prefix.resolve 2.4 ms 2.2 ms -0.2 ms
nitro.create 206.7 ms 206.6 ms -0.1 ms
sandbox.prewarm 194.7 ms 412.1 ms +217.4 ms
nitro.cache.prepare 0.3 ms 0.2 ms -0.1 ms
nitro.prepare 0.9 ms 0.9 ms 0.0 ms
nitro.public-assets 0.8 ms 0.7 ms -0.1 ms
nitro.prerender 0.5 ms 0.5 ms 0.0 ms
nitro.bundle 1.37 s 1.39 s +20.5 ms
nitro.cache.write 0.4 ms 0.4 ms 0.0 ms
vercel.workflow-function.materialize 23.2 ms 23.8 ms +0.6 ms
agent-summary.emit 0.6 ms 0.5 ms -0.1 ms
nitro.close 0.1 ms 0.1 ms 0.0 ms
output.publish 3.3 ms 3.5 ms +0.2 ms
workspace.remove 2.2 ms 2.1 ms -0.1 ms

Comment on lines +991 to +1002
const memoryToolSet = buildToolSetFromDefinitions({
approvedTools,
capabilities: config.capabilities,
disabledProviderTools: opts.disabledProviderTools,
tools: buildMemoryTools(ctx),
});
for (const [name, toolDefinition] of Object.entries(memoryToolSet)) {
if (flatTools[name] !== undefined) {
throw new Error(`Memory tool "${name}" collides with another model-visible tool.`);
}
flatTools[name] = toolDefinition;
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need special handling for memory? Seems like memory tools can be expressed as defineDynamic

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.

First-class memory

2 participants