Skip to content

feat(eve): add periodic activity refreshes - #3347

Open
benpankow wants to merge 1 commit into
mainfrom
benpankow/activity-render-refresh
Open

benpankow wants to merge 1 commit into
mainfrom
benpankow/activity-render-refresh

Conversation

@benpankow

@benpankow benpankow commented Sep 14, 2026

Copy link
Copy Markdown
Collaborator

Summary

Activity renderers currently update only when a new activity event arrives, so time-based presentation becomes stale during long-running work. This adds an opt-in activity.periodicRefreshIntervalMs for Slack channels, which re-renders active snapshots on a durable timer alongside the existing event-driven renders and stops refreshing once activity settles.

slackChannel({
  activity: {
    periodicRefreshIntervalMs: 5_000,
    renderers: [experimental_slackActivityRenderer(renderer)],
  },
});

Validation

Adds unit coverage for periodic refreshes, settlement with an outstanding timer, interval validation, and propagation into the collector workflow. Ran pnpm build, pnpm test, pnpm typecheck, pnpm lint, pnpm fmt, pnpm guard:invariants, and pnpm docs:check.

Signed-off-by: benpankow <ben.pankow@vercel.com>
@vercel

vercel Bot commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

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

Project Deployment Actions Updated
eve-docs Ready Ready Preview, v0 Sep 14, 2026 6:57pm UTC
eve-docs-4759 Ready Ready Preview, v0 Sep 14, 2026 6:57pm UTC
eve-pkg Ready Ready Preview, v0 Sep 14, 2026 6:57pm UTC

@github-actions

Copy link
Copy Markdown
Contributor

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

Key takeaways

  • No notable deltas vs main (15c7a2e).

Delta vs main (15c7a2e)

Area Metric Baseline Current Delta
Package Packed tarball 8.75 MB 8.75 MB -487 B ✅
Package Unpacked publish size 32.92 MB 32.92 MB +2.4 kB ⚠️
Package Installed footprint 78.53 MB 78.53 MB +2.4 kB ⚠️
Package Published files 3989 3989 0
Package Installed files 7910 7910 0
Package Installed package instances 33 33 0
Package Distinct installed package names 32 32 0
Package Installed dependency edges 51 51 0
Package Installed optional peer edges 8 8 0
Runtime Unique function payloads 2 2 0
Runtime Total function bytes 20.70 MB 20.71 MB +6.7 kB ⚠️
Runtime Public routes 18 18 0
Changed function payloads vs main (15c7a2e) (2)
Function Status Baseline Current Delta Route changes
functions/__server.func changed 10.35 MB 10.36 MB +3.3 kB ⚠️ none
functions/.well-known/workflow/v1/flow.func changed 10.35 MB 10.36 MB +3.3 kB ⚠️ none

eve init install

Metric Baseline Current Delta
Installed footprint 116.62 MB 116.62 MB +2.4 kB ⚠️
Installed packages 113 113 0
dependencies 4 4 0
devDependencies 2 2 0
Dependency package bytes 49.15 MB 49.16 MB +2.4 kB ⚠️
devDependency package bytes 5.04 MB 5.04 MB 0 B ➖
Build Metadata
  • Preset: vercel
  • Nitro: nitro@3.0.260903-beta
  • Output directory: apps/fixtures/weather-agent/.vercel/output
  • Build metadata timestamp: 2026-09-14T18:57:54.330Z
  • Route aliases: 18 public, 1 internal (19 total aliases)
  • Vercel routes in config: 21
  • Severity legend: 🔴 dominant/large, 🟠 notable, 🟡 watch, ⚪ small
Package Drill-Down

Package Details

  • Package: eve@0.54.5
  • Package directory: packages/eve
  • Tarball: 8.75 MB (eve-0.54.5.tgz)
  • Unpacked payload: 32.92 MB across 3989 published files
  • Installed footprint: 78.53 MB across 7910 installed files
  • Installed root package: 31.49 MB
  • Installed dependencies: 47.04 MB
  • Installed package instances: 33
  • Distinct installed package names: 32
  • Installed dependency edges: 51
  • Installed optional peer edges: 8
  • Runtime dependencies: 2
  • Peer dependencies: 6 (5 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: 31.49 MB (40.1%)
  • @rolldown/binding-linux-x64-gnu: 19.31 MB (24.6%)
  • ai: 7.13 MB (9.1%)
  • zod: 6.76 MB (8.6%)
  • undici: 3.51 MB (4.5%)
Publish payload breakdown
Published file size
🔴 dist/src/compiled/shadcn-registry/index.js       [#############...........] 9.76 MB 29.6%
🟠 dist/src/compiled/@photon-ai/chat-adapter-ime... [###.....................] 2.27 MB 6.9%
🟠 dist/src/compiled/@ai-sdk/code-mode/index.js     [#.......................] 1.03 MB 3.1%
🟡 dist/src/compiled/@vercel/blob/index.js          [#.......................] 901.4 kB 2.7%
🟡 dist/src/compiled/_chunks/workflow/signal-exi... [#.......................] 514.6 kB 1.6%
🔴 Other published files                            [########################] 18.45 MB 56.0%
Installed footprint breakdown
Installed package size
🔴 eve                             [########################] 31.49 MB 40.1%
🔴 @rolldown/binding-linux-x64-gnu [###############.........] 19.31 MB 24.6%
🔴 ai                              [#####...................] 7.13 MB 9.1%
🔴 zod                             [#####...................] 6.76 MB 8.6%
🟠 undici                          [###.....................] 3.51 MB 4.5%
🟠 nitro                           [#.......................] 1.89 MB 2.4%
🔴 Other installed packages        [######..................] 8.44 MB 10.7%
Runtime dependencies (2)
Package Range Notes
nitro 3.0.260903-beta
undici 8.9.0
Peer dependencies (6)
Package Range Notes
@opentelemetry/api ^1.0.0 optional peer
ai catalog:
braintrust ^3.0.0 optional peer
dd-trace ^6.13.0 optional peer
just-bash ^3.1.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: 116.62 MB across 9794 installed files
  • Installed packages: 113 total (107 transitive-only)
  • dependencies: 4 direct packages totaling 49.16 MB
  • devDependencies: 2 direct packages totaling 5.04 MB
  • Other transitive package files: 62.43 MB

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

Heavy installed dependencies

  • eve: 31.49 MB (27.0%)
  • @typescript/typescript-linux-x64: 27.95 MB (24.0%)
  • @rolldown/binding-linux-x64-gnu: 19.31 MB (16.6%)
  • zod: 10.37 MB (8.9%)
  • ai: 7.13 MB (6.1%)
Installed footprint breakdown
Installed package size
🔴 eve                              [########################] 31.49 MB 27.0%
🔴 @typescript/typescript-linux-x64 [#####################...] 27.95 MB 24.0%
🔴 @rolldown/binding-linux-x64-gnu  [###############.........] 19.31 MB 16.6%
🔴 zod                              [########................] 10.37 MB 8.9%
🔴 ai                               [#####...................] 7.13 MB 6.1%
🟠 undici                           [###.....................] 3.51 MB 3.0%
🔴 Other installed packages         [#############...........] 16.87 MB 14.5%
dependencies (4)
Package Range Installed size Share
@vercel/connect 1.0.0 167.9 kB 0.1%
ai ^7.0.93 7.13 MB 6.1%
eve file:eve-0.54.5.tgz 31.49 MB 27.0%
zod 4.5.4 10.37 MB 8.9%
devDependencies (2)
Package Range Installed size Share
@types/node 24.x 2.54 MB 2.2%
typescript 7.0.2 2.50 MB 2.1%
Function Drill-Down

Payload Size Graph

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

Top Function Payloads

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

🟠 🔎 Dependency Analysis

📦 Bundled files:

Bundled file size
🟠 index.mjs                        [###########.............] 2.24 MB 21.6%
🟡 _libs/undici.mjs                 [#####...................] 980.8 kB 9.5%
🟡 _chunks/esm-Fqlolk7e.mjs         [###.....................] 723.3 kB 7.0%
🟡 _chunks/chatgpt-model.mjs        [###.....................] 699.6 kB 6.8%
🟡 _chunks/signal-exit-Dsy-TT0V.mjs [###.....................] 616.2 kB 6.0%
🔴 Other bundled files              [########################] 5.10 MB 49.2%

🧾 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 • 17 public routes, 1 internal alias • 10.36 MB
Metric Value
Public routes /
/.well-known/workflow/v1/webhook/[token]
/eve/v1/activity/[token]
/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 10.36 MB
Function files 10.36 MB across 115 files
Traced dependencies 0 B
Signal 🟠 Bundled file index.mjs is 2.24 MB (21.6%)

🟠 🔎 Dependency Analysis

📦 Bundled files:

Bundled file size
🟠 index.mjs                        [###########.............] 2.24 MB 21.6%
🟡 _libs/undici.mjs                 [#####...................] 980.8 kB 9.5%
🟡 _chunks/esm-Fqlolk7e.mjs         [###.....................] 723.3 kB 7.0%
🟡 _chunks/chatgpt-model.mjs        [###.....................] 699.6 kB 6.8%
🟡 _chunks/signal-exit-Dsy-TT0V.mjs [###.....................] 616.2 kB 6.0%
🔴 Other bundled files              [########################] 5.10 MB 49.2%

🧾 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: 5.02 s -> 4.83 s (-193.3 ms) vs main (15c7a2e).
  • Timing is informational: shared GitHub runners are too variable for a hard timing budget.
Detailed phase timings vs `main (15c7a2e)`
Phase Baseline Current Delta
extension.check 0.6 ms 0.6 ms 0.0 ms
project.resolve 0.2 ms 0.3 ms +0.1 ms
workspace.create 0.4 ms 0.5 ms +0.1 ms
host.prepare 425.7 ms 476.2 ms +50.5 ms
vercel.service-prefix.resolve 1.4 ms 1.6 ms +0.2 ms
nitro.create 497.1 ms 451.6 ms -45.5 ms
sandbox.prewarm 383.4 ms 335.3 ms -48.1 ms
nitro.cache.prepare 0.2 ms 0.2 ms 0.0 ms
nitro.prepare 0.6 ms 0.6 ms 0.0 ms
nitro.public-assets 0.6 ms 0.6 ms 0.0 ms
nitro.prerender 0.4 ms 0.4 ms 0.0 ms
nitro.bundle 3.49 s 3.49 s +0.2 ms
nitro.cache.write 0.3 ms 0.2 ms -0.1 ms
vercel.workflow-function.materialize 57.8 ms 53.3 ms -4.5 ms
agent-summary.emit 0.5 ms 0.6 ms +0.1 ms
nitro.close 0.1 ms 0.1 ms 0.0 ms
output.publish 154.9 ms 8.7 ms -146.2 ms
workspace.remove 1.5 ms 1.5 ms 0.0 ms

snapshot,
});
rendererStates = rendered.rendererStates;
periodicRefresh ??= hasActiveActivity(snapshot)

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.

P2: Coalesce a refresh that expires during event debounce

If an active event arrives shortly before periodicRefresh resolves, the inner debounce race ignores that promise. The event-driven render then completes, this ??= retains the already-resolved refresh, and the next outer race immediately calls renderSessionActivityStep again for the same snapshot. Custom renderers can perform provider writes, so this can issue duplicate back-to-back mutations. Replace or consume the existing timer after the event-driven render, or include it in the debounce race, and add coverage for a refresh resolving between batch receipt and debounce completion.

Comment thread docs/channels/slack.mdx

The built-in `message.completed` handler renders responses up to 12,000 characters inline. Longer responses are uploaded unchanged as a Markdown snippet named `eve-response.md` with a short in-thread note, which requires the `files:write` bot scope. Upload failures are logged by the channel dispatcher; they do not trigger a model retry. An authored `events["message.completed"]` handler replaces this behavior and owns its own delivery limits.

Activity renderers update after activity events by default. Set `activity.periodicRefreshIntervalMs` to re-render active activity on a timer in addition to those event-driven renders. Periodic refreshes stop when the snapshot has no running work, running actions, or blocked input:

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.

P2: Name every blocker that keeps refreshes active

hasActiveActivity treats every blocked snapshot entry as active, while ActivityBlockerKind includes approval, authorization, and input. This sentence implies only blocked input keeps the timer alive, so readers can underestimate provider writes while an approval or authorization is pending. Please document that refreshes stop only when there is no blocked approval, authorization, or input request.

@benpankow
benpankow marked this pull request as ready for review September 14, 2026 19:26
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