A bot for each job.
Give each bot its own instructions, model, and skills. Start as many conversations as the work needs. Bots can ask one another for help.
OPEN SOURCE / SELF-HOSTEDPublic preview ↗
Give your agents
a computer.
A name. A job. A browser of their own.
Put OpenCode to work in
a workspace you host—and take the conversation with you.
OpenCode
01 / A WORKSPACE FOR DOINGIllustrative conversation
Scout / The weekend field
guide↗
YOU 09:41
Make a little website for our weekend in the Catskills. Ask Builder to put it together.
SCOUT 09:41
I’ll collect the stops and ask Builder to turn them into a field guide.
↳ Browse sources 3 pages read
BBuilderFinished
The guide is ready. Opening it in our browser.
↳ Open page weekend-guide.html
Ready when you are. Take a look →
Message Scout… ↑
localhost / weekend-guide
FIELD NOTES Nº 024
A little
further
upstate.
THE CATSKILLSA WEEKEND GUIDE ↗
The browser your bots actually control.
Follow the conversation, the handoff, and the browser in one
place.YOUR INFRASTRUCTURE. YOUR VIEW.
02 / THE TOOLKIT
More than a chat window.
OpenCode does the work. Bot gives it a place to live.
Watch the work happen.
Read tool calls as they happen. Expand the shared browser. Review approvals, send a follow-up mid-turn, or stop a task.
Choose what’s underneath.
Connect model providers and API keys. Use OpenCode commands, install skills, and configure plugins for the way you work.
Bring the conversation along.
Chat on the web or connect a Telegram bot. Pair another client with a code or QR. Native iOS and Android clients are in preview.
Files belong in the workflow.
Attach a reference image or document. Browse the Computer’s folders, preview text, and upload or download the finished work.
Let your tools talk to it.
Connect an external agent through authenticated MCP. List bots, start tasks, and follow results without opening another chat window.
MCP setup ↗
03 / MAKE YOURSELF AT HOME
Hosted by you.
Hosted by you.
Reached from anywhere.
Start with a Computer on your Cloudflare account. Add a Mac, Linux machine, or Windows computer with the node installer and a pairing token.
One workspace connects your bots and trusted clients. Revoke a paired device when it’s no longer yours.
Meet the node system ↗One command to get started.
The installer deploys to your Cloudflare account and opens your
workspace.
No local Docker. No Docker Hub account.
BASH / macOS · Linux · Windows via WSL2Read the script ↗
curl -fsSL
https://raw.githubusercontent.com/pkyanam/opencode-bot/main/install.sh
| bash
Before you begin
Read the setup guide ↗
Bash, curl, Git, and a Cloudflare account with Workers Paid, Containers access, and R2 enabled. Setup installs Node.js 24+ when needed and prompts for Cloudflare login. Hosting and models are billed separately by their providers.
A few things worth knowing.
Is this an official OpenCode product?
No. OpenCode Bot is an independent, open-source project built on OpenCode. OpenCode’s name and logo belong to their respective owners.
What is ready today?
The web workspace, Telegram integration, model configuration, bot conversations, live Computer browser, file tools, pairing, and MCP are available in the public preview. Native mobile is a development preview, not an App Store or Play Store release. Additional-node desktop streaming and native desktop packaging are still in development.
Where does my data live?
Your control server and artifacts live in your Cloudflare account; model requests go to your configured provider. Bots sharing a Computer also share its files, browser, and credentials. Cloudflare Sandbox disk is temporary: save checkpoints for recovery, and keep important files backed up. Checkpoints support compressed archives up to 2 GiB on Cloudflare.
Can I update or remove it?
Updates are available in Settings after you configure deployment access. The setup utility also includes an uninstaller with a resource preview before deletion.
Uninstall instructions ↗