Install the CLI, sign in, and start your first session.

When you create a new Polygraph account, we recommend going through the built-in demo experience. It showcases the product and helps you get familiar with its features before you point it at your own repos.

Install the CLI with curl:

curl -fsSL https://app.trypolygraph.com/install.sh | sh

Homebrew:

brew install nrwl/tap/polygraph

PowerShell:

irm https://app.trypolygraph.com/install.ps1 | iex

npm:

npm install -g polygraph@latest

Start with the interactive CLI. It guides you through sign-in, account selection, and session setup.

polygraph

Polygraph indexes every repo you have access to and stitches them into one graph. Your agent works against that graph instead of one repo at a time.

After sign-in, confirm the effective account before starting a session.

polygraph whoami

If you want to run the sign-in flow directly, use the auth command.

polygraph auth login

Polygraph uses an OAuth device flow for CLI sign-in. The CLI opens or prints a browser approval URL and code:

> polygraph auth login
       *   *
        \ /
* ------ * - *   Polygraph
        / \
       *   *
Opening your browser to authorize Polygraph CLI...
If your browser does not open, visit:
  https://app.trypolygraph.com/profile/oauth?user_code=XXXX-YYYY
Code: XXXX-YYYY

Compare the code in your terminal with the code shown in the browser, then approve the request while signed in to Polygraph.

Work happens in sessions. Start one by running the CLI:

polygraph session start

Or by invoking the Polygraph skill within your existing agent session:

/polygraph create a session and add all repos that depend on this one

Pick the repos up front, or describe the task and let Polygraph find them.

A session isn't locked to the repos you started with. Prompt the agent to pull in another repo:

Please add vitejs/vite repo to this session.

Whatever you can read, your agent can read: any repo you have access to (organization or open source).

polygraph session search

Show details such as URL, folder, and status for a session.

polygraph session show <session-id>

You can resume any session by any developer in your organization. When resuming, Polygraph reconstructs the state of the session on your machine: the repos are set up at the relevant SHAs, along with the relevant logs. You can start the work on one machine and continue on another, or start the work using Claude and finish it using Codex, without any friction.

polygraph session resume <session-id> # skip session-id to start with search

The exact same mechanism can be used to review other people's code.

polygraph session review <session-id> # skip session-id to start with search

You can also instruct Polygraph to perform an adversarial review.

polygraph session review <session-id> --adversarial

Pick a workflow that matches what you want to do.