Pair program with the agent, together.
Two engineers, one live session, one agent on one running drive. Stop trading a screen-share where one person drives and the other watches. Both of you prompt the same agent, on the same files and terminal, at the same time.
One of you drives, the other watches a video of your screen.Both of you prompt one agent in one live session, together.
What pairing in Coshell actually looks like.
Not a screen-share and not two checkouts that merge later. One shared session on one running drive, with everything you need to work side by side. Every line below is running in production today.
Both of you prompt the same live agent
No driver and no watcher. Two engineers prompt one agent in one live session, on one running filesystem and terminal, and watch the same work land. Not two copies of the codebase trying to merge later.
Presence and follow, so you see each other's focus
See who is in the session and what they are looking at. Follow a teammate's view to ride along with their train of thought, and use the in-session chat overlay to talk without leaving the work.
Shared terminal and shared browser
The terminal and the integrated localhost browser are shared and auto-reloading, so you both see the same output and the same preview. Inspect an element, leave a comment, and send it straight to the agent.
Private when you start, shared when you are ready
Keep a session private while you sketch, share it with your pairing partner by name, or open it to the whole drive. Per-session access control means you decide the audience, session by session.
The codebase is loaded once, for both of you.
A drive stays warm in the cloud with your files, terminal, and dependencies ready. The agent reads the repo once for the session and holds it warm, so the two of you work against the same live state instead of each paying to load context on your own. Use 70+ models on your own keys, scoped per drive, and push to your real git when you are done. It sleeps when idle, and idle time is never billed.
Pairing in Coshell, answered
How is this different from sharing my screen while I drive?
On a screen-share, one person types and everyone else watches a video of it. In Coshell you are both in the same live session, prompting the same agent on the same running drive. Your partner is not watching a stream of your machine, they are working in the environment with you, with their own prompts, presence, and follow.
What happens if we both ask the agent for something at the same time?
You are prompting one shared agent on one running environment, not two copies that merge later, so there are no diverging changes to reconcile afterward. If work runs concurrently and two edits reach for the same lines, an overlap layer catches it before they clobber. The repo is read in once and stays warm for the session, so you are both working against the same live state.
Can my partner pair from the terminal while I use the browser?
Yes. Coshell works from any browser and from the CLI. Your partner can device-login and attach to the drive by name, and the stock OpenCode CLI attaches unchanged. You can be in the browser and they can be in the terminal, both in the same live session on the same drive.
Pair with the agent, in one live session.
Open a drive in the browser, or attach from the CLI. Bring your pairing partner into the same live session and prompt one agent together, on the same running drive.