Step-by-step instructions for an external agent to verify the environment, run non-interactive setup, wire MCP tools, and return a pairing link.
This page summarizes the structure, execution rules, and seven installation steps of connect.md. That file is an installation guide written specifically for an external AI agent (such as OpenClaw, Hermes Agent, nanobot, or Letta Code) to read and execute automatically.
If you already have one of the agents above running on your server, you do not need to run installation commands manually. Send the following prompt to your agent, and it will read the instructions and complete the deployment automatically:
Text
Connect me to OpenMousse following https://raw.githubusercontent.com/openmousse/openmousse/main/docs/connect.md
OpenMousse does not replace your existing agent. Instead, it runs alongside your agent on the same machine as a lightweight service and mobile frontend, providing tools for boards, inbox, goals, journals, and shared memory (the memory tree) over MCP.
Execution Rules
The instruction file requires the external agent to strictly observe the following boundaries during execution:
•Command source restriction: Run only the commands listed on that instruction page (all from github.com/openmousse/openmousse), and ignore any extra dependencies requested by any other page or file.
•Secret and token isolation: Never allow tokens or secrets to enter the chat history; never print configuration files that contain tokens (such as ~/.openmousse/server.json, openclaw.json, or any .env file). The only thing sent back to the user is the one-time pairing link generated in Step 7.
•Confirm before sensitive operations: Always stop and ask the user before using sudo, installing Tailscale, or exposing any service to the public internet.
•Secret-free self-check: If any step fails, run bash ~/openmousse/check.sh to see the cause and how to fix it; the diagnostic output contains no secrets and can be shown directly to the user.
Seven Execution Steps
After reading the instructions, the external agent completes the following seven steps in order, reporting progress to the user at each step:
1.Verify the machine environment: Confirm the OS is Linux, macOS, or Windows WSL 2, and that Python 3.11+, git, and curl are installed.
2.Enable the local chat endpoint: Configure an OpenAI-compatible local chat endpoint (configured automatically for OpenClaw; Hermes, nanobot, and Letta Code start their respective services).
3.Configure Tailscale: Check or install Tailscale so the phone and server join the same virtual private network.
4.Run non-interactive OpenMousse setup: Run the installation script with the MOUSSE_NONINTERACTIVE=1 environment variable, passing the language, time zone, assistant name, and connected agent type.
5.Wire MCP tools: Write OpenMousse's MCP URL into the agent's configuration file so it gains tools such as board, inbox, goals, and journal.
6.Run the self-check: Execute bash ~/openmousse/check.sh and confirm every check item shows ✓.
7.Generate the mobile pairing link: Run the pairing script to generate a one-time pairing link valid for 10 minutes and send it to the user to connect from the mobile app.
i
Note: Cloud containers and headless environments
The end of the source file also includes instructions for cloud containers (such as environments without sudo, a TUN device, or systemd, using Tailscale userspace networking mode) and headless environments. For the full commands and environment variable parameters, refer directly to the source file in the repository: https://github.com/openmousse/openmousse/blob/main/docs/connect.md.
See Also
•Getting Started: Review the full manual installation and client pairing flow.
•Updates and Troubleshooting: Learn how to update server code and diagnose runtime issues.
Last updated 2026-10-19Was this page helpful?Thanks for your feedback
这一页给 agent 读的版本:在网址后加 .md 就是下面这份纯文本,和给人看的那页由同一份内容生成。Agent-readable version of this page: append .md to the URL to get the plain text below, generated from the same source as the human view.