Docs
Computers
One account can hold several computers. Each runs its own daemon and its own sessions; your apps show them all, grouped by computer, and their sessions can write to each other.
Add a computer
Install the daemon on it and pair it like the first one: run slashcode pair there and type the code under Pair another computer in the app's Settings, or Pair a computer in the web app's.
Pairing links the computer to your account, not to one device: every device of the account reaches it, new ones once you approve them. A computer belongs to one account at a time; pairing one that is already on another account fails.
To take a computer off your account, swipe it in Settings › Computers and tap Remove. Your devices stop seeing its sessions; a new pairing code brings it back.
How many computers
Free pairs one computer, Pro up to three. The relay counts them when a computer is paired, and refuses one past your plan: the app says Free pairs one computer. Go Pro to add up to three. See plans.
Sessions across computers
A session on one computer can write to a session on another, the way it writes to one next to it: you name it with @, or the agent looks at your other sessions and sends one a message. It arrives as a prompt, marked with the session and the computer it came from. Starting a session and waiting for one work on the agent's own computer only; see agent tools.
The trust comes from your devices, never from the relay. Each time a device paired with several computers connects, it gives each of them the keys of the others, as it received them at pairing. A computer talks only to computers vouched for this way, and checks that each one's id matches its key.
Two computers then open a channel sealed end to end, through the relay, like a device and a computer. Over it, each shares the list of its sessions: title, harness, folder, branch and status, never their content.
Limits
- The other computer must be online. If it is not, or does not answer within 15 seconds, the send fails and the agent is told so. Nothing is kept to be sent later.
- A computer takes at most 60 messages a minute from your other computers.
- A session sends at most 20 messages per turn, to any session, so that two agents answering each other stop. The count starts over at the next turn.
Turn it off
On by default. A computer that should take no messages from your other computers refuses them all, without a restart:
$ slashcode peers offMessages from your other computers are refused here. `slashcode peers on` takes them again.
Its own sessions can still write to each other, and to your other computers.
When a computer sleeps or stops
A computer that sleeps is offline: your apps show it as Offline, and nothing reaches it until it wakes. The relay does not hold messages for it, and its automations do not run: a time missed while it sleeps is not caught up.
When the daemon stops, because you shut the computer down or reinstalled the service, the harnesses stop with it. At its next start it ends the turns they were in, closes the tools they left running, and plays the messages that were waiting in each session, in the order they were sent.
Every session's history is kept on the computer. Once it is back, your apps catch up from where they left off.