Vercel: eve 1.0 cuts median agent turn latency to 414 ms in mock-model test, from 3.04 s in beta
Vercel has released version 1.0 of eve, its open-source software for building AI agents. In the company’s mock-model test, median agent turn latency fell from 3.04 seconds to 414 milliseconds, but the figure excludes the model’s response time.
Vercel said in a blog post on 17 November that eve is now generally available, following a public preview that began in June. At eve’s core is a harness, the program that steers the agent: it gives the model its tools and runs its steps. In eve, the harness also hands work to subagents. The Workflow SDK saves the agent’s progress, so after a crash the agent picks up from its last completed step.
In a load test run on Vercel Workflows, median turn latency was 3.036 seconds with the early-September beta and 414 milliseconds with version 1.0, Vercel said. 95th-percentile latency fell from 3.692 seconds to 633 milliseconds.
The figure does not show how quickly the agent responds with a real model. The test sends 100 messages one at a time. A mock model answers each immediately, and the turns make no tool calls. Timing runs from sending a message until the turn finishes, so it captures only eve’s and Workflow’s own processing time. The model’s response time comes on top. eve’s GitHub repository contains a public load test in which one session completes 100 sequential turns.
The blog post also contradicts itself: a chart caption gives 1.0’s median as 626 milliseconds, while the table and text give 414.
Vercel attributed the speed-up to a change made with the Workflow team: each run now has a single orchestrator, so background steps no longer replay the workflow. Unnecessary history fetches were also cut. eve agents get these improvements through the Workflow SDK.
Vercel estimates that the Vercel Workflows cost of the 50-turn session it uses as an example falls from 5.4 cents to 1.3 cents, a drop of about 76 per cent. The estimate assumes roughly two model steps per turn and 30-day retention. It covers the workflow service, not model calls.
Other new features include shared multi-user sessions, Slack-style message channels, memory that persists across sessions and OpenTelemetry tracing.
Agents can be self-hosted or run on Vercel. Creating a new agent from the CLI requires Node.js 24 or newer. Vercel urges existing users to follow the 1.0 upgrade guide on eve.dev before deploying an updated agent, because the changes affect agent APIs and stored history, among other things.
Read more: How an agent works · Agent map