MOCHILAB / GUIDE
One server, separate MochiBot assistants for several people
One server with independent chats, files, model settings and Skills logins. The helper is included; authorized users may share a membership account.
On this page
One server, separate MochiBot workspaces for multiple people
Complete first setup ↗ once. Do not buy another server or reinstall OpenClaw for each person. Everyone uses the same app. Models, API keys, Skills logins, chats, and files belong to each workspace.
1. Install the app on the next phone
Get the current MochiBot release (1.0.4 or newer for this setup route) from the download page ↗, then open Settings. USB debugging is unnecessary.
2. Create a workspace in the server terminal
The server operator runs:
sudo mochibotctl member-add phone2 --name Phone2
Replace phone2 with a new ID if needed: lowercase letter first, then lowercase letters, digits, or hyphens, up to20 characters. Phone2 is a display label. The phone can rename its assistant later.
Success shows a creation message and pairing QR. The command creates a dedicated system account, chat storage, workspace, and Skills assistant. No separate Ubuntu login password is needed.
3. Pair the next phone
Settings → Scan to connect → scan this workspace's QR → confirm. Do not reuse the first phone's QR. To replace an expired code:
sudo mochibotctl member-pair phone2
Do not repeat member-add or reinstall the server.
4. Set up personal access
On the new phone, Settings → Manage models: choose a model, enter your own API key, and tap Test, save and use. This does not change anyone else's model or copy their key.
Then connect a Skills account under Settings → MochiLab Skills account. Authorized users may each connect the same membership account; each workspace stores its own login. The helper is already installed. After verification succeeds in Settings, the assistant uses the saved connection for downloads; do not provide keys in chat.
5. Verify separation
Send different test messages and upload different harmless files on the two phones. Each should see only its own chats and files. On the server:
sudo mochibotctl member-list
sudo mochibotctl member-check
Expect an enabled workspace with an active service, and passed: true from the isolation check. The check does not print chat or file contents.
Later maintenance
sudo mochibotctl member-disable phone2
sudo mochibotctl member-enable phone2
These disable and restore that workspace's access while keeping data and other workspaces. To add someone else, repeat steps2–4 with a new ID. This installer supports up to8 additional workspaces; practical concurrency depends on host resources and API limits. WeChat and Telegram channels need separate configuration; these QR codes pair only MochiBot.
Each dedicated non-root account can execute commands, run scripts, install personal dependencies, and access the network. System permissions protect other workspaces and system directories. The host's root operator can administer all workspaces; this is not secrecy from the server owner.
Reinstalling a phone or renewing an expired code
For an owned computer, first complete the LAN setup guide ↗. Run sudo mochibotctl member-list to find the existing workspace ID. For an existing phone2, run sudo mochibotctl member-pair phone2 and scan the fresh code, rather than creating another workspace for the same person. Use member-add only for a new workspace. Codes last five minutes; renewing one preserves chats and other users.