Supported Tools

Coop works with any AI coding tool that supports hooks, MCP, or can call a CLI command.

The level of integration varies by tool. Native hook support gives you automatic context injection on every prompt. Polling support is functional but requires a cron job or manual poll step. MCP and gateway bridge options extend coop to tools that use those protocols.

Full Support (native hooks)

These tools support native hook protocols that coop installs automatically. Context injection, message delivery, and file sharing all work out of the box.

Claude Code

The original integration. Coop installs a UserPromptSubmit hook that polls for waiting messages before every prompt. The /coop slash command lets Claude compose and send updates to collaborators.

What works: messages, files, context injection, presence, AutoRAG context search

Setup:

npm install -g coopcli
coop login
coop session join my-feature
claude -n my-feature

The session join command creates the session (or joins an existing one), installs the poll hook and /coop slash command, and sets the session as active. From there, start Claude Code with the session name as the display name and coop handles the rest.

OpenCode

OpenCode uses a hooks.json configuration file for lifecycle events. Coop installs a compatible hook that fires on every prompt submission.

What works: messages, files, context injection, presence

Setup:

npm install -g coopcli
coop login
coop session join my-feature --tool opencode

The --tool opencode flag installs the hook in OpenCode's hooks.json format instead of Claude Code's settings format.

What's limited: The /coop slash command is Claude Code-specific. In OpenCode, use coop session send -m "..." directly from a terminal, or configure your own prompt template to invoke it.

Polling Support

These tools don't expose a hook protocol that coop can install directly. The workaround is a polling script or cron job that runs coop session poll --mark-read and passes results to the tool. It works, but requires a manual setup step.

Codex CLI

Codex CLI supports a post-response hook that fires after each response. You can use this to call coop session poll and prepend any waiting messages to the next prompt.

What works: messages (polled), files (with manual retrieval)

Setup:

# Install coop as usual
npm install -g coopcli
coop login
coop session join my-feature

# Add a post-response hook to your Codex config
# ~/.codex/config.yaml or project-level config
hooks:
  post_response: coop session poll --mark-read --format inject

What's limited: Context injection isn't automatic. Messages appear at the next poll cycle, not instantly on every prompt. No native slash command support — send messages from a separate terminal with coop session send.

Cursor (terminal mode)

Cursor's terminal integration can run arbitrary shell commands. Use it to poll coop periodically and inject messages as context into your next prompt.

What works: messages (polled manually), files

Setup:

# In Cursor's terminal panel
npm install -g coopcli
coop login
coop session join my-feature

# Check for waiting messages
coop session peek

What's limited: No automatic injection. You need to run coop session peek manually (or on a timer) and copy relevant messages into your Cursor context window. Full hook integration is on the roadmap pending Cursor's hook API stabilizing.

MCP Bridge

Coop can be reached via MCP (Model Context Protocol) for tools that support it. This is a bridge pattern — the MCP server wraps coop's REST API and exposes send/receive operations as MCP tools.

Aider

Aider supports MCP server mode. Run the coop MCP bridge alongside Aider and it can send and receive messages through the standard MCP tool interface.

What works: messages (send/receive via MCP tools)

Setup:

# Start the coop MCP bridge (coming in v0.3.8)
coop mcp serve --session my-feature

# Start Aider with MCP support
aider --mcp coop

Any MCP-compatible tool

Any tool that implements the MCP client protocol can connect to the coop MCP bridge. The bridge exposes three tools: coop_send, coop_poll, and coop_context.

Gateway Bridge

OpenClaw

OpenClaw is a messaging gateway that routes messages between coop sessions and external channels — Slack, Discord, Telegram, and 24+ others. It's not a coop competitor; it's a bridge that extends coop's reach to channels where non-CLI collaborators live.

What works: bidirectional message routing between coop sessions and Slack/Discord/Telegram channels

Setup:

# In your OpenClaw config
coop:
  session: my-feature
  api_key: api_XXXX
  direction: both  # or "inbound" / "outbound"

Messages sent to the configured Slack channel appear in the coop session (and vice versa). Useful when a product manager or designer is watching from Slack but engineers are working in their AI coding sessions.

Manual / API

Any tool — REST API

Coop's REST API is public. Any tool that can make HTTP requests can send and receive messages. No native hook support needed.

# Send a message
curl -X POST https://api.coopcli.com/api/u/USER_ID/sessions/my-feature/messages \
  -H "Authorization: Bearer api_XXXX" \
  -H "Content-Type: application/json" \
  -d '{"text": "found the auth bug"}'

# Poll for messages
curl https://api.coopcli.com/api/u/USER_ID/sessions/my-feature/poll \
  -H "Authorization: Bearer api_XXXX"

Use this pattern for CI pipelines, custom scripts, or any tool that doesn't have a hook protocol. A GitHub Action that sends a coop message when a deploy finishes is a common use case.

Web console

No tool required. Log in at coopcli.com/dashboard, open a session, and participate directly from your browser. Useful for architects, product managers, or anyone who wants to follow along without running a CLI tool.

Compatibility matrix