---
type: "post"
id: "making-every-harness-durable-analysis-9f2d73"
slug: "making-every-harness-durable-analysis-9f2d73"
title: "Making every harness durable"
description: "**Thesis:** Durable execution is becoming an adapter-layer property of coding-agent harnesses, rather than a feature each harness must implement alone."
retrieval_nugget: "**Thesis:** Durable execution is becoming an adapter-layer property of coding-agent harnesses, rather than a feature each harness must implement alone."
published_at: "2026-10-20"
updated_at: "2026-10-20"
record_date: "2026-10-20"
date_kind: "published_at"
topics: ["agent-harness","coding-agents","harness-engineering"]
source_urls: ["https://vercel.com/blog/making-every-harness-durable"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:making-every-harness-durable-analysis-9f2d73"
status: "published"
visuals: []
editorial_provenance: {"schema_version":"newruntime-editorial-copy-v1","content_status":"source_grounded_final","final_copy_sha256":"sha256:baef26163d9a0dc4983346f3238420d6c667a8b6c4344357d24bd70022af1589","reviewed_at":"2026-10-20T22:00:52.283Z","source_evidence_count":1,"verified_claim_count":3,"site_analysis_schema_version":"newruntime-site-analysis-v1","site_object_kind":"field_note","observed_fact_count":3,"implication_count":2,"watch_condition_count":1,"related_record_count":0}
analysis: {"schema_version":"newruntime-site-analysis-v1","object_kind":"field_note","thesis":"Durable execution is becoming an adapter-layer property of coding-agent harnesses, rather than a feature each harness must implement alone.","observed_facts":[{"text":"Vercel says durable-harness supports Pi, OpenCode, Codex, and Claude Code without changing the harness itself.","source_urls":["https://vercel.com/blog/making-every-harness-durable"]},{"text":"The package records intent and outcomes for model and tool calls in a durable log, with a queue that lets a replacement function resume after failure.","source_urls":["https://vercel.com/blog/making-every-harness-durable"]},{"text":"The announcement describes safe and never replay policies for tools, and hosted, local, and self-hosted World backends.","source_urls":["https://vercel.com/blog/making-every-harness-durable"]}],"mechanism":"A durable log records call intent and result, while a queue restarts interrupted turns; tool replay labels distinguish safe retries from potentially completed side effects that require checking.","why_now":"Vercel describes cloud coding-agent sessions lasting minutes or hours and argues that cloud compute alone does not preserve call completion state or resume interrupted turns.","implications":["Teams can assess crash recovery as an adapter around an existing harness rather than adopting a new harness.","Reliability still depends on choosing and implementing tool replay policies correctly."],"evidence_boundary":"Claims and architecture are described in Vercel's announcement; no independent reliability evaluation or general exactly-once guarantee is provided.","watch_conditions":["Whether deployments show logs and replay policies avoiding duplicated or lost work after crashes, especially for external side effects."],"related_records":[],"new_branch_reason":"No prior New Runtime record was supplied; this release warrants a distinct record on durable execution adapters for coding-agent harnesses."}
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/making-every-harness-durable-analysis-9f2d73/","markdown":"https://newruntime.com/posts/making-every-harness-durable-analysis-9f2d73.md","json":"https://newruntime.com/posts/making-every-harness-durable-analysis-9f2d73.json"}
related_patterns: ["harness-architecture-outlives-model-choice"]
---

# Making every harness durable

## Retrieval answer

**Thesis:** Durable execution is becoming an adapter-layer property of coding-agent harnesses, rather than a feature each harness must implement alone.

**Thesis:** Durable execution is becoming an adapter-layer property of coding-agent harnesses, rather than a feature each harness must implement alone.

Vercel says durable-harness works with Pi, OpenCode, Codex, and Claude Code without changing the harness itself. It records each step of a turn in a durable log, recording intent before model or tool calls and the outcome after completion. A queue backs the turn; when a function dies, a replacement reads the log and resumes from completed work. **Mechanism:** A durable log records call intent and result, while a queue restarts interrupted turns; tool replay labels distinguish safe retries from potentially completed side effects that require checking. The log distinguishes completed, in-progress, and not-yet-started calls; tool-level replay labels govern whether interrupted work can be retried or must be checked rather than repeated.

**Why now:** Vercel describes cloud coding-agent sessions lasting minutes or hours and argues that cloud compute alone does not preserve call completion state or resume interrupted turns. This release packages recovery for existing harnesses, and Vercel says the same interface can target its hosted backend, local files, or self-hosted storage such as Postgres. **First implication:** Teams can evaluate durability as a layer around a chosen harness, instead of treating a harness migration as the prerequisite for crash recovery. Teams can assess crash recovery as an adapter around an existing harness rather than adopting a new harness.

**Evidence boundary:** Claims and architecture are described in Vercel's announcement; no independent reliability evaluation or general exactly-once guarantee is provided. These are capabilities and deployment options described by Vercel; the announcement is not an independent reliability evaluation, and it does not establish exactly-once behavior for arbitrary external side effects. Tool policies and integration determine recovery behavior. **First watch condition:** Whether deployments show logs and replay policies avoiding duplicated or lost work after crashes, especially for external side effects. Whether real deployments report that replay policies and durable logs prevent duplicated or lost work across crashes, particularly for tools with external side effects.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Agent Harness](https://newruntime.com/topics/agent-harness.md): Explore the agent-harness topic hub.
- topic hub: [Coding Agents](https://newruntime.com/topics/coding-agents.md): Explore the coding-agents topic hub.
- topic hub: [Harness Engineering](https://newruntime.com/topics/harness-engineering.md): Explore the harness-engineering topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)