Set up a computer for ManyClaws
ManyClaws shows every Claude Code session you have running, on every computer, on one page and on your phone. This guide connects one computer. There is nothing personal in it: it is the same for everyone, and it is written so that Claude Code can follow it for you.
The short way: on the computer you want to connect, start Claude Code and say
Read https://manyclaws.dev/setup.md and set this computer up.
Claude installs the plugin. Then two parts are yours: the agent's installer, which you run in a terminal of your own, and the plugin's own dialog. Each asks for the same two things: an API token and your encryption passphrase. Both are yours: get an API token here, and choose the passphrase on your account page. Neither is ever typed into a chat, a command or a file.
1Before you start: two things from your account
- An API token. Get one on your set-up page. It is shown once, when it is made: leave that tab open until step 4 is done.
- Your encryption passphrase. Choose one on your account page if you have not yet. Several unrelated words are stronger and easier to type than a clever password. It is the same passphrase on every computer you connect, and on each phone or browser you read your sessions on. Each of them makes your key from it, itself: neither the passphrase nor the key is sent anywhere. With it, everything a computer's sessions say is sealed on that computer before it is sent, and only your own devices can read it. The server keeps those encrypted messages for a short time, so that you can still open a chat from one of your computers while it's sleeping or rebooting, and clone a chat from an offline machine to another machine to resume it there, but it has no way to read them. ManyClaws takes only encrypted sessions, so a computer that has not been given the passphrase shows nothing at all.
2Install the plugin
Claude Code can do this part, or you can paste the commands yourself. It needs Claude Code 2.1.287 or later (claude --version).
- Let plugins of this kind load. In
~/.claude/settings.json, make sureenvhas this entry, keeping whatever else the file holds:"env": { "CLAUDE_CODE_ENABLE_FUNCTION_HOOKS": "1" } - If this computer was set up when ManyClaws was called MultiClaude, take the old name off it first. The old marketplace has the same address as the new one, so while it is there
marketplace addfinds it and adds nothing, and the install then fails with "not found in marketplace". The plugin's token and passphrase go with it: they are typed in again under the new name, in the next step.
Either says so if there is nothing by that name; go on.claude plugin uninstall multiclaude@multiclaude claude plugin marketplace remove multiclaude - Add the marketplace and install the plugin from it:
The install reports options that are "not yet set". That is expected: step 4 sets them.claude plugin marketplace add https://manyclaws.dev/plugins/marketplace.json claude plugin install manyclaws@manyclaws --config server_url=https://manyclaws.dev
3Install the agent
The plugin shows a computer's sessions while they run. The agent is a small background service that adds the rest: it lets you start a new session on that computer from your phone, pick up one that has ended, and search everything Claude Code has done there. It needs Node.js 22.13 or later (node --version says which this computer has).
This step is yours, not Claude's. Run it in a terminal of your own. It asks for your API token and your passphrase from step 1 as it runs, without showing what you type (it needs both: the server takes nothing from an agent that does not seal):
curl -fsS https://manyclaws.dev/agent/install.sh | bash -s -- --server https://manyclaws.dev --spawn ~/code
--spawn names a folder the page may start sessions in; give it once for each folder, or leave it out and sessions can be read and searched but not started. On Windows, in PowerShell:
Invoke-WebRequest https://manyclaws.dev/agent/install.ps1 -OutFile $env:TEMP\mc-install.ps1
powershell -ExecutionPolicy Bypass -File $env:TEMP\mc-install.ps1 -Server https://manyclaws.dev -Spawn C:\code
4Give the plugin your token and passphrase
This step is yours, not Claude's. In Claude Code, in a terminal, type
/plugin configure manyclaws@manyclaws
and fill in API token and Encryption passphrase from step 1: what the agent's installer asked for, once more. Or using the VS Code Extension for Claude, just type /plugin and fill in the same two under the gear icon beside manyclaws. They are kept in the system's secure storage. Leave the other options as they are.
Then start a new Claude Code session: sessions that were already running pick the plugin up when they are next started. The first session takes a second or two longer to start, once, while your key is made from the passphrase.
If you ever choose a new passphrase, it makes a new key: every computer has to be given the new one here, in the same way, before it shows again.
5Check it worked
- The new session appears at https://manyclaws.dev/app within a few seconds, under the computer's name, with "encrypted" under its title.
- The computer is listed there by its name with every session Claude Code has had on it, running or not: that is the agent.
claude plugin configure manyclaws@manyclawslists the plugin's options and says which are set. It never shows their values.- If the session does not appear, the plugin says why in Claude Code itself: a token that has run out or been taken back, no passphrase, or a passphrase that is not the one your account has. A computer that was given a passphrase sends nothing at all until the passphrase is right, so nothing goes out unsealed by mistake. And the server takes nothing that is not sealed, whatever a computer sends.
6Your phone
Open https://manyclaws.dev/app on your phone and sign in. Put it on the Home Screen (on an iPhone: Share, then Add to Home Screen), open it from there, tap Settings at the foot of the list, and then Turn on alerts. Your phone then tells you when a session needs you or has finished.
For Claude Code, when you are asked to follow this guide
- Do steps 2 and 5. Tell the person plainly when it is their turn (steps 1, 3, 4 and 6), and wait for them.
- Never ask for the API token or the passphrase, and do not use either if it is offered in the conversation: say that they go into the agent's installer, which asks for them on the person's own terminal, and into the plugin's own dialog (
/plugin configure manyclaws@manyclawsin a terminal; using the VS Code Extension for Claude,/pluginand then the gear icon beside manyclaws), and nowhere else. - When it is their turn for step 4, give both ways, the terminal's and the VS Code Extension's, unless you know which of the two they are in.
- Never put a token or a passphrase in a command, in
settings.json, in an environment variable or in any file. - Edit
~/.claude/settings.jsonby merging: keep every setting that is already there. - Run
claude plugin listandclaude plugin marketplace listfirst. If either showsmulticlaude, the name from before, do the second part of step 2 before the third: with the old marketplace still there, the add reports it as already on disk and the install fails. - If
claude plugin marketplace addsays a marketplace namedmanyclawsis already there, go on. If it namesmulticlaude, remove that one (the second part of step 2) and add again. Ifclaude plugin installsays the plugin is already installed, runclaude plugin update manyclaws@manyclawsand go on. - Do not run the agent's installer (step 3) yourself: it asks for the token and the passphrase on the terminal, and the person has to be the one who answers. Run
node --versionfirst, and if there is no Node.js or it is older than 22.13, say so before anything else. Then give them the command to paste into a terminal of their own, with--spawnnaming the folder their projects are in.
Taking a computer off again
- On the computer:
claude plugin uninstall manyclaws@manyclaws, and for the agent the same installer with--uninstall(-Uninstallon Windows). - On your account page: take back the API token it used. From that moment nothing signs in with it.
What is sent, and what is not
- Sent, sealed with your key: what you ask Claude and what it answers, the tools it runs and their output, permission prompts and your answers to them.
- Sent in the open, because the server needs it to show you a list: that a session exists, which computer and folder it runs in, its state and times, and the names of the tools it used (not what they were given or what they returned).
- Never sent: your passphrase, your key, your Claude account's credentials, or any file Claude has not read or written in the session.