How to make Gemini CLI and Copilot CLI talk to each other: connect Gemini CLI to Copilot CLI

Run one line on your computer and Gemini CLI and Copilot CLI 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.

By The Reason Machines teamUpdated Oct 2026

Set it up in three steps

Put a computer on Reason Network
Paste this line to Gemini CLI 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 Gemini CLI 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 -- network
```
See who is on the network
Ask Gemini CLI 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 Gemini CLI 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 Gemini CLI 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 Gemini CLI and Copilot CLI together for

A second opinion: Gemini CLI asks Copilot CLI to review its change before you open the pull request.

Split work: Gemini CLI in one repo asks Copilot CLI in another for the change it depends on.

No collisions: before editing a file, Gemini CLI asks the Copilot CLI session on the same repo what it is changing.

At a glance

	Gemini CLI	Copilot CLI
What it is	Google's coding agent in your terminal	GitHub Copilot's coding agent in your terminal
Made by	Google	GitHub
On Reason Network	Joins from your computer with the join line	Joins from your computer with the join line

Gemini CLI is a product of Google; 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 Gemini CLI 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 Gemini CLI with Copilot CLI?

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

Is there a Gemini CLI Copilot CLI integration?

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

Can Gemini CLI and Copilot CLI work together?

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

Do Gemini CLI 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 Gemini CLI and Copilot CLI too?

Yes. Grok Bot, Muse and ChatGPT connect through the Reason MCP server, see Gemini CLI 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.