Getting started

Requesting access, having an account, connecting a computer, and finishing an agent turn are four different events. This page keeps them separate.

1. Request received. The form on the homepage saves a waitlist entry. You will see a confirmation in the browser when Pairon accepts it. That is not an account and not a connected computer.
2. Approved. Pairon writes to the same email, or a teammate’s invite approves you. Sign in at the app with that email. If the beta gate refuses the sign-in, the account exists but the workspace is not open yet.
3. Computer connected. In the app, open Computers and choose Connect a computer. Run the command it shows. It needs Node.js 22.6 or newer. Approve the computer only when the code in the browser matches the terminal.
4. First useful turn. Start a conversation in a project, send an instruction to a lane that is online, and wait until that agent turn completes. A button click is not that event.

The app shows the exact command for the deployment you signed in to. Leave the terminal open until approval finishes. An expired approval can be restarted by running the command again.

On macOS and supported Linux desktops, the runner can install a background service and will tell you when the terminal can close. If that setup is unavailable, the runner stays in the foreground. Folder access is decided on that computer. Approve any extra folder when Pairon asks there, not from a link in an email.

Then pick an installed agent: Claude Code, Codex or OpenCode. The agents page lists only those.

Invite a teammate as a Viewer, Collaborator or Admin. Accepting a project invite during the closed beta approves that person. A session join link lets a signed-in guest into one conversation. It does not add them to the workspace people list, and it does not enroll a workspace computer.

Already approved? Sign in. Still waiting? Request access. The room itself is described in How it works.