Install the CLI, launch a drive, and bring your team into one live AI coding session. Here is everything you need to start, plus the concepts and commands to go deeper.
Two ways in, and you can mix them: everything works in your browser at coshell.ai, and from your terminal with the CLI. Each step below shows both.
Open coshell.ai and sign in to launch a drive in your browser, or install the CLI and sign in from your terminal. GitHub sign-in works either way.
A drive is your team's shared workspace. Create one from the dashboard, or from the terminal. Name it after a project or workstream.
Your drive opens in the browser with the agent, the terminal, and an integrated preview of your running app. Prefer the terminal? Attach to it instead. Either way you are in the same live session.
Invite a teammate to the drive. They join from a browser, or run coshell attach my-project, and you are in the same live session, prompting the same agent and watching the same work land.
Coshell does not fork the protocol. The OpenCode CLI you already have attaches to a drive unchanged, so you are never locked to our interface.
You can also mint a per-drive token from the dashboard, under CLI access.
A drive is your team's persistent cloud workspace: the repo, the environment, and your sessions, kept warm between sessions. Pricing is free to self-host, so teams keep a drive per project.
Inside a drive, everyone works in the same live session: one agent, one filesystem, one terminal, and an integrated browser preview. It is closer to a Google Doc than to git.
When two agents reach for the same lines of the same file, Overlap catches it and steers the second edit before it clobbers the first. It works across every model and fails open, so it never blocks your editing.
See who is in the session and what they are doing. Follow a teammate to watch them steer the agent in real time.
A drive runs your app and shows it live in an integrated browser preview. When the agent ships a change, everyone in the session sees it reload, so you review the running app together, not a diff.
Run 70+ models on your own keys, use the included models, or, on Enterprise, route through Amazon Bedrock in your own AWS account. Admins choose the allowed set per drive.
Every session has its own access control: private to you, shared with named teammates, or open to the drive. See the security details.
Work in a drive lands in your own repositories as normal commits and pushes, so your existing branches, reviews, and CI keep working. Nothing you build is trapped in Coshell.
Prefer the terminal? Everything here is also in the browser, but these are the commands you will use most. Run any command with --help for the full options.
Drive sizes: large (4 vCPU, 8 GB RAM, 20 GB disk, default), standard (2 vCPU, 4 GB), and small (1 vCPU, 2 GB). See pricing for the free tier and Teams.
Coshell runs 70+ models. Bring your own provider keys, use the included models, or, on Enterprise, route every model call through Amazon Bedrock in your own AWS account. Admins choose the allowed set of models per drive.
Work in a drive lands in your own repositories as normal git commits and pushes, so your existing branches, reviews, and CI keep working as they do today. Nothing you build is trapped in Coshell: your code stays in the git you already use.
Overlap. Everyone in a drive works on one shared filesystem, so there is no diverging copy to lose. And when two agents reach for the same lines of the same file, Overlap catches it and steers the second edit before it lands: proceed if the changes are compatible, take other lines, wait, or let the first land first. It runs across every model and fails open, so it never blocks editing.
Yes. Coshell does not fork the protocol, so the stock OpenCode CLI attaches to a drive unchanged. Mint a per-drive token with coshell token new, set OPENCODE_SERVER_PASSWORD, and run opencode attach against your drive's address.
Launch a drive in the browser, or attach from the CLI. Your whole team works in the same live session, on the same codebase.