Agent with Vercel's Eve Framework

Vercel recently open-sourced . Eve checkpoints progress at each step boundary (one model call + its tool calls = one step). If the process crashes mid-turn, it resumes from the last completed step rather than replaying everything.

Locally, this is just files on disk. Run your agent and you'll find a .workflow-data/ directory:

.workflow-data/

├── runs/       # one JSON file per session (workflow state)

├── steps/      # checkpoint per completed step

├── streams/    # event streams (what clients read via /stream)

├── hooks/      # parked continuation tokens (waiting for input)

└── events/     # workflow lifecycle events

This means you can:

1. Start a conversation, ask the agent something


2. Kill the server (Ctrl+C)


3. Restart it


4. Continue the conversation with the same sessionId and continuationToken
   

The session picks up exactly where it left off — including mid-turn recovery if a step was already completed before the crash.

Obviously, local files aren't scalable for production. Eve's durability is pluggable via the if none of the existing options fit.

Example: Exposing the Agent as AG-UI

To make this concrete — I built a custom channel that exposes the Eve agent over the

Please feel free to reach out on twitter @roamingcode