Skip to main content
You need a connection allowance, access to at least one assigned vault, and a machine that can run nlkb. The local knowledge root must be dedicated and empty for first enrollment. Cloud vaults can already contain files or be empty.

​
Set up a new machine

  1. Open Connections in the correct workspace and choose Add new connection or Connect an agent. On desktop, use Set up this machine.
  2. Give it a recognizable name. An administrator can assign the owner to another person or a service principal.
  3. Select vaults. Company and Personal start selected when available; team vaults stay off until selected. Selected replica vaults request two-way sync where permissions and vault policy allow it.
  4. Select Copy agent prompt and paste it into the file-capable AI tool on that machine.
  5. Let the tool follow the setup instructions, install the service, and run nlkb doctor.
  6. Check the connection card and open the local folders. Confirm an existing cloud page appears, or create a harmless test page if the vault is empty.
Pairing codes expire after 15 minutes and can be redeemed once. If the code expires, use Reissue code on the same connection. A pending card’s Copy agent prompt can reopen the receipt or issue a replacement when needed.

​
Already paired this machine?

Use Add this harness to install the instructions in another tool. The setup skill detects an existing replica and skips enrollment. Do not reset a healthy replica merely to add another AI tool.

​
Without an agent

Open Manual install on the receipt and select Linux, Mac, or Windows. Use the generated command for that machine. It installs the binary, enrolls the connection, installs the background service, and checks health. Windows instructions use Git Bash. The manual command contains a short-lived pairing code and may remain in shell history. Keep the prompt private and never place codes or durable keys in vault files, reusable skills, URLs, or shared screenshots.

​
Local layout

Only granted vaults are mounted. Team-name collisions receive a suffix. Renaming a cloud vault does not rename its existing local folder. Use CLI orientation to locate the actual mounts.