skip to content
Set up in five minutes

Parallax

Connect your coding editors

Choose your editors, run one install command, and confirm they connect.

Open the setup page

Go to Parallax setup, sign in with GitHub, and add a payment method. Choose Claude Code, Codex, Cursor, OpenCode, or several editors. Copy the command shown for your choices and run it in your terminal. The command expires after ten minutes; get a new one on the page if needed.

The installer needs Node.js 18 or newer, Git, and curl. It installs session capture and Parallax’s MCP tools for each selected editor, preserves unrelated editor settings, and keeps your credential in ~/.parallax-client/config.json. Your existing model provider and subscription stay in use. There is no spending cap on a fresh install (PARALLAX_WEEKLY_CAP_USDin front of the command adds one).

If you also use Prime Agent, replace install.sh with team-install.sh in the copied command and keep everything else, including its PARALLAX_HARNESSES=… editor selection. That installer wires the editors you chose, detects Prime Agent on the machine and adds its capture skill, dry-runs every client, and prints what will be captured and how to opt out.

terminal
curl -fsSL https://parallax.conifer.build/team-install.sh | PARALLAX_HARNESSES=claude-code,codex PARALLAX_CODE=<code> sh

Confirm the connection

The installer opens the setup page after it confirms installation. Restart your selected editors and accept their Parallax tool or hook trust prompt. In Codex, open /hooks to review new hooks. The page reports MCP connected when an editor starts the tools, and Capture received after a session sends its first captured activity.

Installation alone does not mean an editor has connected. Keep the page open while you start a session, or use Check connection. A failed status read can be retried without installing again. To install elsewhere, choose Set up another editor or machine.

Your first hour

Start a session in a connected repository. Claude Code and Codex show one line from Parallax at the start (Parallax brief handed to this session: 2 lessons); the agent never sees your transcript, the door does. When the session ends, Parallax sweeps it once and the result appears in the console Inbox. To check the machine at any time, run node ~/.parallax-client/doctor/main.mjs(installed with Codex) or the team-install.sh line again.

Open a pull request in a connected repository and a check named Parallax appears on it within seconds. When the review finishes you get one summary comment (verdict, findings by severity with their evidence, the one action) and, only when a fix was proven in a sandbox, one fix pull request. Reviews run four at a time per account, so a comment takes minutes on a quiet door and longer behind a full queue.

The console has three pages: Inbox (what needs a decision), Reviews and Repo. A Bugs page is built but not promoted yet.

Connect a repository

Install the GitHub App from the setup page and select a repository. Merge its setup pull request, then pull the change locally. The resulting parallax.yml at the repository root enables capture there. A teammate can install the App and merge this file for everyone; each developer runs their own install command.

Start an editor session in that repository and run a tool. If the setup page still says Capture waiting, check that your local checkout contains parallax.yml. Add the repository’s test command to the file so Parallax can verify findings against it.

parallax.yml
test: npm test

Capture and controls

Capture is scoped to your account and repositories with the marker, plus any repositories you explicitly name during installation. Claude Code and Codex send their saved transcripts. Cursor records completed tools and responses through hooks; OpenCode reads completed messages when a session becomes idle; Prime Agent captures through its skill. Available usage and cost information depends on the editor.

To stop on one machine, remove Parallax’s hooks, plugin, skill and MCP entry from the editors you installed, or remove ~/.parallax-client/config.json. Remove parallax.yml to stop marker-based capture in a repository for the team. Explicitly named repositories must also be removed from the local configuration.

Advanced: run your own server

The hosted setup above manages the server for you. To operate your own Parallax server, use Node.js 24 or newer and a Conifer API key for reviewer calls. Keep its database and credentials private.

terminal
git clone https://github.com/ConiferKit/Parallax parallax
cd parallax
npm install
export CONIFER_API_KEY='<your Conifer key>'
PARALLAX_TOKENS='dev:acct_me' node packages/server/src/main.ts

Install against the local server

terminal
curl -fsSL http://127.0.0.1:8787/install.sh | PARALLAX_DOOR=http://127.0.0.1:8787 PARALLAX_TOKEN=dev PARALLAX_HARNESSES=codex,cursor sh

Replace the example token before exposing a server beyond your machine. Hosted setup confirmation reads the hosted server; manage a separate server through its own API. For proxy capture, transcript imports, the GitHub App, and server configuration, follow the Parallax repository documentation.