Fix a ChatGPT or Codex connection

Start with the action that failed and Proofline's error message. Reading a review, requesting a review, and changing setup require different permissions. A working connection can still lack permission for one action.

Authorization completed, but the client asks to reconnect#

The browser's “Authentication complete” page confirms that the authorization flow returned to the client. Check the connection by asking the plugin to read an accessible review.

If it still reports expired authentication, reconnect Proofline from the client where the error appears. Reconnecting ChatGPT does not update a separate Codex connection.

Complete authorization in a browser signed in to the intended GitHub account. If you use different accounts in Chrome and Safari, check the account on Proofline's authorization page before approving.

After authorization succeeds, retry the failed action. If Codex still uses the previous connection, close and reopen Codex, then retry. Repeatedly approving the same permissions will not add a missing permission.

Setup is refused#

Check the reason shown by Proofline:

• If Run setup from a coding agent is missing, reconnect with a client request that includes that permission. You cannot add it on a consent page that does not offer it.
• If administrator access is required, sign in as an administrator of the selected organization. Repository access alone is insufficient.
• If setup requires all repositories, choose All repositories I can access in this organization.
• If the organization's policy refuses setup, ask an owner to allow it under Settings → API tokens → Policy. Reconnecting cannot override that policy.
• If the browser sign-in is too old, sign in to Proofline again and reconnect with setup permission.

Setup answers require a sign-in from the last 24 hours. Signing out of the browser session that approved the connection ends its setup access. Other granted permissions can continue to work.

The organization or repository is missing#

Check the selected organization and GitHub identity first. The plugin's authorization is limited to that organization and the approved repositories.

If the authorization page offers Install the GitHub App, complete that step and select Check GitHub access. If installation needs another administrator's approval, wait for that approval before continuing.

Access through a browser does not prove that the plugin has the same access. Organization membership and the plugin's repository selection also affect authorization. Ask an organization administrator to check access if the expected organization is absent.

Reviews work, but guidance or review requests fail#

Guidance needs Read guidance. Starting a review needs Request reviews, plus GitHub write access to the repository. Ask the client to request the missing permission, then review the new authorization page.

A policy refusal needs an organization owner to change the policy. It is not an expired login.

Setup has no environment assessment#

Check Installation in Proofline. A deferred environment leaves you with code reviews until you connect and confirm an environment.

If an environment exists, inspect its setup status and the review's missing evidence. A connected plugin cannot make an unavailable cloud account or incomplete evidence collection ready. See Guided setup and Read a review.