coop

Real-time collaboration for AI coding sessions

One session talks to Claude. Another talks to GPT. A third runs locally with Llama. Coop connects them all.

One team, any tool

Claude Code
OpenCode GPT / Gemini
Codex CLI
Cursor terminal mode
coop messages · files · context · presence

Your team doesn't need to agree on a tool. They just need to agree on a session.

Works with

Claude Code Native hooks
Codex CLI Native hooks
OpenCode Native hooks
Gemini CLI MCP (coming soon)
Goose MCP (coming soon)
OpenClaw CLI commands
Aider CRON/CLI poll
Amp CRON/CLI poll
Any CLI REST API
Claude Code Native hooks
Codex CLI Native hooks
OpenCode Native hooks
Gemini CLI MCP (coming soon)
Goose MCP (coming soon)
OpenClaw CLI commands
Aider CRON/CLI poll
Amp CRON/CLI poll
Any CLI REST API

Native hooks CLI commands MCP (coming soon) CRON/CLI poll

Pair programming

Send a prompt, pass an interface, share a snippet — directly into your partner's session, whatever tool they use. No Slack, no screen share, no "hey can you look at line 42."

Both sessions stay focused on their own work. When one finds something the other needs, /coop sends it through. Your tool reads the conversation, composes the message, and your partner's tool picks it up automatically.

alice — feature-auth
> refactor AuthProvider to use token rotation
Claude Done. New interface:
interface AuthProvider { rotate(token: string): Promise<TokenPair> validate(token: string): boolean revoke(sessionId: string): void }
> /coop pass the new AuthProvider interface to bob
Sent to feature-auth
bob — feature-auth
> wire up the login API route
from @alice
New AuthProvider interface with token rotation — rotate(), validate(), revoke(). Use this for the login route.
Claude Got it. I'll implement the login route using Alice's new AuthProvider interface.

Group work

Generate a plan, split it into sections, and share it with your team. Each person takes a piece and coordinates through their AI coding session — without ever leaving the shell.

The plan lives in everyone's context. When Alice finishes the API layer, she sends a status update. Bob's tool sees it and knows the endpoints are ready for the UI. Carol's tests can target the real interfaces, not stubs.

v2 migration plan
@alice API routes + middleware
@bob Dashboard UI components
@carol Integration tests
alice API done
bob building UI
carol waiting on API

Teleport your session

Working from your desktop? Check the code in, push your context — what you were doing, what's left, what you tried — and pick it up seamlessly on your laptop, a server, or a teammate's machine.

Session context travels with the work, not the hardware. Your plans, findings, and in-progress notes arrive at the next prompt on whatever machine you open next.

desktop
context + plans + findings
laptop
desktop — refactor-v2
> /coop push context for finishing on my laptop
Claude Sending session summary: 8 files modified, auth middleware refactored, 2 tasks remaining (tests + migration). Context pushed.
Sent to refactor-v2

Not just chat — context

Every message, every file, every decision is indexed and searchable. When someone joins the session — human or AI — they get relevant history injected automatically. No catching up. No "scroll up."

Works from the CLI. Works from the web console. Works from a hook that fires before every prompt.

terminal
> coop session context --query "what was the auth decision?"
[2026-04-10] decided to use Clerk JWT verification in middleware
[2026-04-12] middleware.ts auth bypass when API key header missing

Web + CLI + API

Browse session messages and search context from a browser. Manage sessions from the terminal. Build integrations via REST.

Same data, three interfaces. Use what fits.

Browser
coopcli.com/dashboard
Terminal
coop session peek
API
POST /api/u/:userId/sessions/:name/context

How it works

Three moving parts, any tool, zero overhead.

1

Hook fires on every prompt

coop installs a UserPromptSubmit hook. Every time you press Enter, it silently polls the server for waiting messages.

alice — feature-auth
> add error handling to the login route
↑ hook: polling for messages…
↑ hook: 1 message waiting
Claude Starting on error handling. (Message from bob injected.)
2

Send with /coop

The slash command lets your tool compose and route a message naturally. Describe what to share — it goes to the right session instantly.

bob — feature-auth
> /coop let alice know the UI is wired up, needs her API endpoint
Claude Sending to alice on feature-auth…
✓ Delivered
3

Context at the next prompt

At alice's next prompt the message is injected as context. The tool reads it and acts — no copy-paste, no alt-tab, nothing lost.

alice — feature-auth
from @bob
UI is wired up — needs the /api/v2/auth endpoint to be live.
Claude Got it. Deploying the auth endpoint now.

Get started in 60 seconds

1

Install

npm i -g coopcli
2

Log in

coop login
3

Create a session

coop session join my-feature
4

Collaborate

/coop
Get Started Read the Docs