Signals
Cloudflare Turns OpenCode Into a Coding Agent That Survives Eviction
Published October 15, 2026Update Released Oct 12, 2026
Before, hosting a long-running coding agent on serverless meant building your own session storage and crash recovery. Cloudflare's experimental OpenCodeHarness runs OpenCode 2.0 inside a single Durable Object that saves sessions and wakes interrupted work on its own, so a hosted coding agent is now a small amount of Worker code.
What Changed
- A full coding agent, OpenCode 2.0, now runs inside one plain Durable Object through the Agents SDK OpenCodeHarness (Agents SDK 0.28.0+).
- Sessions live in the Durable Object's SQLite storage, and Lifecycle integration wakes interrupted work after eviction, so a long task resumes instead of dying.
- Models come from Workers AI through the AI binding, and plugins add your own tools, remote MCP servers, and skills.
Who Should Care
- Builders who want to offer a hosted coding agent per user or per repo without running containers or a job queue.
- Teams already on Workers and Workers AI who have been hand-rolling agent session persistence and retry logic.
- Platform teams evaluating where background coding agents should live.
Who Should Not Care
- Developers who run OpenCode or another coding agent locally and are happy there.
- Teams not on Cloudflare, or tied to frontier models outside Workers AI.
- Anyone who needs a stable production contract today; the harness is experimental.
The Verdict
If you want to host coding agents for users, prototype on OpenCodeHarness now: durable sessions and resume after eviction are the hard parts, and they come built in. Keep it out of production until the API leaves experimental status.
Take This To Your Agent
Copy a ready-to-paste investigation handoff that asks your coding agent to check this update against your product and recommend what to do next.