Is Oyster for you?
Agents can work on Computers and build Apps on Oyster. See when that is useful, and when Cloudflare Workers Builds is the simpler choice.
Start with the Computer
Section titled “Start with the Computer”You want an agent to work on files, run commands and make Apps people can open. On a deployed Oyster, an owner can attach a Computer to an agent. The agent can then use the files and execution it has been granted. The starter setup also uses one Computer to build Apps from git commits. Attaching a Computer does not create a private Computer for every agent.
Oyster puts a desktop around that work. Grove holds agent conversations, Bonsai
holds git repositories, Shed opens a terminal and Inkcap edits files. People use
installed Apps in a browser. Agents call App methods through one /mcp
endpoint, with their own keys. The copied Oyster Worker includes owner-only
POST /api/keys for issuing those keys.
Oyster might fit if you want to run that App and agent platform on your
Cloudflare account, fork the starter Apps or build Apps your agents can call.
The oyster install-apps command builds and installs seven starter Apps. It
builds two at a time by default on the setup’s Computer.
It might not fit if your whole job is to build and deploy one Worker when you push to Git. You don’t need an App desktop or an agent’s Computer for that.
Oyster or Workers Builds?
Section titled “Oyster or Workers Builds?”| Your job | Oyster 0.5.0 | Cloudflare Workers Builds |
|---|---|---|
| Ship code from Git | Builds App Releases from git commits on your Oyster’s Computer, then installs them into its App host. | Connects a Worker to Artifacts, GitHub or GitLab. A push triggers a build, then deployment or a branch Preview. |
| Give an agent a workspace | An owner can attach a Computer to an agent. Agents with access can use its files and commands alongside installed Apps. | Builds is a Worker build and deployment workflow, not a ready-made agent workspace. You can build your own agent software on Cloudflare. |
| Open the result | People open Apps in Oyster’s desktop; agents call them over /mcp with a key. |
Opens your deployed Worker. Non-production branches can produce Preview URLs. |
Workers Builds is Cloudflare’s CI/CD path for a Worker. Its build and deploy commands are configurable. Oyster is a platform you operate on Cloudflare; it does not replace Cloudflare’s CI/CD service. You can use both.
Try it before you decide
Section titled “Try it before you decide”The
local Oyster quickstart
runs one small App under wrangler dev. You need Node 24, pnpm 11, Git, curl
and openssl, but not Docker or a Cloudflare account for that local trial. That
trial has no Computer, git storage or Workers AI. To build starter Apps on a
Computer, follow the deployment guide.
That needs Cloudflare Workers Paid and Docker.
The live Oyster requires an Oyster key. It is not an anonymous demo.
Roadmap, not available today: a public no-key Oyster demo. The own-server guide is still a draft; running Oyster on your own server does not remove the Cloudflare Artifacts requirement for git. For now, start with the local trial or deploy Oyster on your Cloudflare account.