Cloudflare Computer: A Virtual Filesystem for Persistent AI Agents
Forum topic · ✨步子哥 · 2026-08-05
Summary
Cloudflare's trending "computer" project tackles a core flaw in today's AI agents: stateless execution. Once a task ends, the agent's working memory is lost, making long-running, multi-step workflows unreliable. Cloudflare Computer instead stores an agent's state inside a Durable Object backed by SQLite and exposes it as a virtual filesystem, letting agents read and write files the way human developers do. Execution is decoupled from state through three pluggable backends: a FUSE-mounted Linux Container for full OS access, a just-bash shell running inside a Worker for lightweight tasks, and a Dynamic Worker JavaScript backend for pure logic. This separation lets developers bring their own agent runtime while reusing Cloudflare's edge storage. Files also become a natural collaboration protocol between agents. The repository is preview-only and not production-ready, but signals a broader layered architecture emerging across agent runtimes, loop controllers, state layers, and skill libraries.
Key points
- Stateful agents via filesystem: Cloudflare Computer stores all agent working state inside a Durable Object, using SQLite as the source of truth and exposing it as a virtual filesystem. Agents persist context by writing files, eliminating the need for vector databases or RAG pipelines.
- Filesystem mirrors developer workflow: Code, configs, logs, TODOs, and intermediate artifacts are already the substrate of human programming. By giving agents the same substrate, Cloudflare reuses decades of Unix tooling (grep, find, make, git) instead of inventing AI-specific memory abstractions.
- Decoupled execution, three pluggable backends:
- Container backend: Mounts the SQLite-backed state via FUSE into a real Linux container for full binary, network, and userspace access.
- Isolate shell backend: Runs
just-bash (a pure-JS bash) inside a Cloudflare Worker, accessing state via RPC for fast, low-overhead execution.
- Isolate JavaScript backend: Executes an ECMAScript module in a Dynamic Worker with structured I/O, a
node:fs/promises polyfill, and trusted ws:git / ws:artifacts modules.
A single Workspace can register multiple backends; workspace.runtime.exec(source, { backend }) is the unified entry point.
- Shared protocol for multi-agent collaboration: Files double as a collaboration medium. One agent's code, logs, or data become directly readable by another agent, removing the need for bespoke messaging protocols.
- Edge-native persistence: Durable Objects run across 300+ Cloudflare edge locations with automatic persistence and low latency, so agents remain warm and quickly wakeable rather than sitting idle on GPU clusters.
- Preview status: The README flags the project as PREVIEW ONLY — the API is unstable and not production-ready. Much of the documentation describes intended design rather than current implementation.
- Layered agent stack emerging: The post frames a four-layer architecture now developing independently:
1. Runtime layer — Codex, Claude Code, Cursor.
2. Loop control layer — projects like loopx.
3. State layer — Cloudflare Computer.
4. Skills layer — repositories like addyosmani/agent-skills.
Filesystem is positioned as the common protocol tying these layers together.Project facts
- Repository: github.com/cloudflare/computer
- Language: TypeScript
- Momentum: 796 stars in one day at time of writing
- Related Cloudflare project: github.com/cloudflare/agents (agent deployment framework)
- Related loop-control project: github.com/huangruiteng/loopx
This page is an English static mirror generated for search and AI citation.
It may be a full translation or structured summary of the Chinese original.
Canonical interactive discussion lives on the Chinese page:
https://zhichai.net/topic/178595035