Cloudflare adds a way to run Exo agents on its infrastructure
A new, independently maintained adapter lets Exo, a self-hostable agent harness, run on Cloudflare using Durable Objects for coordination and Sandboxes for tool execution, with no Agents SDK required.
Cloudflare published a changelog entry on 9 November for a new way to deploy Exo agents on its platform. Exo is an open-source, self-hostable agent harness: Durable Objects now coordinate the conversation, and Cloudflare Sandboxes run the Linux tools the agent calls.
The adapter is maintained by the Exo project itself, not Cloudflare, and the changelog is explicit that it doesn’t require the Agents SDK. You define an agent in a Markdown file with frontmatter for the harness type and model:
---
harness: basic
model:
name: gpt-6.1-sol
credential: openai
---
Help the user with their task.Then run it with exo --provider cloudflare agent run --agent-file agent.md.
Why it matters: this gives Exo users a hosted path that doesn’t involve standing up their own servers for conversation state, while keeping them off Cloudflare’s own Agents SDK if they’d rather not adopt it. For Cloudflare, it’s another sign that Durable Objects and Sandboxes are becoming the default building blocks for third-party agent frameworks, not just Cloudflare’s own.
The caveat: the adapter sits outside Cloudflare’s own support surface, so bugs and breaking changes in it are the Exo project’s to fix, not Cloudflare’s.