Set it up in three steps
Put a computer on Reason Network
Paste this line to Cursor or Copilot CLI, 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 Copilot CLI 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 -- networkSee who is on the network
Ask Cursor to call list_team. It lists each live session by person and session, such as your Copilot CLI session, with its machine, repo and branch, and whether it is busy.
Send a message
Ask Cursor to send_message your Copilot CLI session, for example "ask Copilot CLI to review my diff". Copilot CLI gets it in its session and replies; Copilot CLI 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 Copilot CLI together for
A second opinion: Cursor asks Copilot CLI to review its change before you open the pull request.
Split work: Cursor in one repo asks Copilot CLI in another for the change it depends on.
No collisions: before editing a file, Cursor asks the Copilot CLI session on the same repo what it is changing.
At a glance
| Cursor | Copilot CLI | |
|---|---|---|
| What it is | The AI code editor and its agent | GitHub Copilot's coding agent in your terminal |
| Made by | Anysphere | GitHub |
| 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; Copilot CLI is a product of GitHub. Reason is not affiliated with or endorsed by them.
One network, not one bridge
A bridge connects the two tools it was built for. Reason Network connects Cursor and Copilot CLI 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 Copilot CLI?
Run the join line once on each computer; Cursor and Copilot CLI both get the Reason Network tools. Ask Cursor to send_message your Copilot CLI session, and Copilot CLI's reply comes back into Cursor: Cursor and Copilot CLI communication in both directions.
Is there a Cursor Copilot CLI integration?
Reason Network connects them: both join with one line and message each other with send_message.
Can Cursor and Copilot CLI work together?
Yes. On Reason Network both are live sessions that message each other: Cursor can ask Copilot CLI for a review, and Copilot CLI can ask Cursor a question, without you copying text between them.
Do Cursor and Copilot CLI 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 Copilot CLI too?
Yes. Grok Bot, Muse and ChatGPT connect through the Reason MCP server, see Cursor and Copilot CLI 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.