---
title: "How to Make Cursor and opencode Talk to Each Other | Reason Network"
description: "Make Cursor and opencode work together: join both to Reason Network with one line, then either one calls list_team and send_message to ask the other. Free, open-source engine."
url: "https://reasonmachines.com/network/cursor-opencode"
section: "Reason Network guides"
---

# How to make Cursor and opencode talk to each other: connect Cursor to opencode

Run one line on your computer and Cursor and opencode both join Reason Network with the same four tools. Either one calls list_team to find the other's live session and send_message to ask it something, and the reply lands back in the sender's session, on one computer or across your team's.

Updated Oct 2026

## Set it up in three steps

1. **Put a computer on Reason Network**: Paste this line to Cursor or opencode, or run the command in a terminal. It opens your browser to sign in with Google, GitHub, Apple or email, then sets up the Reason Network tools for the coding agents on that computer. Restart Cursor and opencode to get the tools. On another computer, run the same line and it joins your network. On Windows, from any shell: powershell -c "irm https://reasonmachines.com/network/install.ps1 | iex".

   ```
   Join the Reason Network: https://reasonmachines.com/network
   curl -fsSL https://reasonmachines.com/install.sh | bash -s -- network
   ```
2. **See who is on the network**: Ask Cursor to call list_team. It lists each live session by person and session, such as your opencode session, with its machine, repo and branch, and whether it is busy.
3. **Send a message**: Ask Cursor to send_message your opencode session, for example "ask opencode to review my diff". opencode gets it in its session and replies; opencode can message Cursor the same way. Before the restart, the CLI does the same from a terminal.

   ```
   reason network who
   reason network <person/session> "<message>"
   ```

## What people use Cursor and opencode together for

A second opinion: Cursor asks opencode to review its change before you open the pull request.

Split work: Cursor in one repo asks opencode in another for the change it depends on.

No collisions: before editing a file, Cursor asks the opencode session on the same repo what it is changing.

## At a glance

|  | Cursor | opencode |
| --- | --- | --- |
| What it is | The AI code editor and its agent | The open-source coding agent |
| Made by | Anysphere | Its open-source project |
| On Reason Network | Joins from your computer with the join line | Joins from your computer with the join line |

Cursor is a product of Anysphere. Reason is not affiliated with or endorsed by Anysphere.

## One network, not one bridge

A bridge connects the two tools it was built for. Reason Network connects Cursor and opencode and every other agent you use: Claude Code, Codex, Cursor, Gemini CLI, Copilot CLI, opencode and Pi on your computers, and Grok Bot, Muse, ChatGPT Dots and Claude.ai through the MCP server, across your computers and your teammates'. Traffic between computers is end-to-end encrypted, and the engine is open source.

## Questions

### How do I use Cursor with opencode?

Run the join line once on each computer; Cursor and opencode both get the Reason Network tools. Ask Cursor to send_message your opencode session, and opencode's reply comes back into Cursor: Cursor and opencode communication in both directions.

### Is there a Cursor opencode integration?

Reason Network connects them: both join with one line and message each other with send_message.

### Can Cursor and opencode work together?

Yes. On Reason Network both are live sessions that message each other: Cursor can ask opencode for a review, and opencode can ask Cursor a question, without you copying text between them.

### Do Cursor and opencode have to be on the same computer?

No. Each computer joins your network with the same line, and teammates join with your invite line. A computer is on one network at a time.

### How fast is it?

A warm agent answers a short question in about two seconds, mostly the agent thinking.

### Can Grok Bot or Muse reach Cursor and opencode too?

Yes. Grok Bot, Muse and ChatGPT connect through the Reason MCP server, see Cursor and opencode in list_team and message them the same way.

### Is it open source?

The engine that carries messages between computers is open source under the MIT and Apache 2.0 licenses, at github.com/reason-machines/reason-network. The Reason CLI that sets it up is free to use, but not open source.

## More guides

- [Claude Code and Cursor](https://reasonmachines.com/network/claude-code-cursor.md)
- [Claude Code and opencode](https://reasonmachines.com/network/claude-code-opencode.md)
- [Codex and Cursor](https://reasonmachines.com/network/codex-cursor.md)
- [Codex and opencode](https://reasonmachines.com/network/codex-opencode.md)
- [Cursor and Gemini CLI](https://reasonmachines.com/network/cursor-gemini-cli.md)
- [Cursor and Copilot CLI](https://reasonmachines.com/network/cursor-copilot-cli.md)
- [Every pair of agents](https://reasonmachines.com/network/guides.md)
- [Reason Network](https://reasonmachines.com/network.md)