Coshell is built on OpenCode, compatible through v1.17.10. OpenCode is the agent engine. Coshell adds the layer between the people.
OpenCode makes one person work with the agent.Coshell makes the whole team work with the agent, together.
OpenCode gives you the agent. Coshell gives that agent to your whole team, hosted and live. Every line below is a layer OpenCode does not ship, and every one is running in production today.
A drive is a workspace that stays warm in the cloud, with your files, terminal, and dependencies ready. Open it from any device.
Several people prompt one agent in one live session at once, watching the same work land on the same running environment.
When two agents reach for the same lines of the same file, an overlap layer catches it and holds the second edit before it clobbers, steering that agent to proceed if the changes are compatible, or to take other lines, wait, or let the first land first.
Keep a session private to you, share it with named teammates, or open it to the whole drive. Your call, per session.
Every action is tied to a verified identity that cannot be spoofed. Credentials are scoped to a single drive, with no master key to steal.
Run your app and see its localhost preview inside the session, shared with everyone on the drive, auto-reloading as the agent works.
Log in once from your terminal with a device code, then attach to any drive by name. The same login, the same drives, everywhere.
Pay for the drive, not the seat. Up to 5 teammates on one drive, and adding a teammate never adds to the price.
Run the whole thing on your own infrastructure with your own model keys, so your code never leaves your environment.
Coshell does not fork the protocol. Point the OpenCode CLI you already have at a drive and attach, and you are in the same live session as everyone else on it. No new client, no lock-in.
Stock OpenCode, attached to a Coshell drive. Mint a per-drive token from the dashboard CLI access tab.
| OpenCodeopen source · self-hosted | Coshellhosted · multiplayer | |
|---|---|---|
| What it is | The open-source agent engine | OpenCode, hosted, with the team layer added |
| Where it runs | Your machine or your own server | Managed cloud drives, or your own infra on enterprise |
| Players per session | One person, one session | Up to 5 teammates in one live session |
| Real-time multiplayer | Not built in | Same live session, shared filesystem and terminal |
| Overlap detection | — | Catches overlapping edits before they clobber |
| Load codebase once | Per person, per machine | Loaded once, cached for the whole team |
| Per-session privacy | — | Private, named, or open, per session |
| Integrated preview | — | Shared localhost browser in the session |
| Models | Bring your own keys | 70+ models on your own keys, scoped per drive |
| Works from | A terminal you set up | Any browser, plus the CLI |
| Pushes to real git | Yes | Yes |
| Setup | You host and maintain it | Nothing to host. Launch a drive and share it |
| Best for | One developer, self-managed | A whole team working with the agent together |
OpenCode is the engine underneath. Coshell is what makes it a team product.
Use the included models through OpenCode's gateway, point Coshell at your own provider keys directly, or, on Enterprise, route everything through Amazon Bedrock in your own AWS account. The included models and your own provider keys each follow that provider's data terms. With Bedrock in your own AWS account, calls run in the AWS region you invoke, and AWS does not store, train on, or share your prompts and completions. Pick the path that fits your data rules.
See the security details.
The agent engine, the SDK, the providers, the MCP tools, the themes are all OpenCode, unchanged. The only thing new to learn is the layer Coshell adds: drives, multiplayer, privacy, verified-identity access, and your own model routing. Our docs map straight onto what you already use, and link back to OpenCode for the engine itself.
We did not start from zero. We started from the best open-source agent there is, and built the team layer on top.
No. Coshell is built on OpenCode and keeps it fully open underneath, including the CLI, SDK, and wire protocol. What Coshell adds is the hosted team layer OpenCode does not ship: persistent cloud drives, real-time multiplayer in one live session, overlap detection, per-session privacy, and per-drive auth. You can self-host OpenCode for free forever. Coshell is for teams who want that agent shared and hosted.
Yes. Coshell does not fork the protocol, so the stock OpenCode CLI attaches to a Coshell drive unchanged. Set OPENCODE_SERVER_PASSWORD to a per-drive token and run opencode attach against your drive's address. You are then in the same live session as everyone else on the drive.
Persistent cloud drives, real-time multiplayer in one shared session, per-session privacy controls, verified-identity access control, an integrated localhost browser, CLI device-login, per-drive billing, your own Amazon Bedrock, and on-prem enterprise. OpenCode provides the agent engine those layers sit on top of.
They are different layers of the same stack. OpenCode is the open-source agent engine that runs on one machine for one person. Coshell is the hosted product that takes that engine and makes it multiplayer for a whole team. Comparing them is really comparing single-player self-hosted against hosted multiplayer.
You keep the engine, the models on your own keys, and real git, and you can run on your own infrastructure on the enterprise tier. What changes is that you no longer host or maintain it yourself, and you gain the team layer. If you only ever work solo, self-hosted OpenCode is a perfectly good choice, and we will say so.
Keep the agent engine you trust. Add the live session your whole team works in together. Open a drive in the browser, or attach from the OpenCode CLI you already have.