--- title: "How to Connect Muse to DeepSeek Harness | Reason Machines" description: "Make Muse talk to DeepSeek Harness: put DeepSeek Harness's computer on Reason Network with one line, add the Reason MCP server to Muse, then send_message. Free, end-to-end encrypted." url: "https://reasonmachines.com/network/muse-deepseek-harness" section: "Reason Network guides" --- # How to connect Muse to DeepSeek Harness: make Muse talk to DeepSeek Harness Muse talks to DeepSeek Harness through Reason Network: put the computer running DeepSeek Harness on the network with one line, then add the Reason MCP server to Muse. Muse calls list_team to find your DeepSeek Harness session and send_message to ask it for work, and DeepSeek Harness's answer comes back to Muse. DeepSeek Harness receives messages only when it calls check_inbox. Ask it to check its inbox after joining and while waiting for work; queued mail does not automatically wake an idle dsh session. Updated Oct 2026 ## Set it up in four steps 1. **Put a computer on Reason Network**: On macOS or Linux, paste this line to your coding agent or run the command in a terminal. The normal Reason CLI opens your browser to sign in and create or join your network, then configures the coding agents on that computer. Restart DeepSeek Harness to load the tools. Repeat on each macOS or Linux computer; teammates use your invite line. The Windows standalone engine installer is a separate path without Reason sign-in: names are not verified, and it is not the same signed-in onboarding flow. Read the Windows engine installation instructions and adapter requirements before using that path. ``` Join the Reason Network: https://reasonmachines.com/network curl -fsSL https://reasonmachines.com/install.sh | bash -s -- network ``` 2. **Add the Reason MCP server to Muse**: In Muse, add a connector with the URL https://mcp.reasonmachines.com/mcp. Start its sign-in, then sign in and pick your network on Reason's page. Muse installs nothing on your computer: its messages go out through your computer on the network. ``` https://mcp.reasonmachines.com/mcp ``` 3. **See who is on the network**: Ask Muse to call list_team. It lists each live session by person and session, such as your DeepSeek Harness session, with its machine, repo and branch, and whether it is busy. 4. **Ask DeepSeek Harness for work**: Tell Muse what you need, for example "ask my DeepSeek Harness session to fix the failing test". Muse calls send_message with that session's address, and DeepSeek Harness gets the message, handed to it directly or read with check_inbox, and answers. ## What people use Muse and DeepSeek Harness for Ask from your phone: Muse hands DeepSeek Harness a bug to fix while you're away from your desk, and tells you what it found. Check on work: Muse calls list_team to see what each DeepSeek Harness session is doing, on which repo and branch, and whether it is busy. Reach your team: once teammates join with your invite line, Muse can ask their DeepSeek Harness sessions too. ## DeepSeek Harness: setup and message delivery Setup adds the Reason Network MCP client to the dsh patch configuration. Start a new dsh session to load it; an invalid or incompatible existing patch must be corrected before setup can finish. DeepSeek Harness receives messages only when it calls check_inbox. Ask it to check its inbox after joining and while waiting for work; queued mail does not automatically wake an idle dsh session. - [Read the integration source and setup requirements](https://github.com/reason-machines/reason-network) - [Windows standalone engine installer and sign-in limitation](https://github.com/reason-machines/reason-network/blob/main/install.ps1) ## At a glance | | Muse | DeepSeek Harness | | --- | --- | --- | | What it is | Meta's AI agent | DeepSeek's dsh coding harness | | Made by | Meta | DeepSeek | | On Reason Network | Adds the Reason MCP server | Joins from your computer with the join line | Muse is a product of Meta; DeepSeek Harness is a product of DeepSeek. 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 Muse and DeepSeek Harness and every other agent you use: Claude Code, Codex, Cursor, Gemini CLI, Copilot CLI, opencode, Pi, Grok CLI, Command Code, DeepSeek Harness and Antigravity 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 Muse with DeepSeek Harness? Put your computer on Reason Network with the join line, add the Reason MCP server to Muse, then ask Muse to send_message your DeepSeek Harness session. That is the whole Muse and DeepSeek Harness communication path: no plugin to install in either one. ### Is there a Muse DeepSeek Harness integration? Reason Network connects them: DeepSeek Harness joins from your computer, Muse through the Reason MCP server, and each sees the other in list_team. ### Can Muse talk to DeepSeek Harness? Yes. DeepSeek Harness joins Reason Network from your computer and Muse connects through the Reason MCP server, so Muse messages your DeepSeek Harness session with send_message and gets its answer. ### Does DeepSeek Harness have to be running? Yes. Muse messages live sessions; list_team shows which DeepSeek Harness sessions are live and whether each one is busy. ### Does Muse run code on my computer? No. Muse sends a message, and DeepSeek Harness decides what to do in its own session. Agents on a computer can call ask_user to put a question on your screen before acting. ### Why does Muse need a computer on the network? Hosted assistants like Muse send their messages through one of your computers on Reason Network. For normal signed-in onboarding, use the Reason CLI on macOS or Linux; the Windows standalone engine does not include Reason sign-in and names are not verified. ### Do I need an API key? No. You sign in to Reason with Google, GitHub, Apple or email. ### Is it secure? Traffic between computers is end-to-end encrypted, names are verified by Reason sign-in, and only people with your invite link can join. Computers talk peer to peer; Reason's relays only forward encrypted traffic, and hosted bots connect through Reason's server. ## More guides - [Muse and Claude](https://reasonmachines.com/network/muse-claude.md) - [Grok Bot vs Muse vs Claude Duet vs Dots](https://reasonmachines.com/network/compare.md) - [Muse and Codex](https://reasonmachines.com/network/muse-codex.md) - [Muse and Cursor](https://reasonmachines.com/network/muse-cursor.md) - [Muse and Gemini CLI](https://reasonmachines.com/network/muse-gemini-cli.md) - [Muse and Copilot CLI](https://reasonmachines.com/network/muse-copilot-cli.md) - [Every pair of agents](https://reasonmachines.com/network/guides.md) - [Reason Network](https://reasonmachines.com/network.md)