Skip to content

Troubleshooting

Each section starts with the message or symptom you see. If your problem is not here, use Contact. Running the command with VIEWPORT_LOG=json set adds a JSON line to the error that is useful to include.

The CLI has no token for the server. Run viewport login and authorize it in the browser; see Sign in. This also happens after you revoke the machine’s token on the CLI tokens page or delete ~/.viewport.

no agent conversation was captured on branch …

Section titled “no agent conversation was captured on branch …”

Viewport found no recorded agent turns for this branch, so there is nothing to build the review from. Check these in order:

  1. Run viewport install and check that your agent shows conversation capture on.
  2. Capture only covers sessions started after viewport install. Start a new session in your agent.
  3. The turns are matched to the branch that was checked out when they happened. Make sure the work was done with the branch checked out (or on the target branch right before you created it).

One of the two branches does not exist in your local repository. Check the spelling of any branch you named. If it is the target, it may exist only on the remote: run git fetch, or name the target explicitly, for example viewport pr my-feature main.

You ran viewport pr while on the target branch, usually main. Check out the branch you want reviewed, or name it: viewport pr my-feature.

Run viewport pr from inside the repository. In your agent, make sure the session’s working directory is in the repository.

The terminal says the pairing code expired; run viewport login again, or the browser says “This code expired”. A code lasts 10 minutes. Run viewport login again and authorize the new code.

If the browser says “This link has no pairing code”, the URL was cut short. Run viewport login again and open the URL it prints in full.

On a server, over SSH, or anywhere without a browser, run:

Terminal window
VIEWPORT_NO_BROWSER=1 viewport login

Open the printed URL on any device where you are signed in to Viewport, check the code and click Authorize. The terminal prints logged in.

viewport install looks for ~/.claude, ~/.cursor, ~/.codex and ~/.copilot. Install your agent and run viewport install again.

Cursor creates ~/.cursor only on its first launch. If you use Cursor, open it once, then run viewport install again.

~/.local/bin is not on your PATH. Add this line to your shell’s rc file (for example ~/.zshrc or ~/.bashrc) and open a new terminal:

Terminal window
export PATH="$HOME/.local/bin:$PATH"

Your organization has used its reviews. viewport pr still records the branch and prints the link, but no run starts, and the review shows Quota exhausted. On a team organization the quota resets on the date the Review quota card shows; on a trial, click Request full access. Then open the review and click Rerun. See Your team.

The run could not finish, and the review shows Review failed. Click Rerun in the review’s header to try again. A failed run does not use up a trial review. If it keeps failing, send the review’s link through Contact.

An invitation link lasts 7 days and a password reset link 1 hour, and each works once. Click Send a new link on the page, enter your email, and a new link arrives by email.