Vercel Open-Sources durable-harness for Crash-Proof Coding Agents

Vercel Open-Sources durable-harness for Crash-Proof Coding Agents


Vercel has released durable-harness, an open-source package that keeps coding agent sessions alive through crashes and timeouts. It wraps existing harnesses β€” including Pi, OpenCode, Claude Code, and Codex β€” without modifying them. Each session lives in a durable log, so a dead function no longer means lost work. For teams moving agents off laptops and into the cloud, that closes a real, long-standing gap.


TL;DR


  • Size: npm package, version 0.0.x, Apache-2.0. Adapters cover five harnesses: Pi, OpenCode, fx, Claude Code, and Codex.
  • Runs on: Vercel Functions plus Vercel Queues, Node.js 22+ with Postgres, or local laptop files. Claude Code and Codex require a Vercel Sandbox.
  • Performance: No latency or throughput benchmarks have been published. All recovery claims are self-reported by Vercel.
  • Best: Completed model and tool calls are read back from the log β€” never re-run or billed twice.
  • Worst: Experimental 0.0.x API. Claude Code and Codex run only in a Vercel Sandbox, even when self-hosted.

What Is durable-harness?


durable-harness is a set of adapters from Vercel that store a harness session in a Workflow SDK World. A World bundles storage, a queue, and a stream behind a single interface. The package reuses the same machinery that powers Vercel's Workflow SDK.


Why Do Coding Agents Lose Work in the Cloud?


Harnesses like Pi and Claude Code were designed as long-lived local processes, keeping the session in memory. Locally, the workspace and history sit on the same disk, so a process death is the only real failure mode. Cloud execution changes the calculus: serverless functions time out, instances are reclaimed, and execution is distributed across ephemeral workers. In 2026, as more teams push long-running agentic coding workloads into serverless and edge environments, these interruptions have become a routine operational cost rather than an exception.


durable-harness addresses this by decoupling session state from the process. By persisting every model call, tool invocation, and intermediate result to a durable log, it lets a new worker resume exactly where the previous one left off β€” without repeating completed steps or incurring duplicate costs.


What's Next


With agent frameworks maturing rapidly in 2026 and enterprise adoption of coding agents accelerating, durable execution is shifting from a nice-to-have to a baseline requirement. Vercel's move to open-source the adapters under Apache-2.0 lowers the barrier for other harness maintainers to adopt the pattern. However, the experimental 0.0.x status and the Vercel Sandbox requirement for Claude Code and Codex suggest the package is still best suited for early adopters willing to accept some platform coupling in exchange for crash-proof reliability.

via MarkTechPost

Related