cf-opencode runs OpenCode in a cloud workspace. You deploy it into your own Cloudflare account. No hosted service is involved.
A workspace is a container with your repository, your tools and an OpenCode server. Your local OpenCode connects to it.
What you get
- Work that continues without your laptop. The agent runs in the workspace. Close the lid and the task goes on.
- No cost while idle. An idle workspace saves its disk to a snapshot and stops. The next connect restores it.
- No model keys. Models come from your account through the Workers AI and AI Gateway bindings.
- Private repositories. The GitHub token stays in the Worker. It never enters the workspace.
- Shell, SSH and browser access. You can open a terminal, use
ssh, or give the agent a browser. - Hand off a task.
cf-opencode rungives a task to the agent and returns.cf-opencode tasksshows the result. An agent on your machine can do the same over MCP, and another agent can use A2A. - Preview a dev server.
cf-opencode preview 3000opens a dev server of the workspace athttp://localhost:3000. Nothing is public. - Skills.
cf-opencode skillscopies your skills into a workspace. - Web search and page reading. The agent searches the web and reads pages with no key.
- Messages.
cf-opencode notify-urlsends the result of a task to a URL that you own.
How you use it
Install once:
npx cf-opencode initThen, from any git checkout:
npx cf-opencode connectconnect wakes or creates the workspace for that checkout. It then opens your local OpenCode against it.
Where to go next
- Quickstart installs cf-opencode and opens a first workspace.
- How it works explains the parts and the workspace life cycle.
- CLI reference lists every command and flag.
- Hand off a task gives work to the agent and closes the laptop.
- Troubleshooting explains the
Failed:errors. - Limits and costs lists what a workspace cannot do and what it costs.
The control plane is a fork of the cf-orbs project. The source is at github.com/meirdick/cf-opencode.