agent-framework durable-workflows multi-channel state-management open-source

Vercel Eve separates agents from communication channels

Eve's filesystem-first architecture decouples agent reasoning from platform transport—write once, expose via HTTP, Slack, Discord, or custom webhooks without conditional logic.

June 24, 2026

Summary

Eliminates boilerplate for multi-channel agent deployment and enforces durable session persistence by default, reducing crash-recovery complexity from scratch-built state management.

Why it matters

Eliminates boilerplate for multi-channel agent deployment and enforces durable session persistence by default, reducing crash-recovery complexity from scratch-built state management.

Implementation verdict

Replaces custom agent scaffolding and session handling. Requires Node.js runtime and pluggable backend selection (local files → Postgres/Redis/Vercel Workflow). Ready to try now for greenfield agents; integration complexity depends on existing channel requirements.

Sources

1.Eve draws a hard line between what the agent is and how it communicates
2.Sessions survive server restarts and support reconnection at any event index (?startIndex=N)
3.Eve checkpoints progress at each step boundary (one model call + its tool calls = one step)
4.You can: Start a conversation, ask the agent something / Kill the server (Ctrl+C) / Restart it / Continue the conversation with the same sessionId and continuationToken
5.The World interface has three responsibilities: Storage (persisting runs, steps, hooks via an append-only event log), Queue (dispatching workflow/step invocations with at-least-once delivery), and Streams (real-time event delivery to clients)

Dev Signal

Get briefs like this in your inbox — free, every weekday.

100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.

Read the full issue →All briefs