Set up Proofline from a coding agent

An organization administrator can answer Proofline's setup questions from Claude Code, Codex or another connected agent instead of the Installation page. The agent asks the same questions as the setup conversation and sends your answers to it.

Before you start#

You are an organization administrator.
You signed in to Proofline in your browser within the last 24 hours.
The Proofline CLI is installed and your agent is connected to it. See Set up a coding agent.

Approve setup for the CLI#

In a terminal, run proofline login with the setup permission. The coding-agent guide has the full command.
On the approval page, check the device code and choose your organization.
Keep Run setup from a coding agent selected, and keep All repositories I can access in this organization. The setup permission cannot be limited to selected repositories.
Select Authorize Proofline CLI.

If the approval is refused, sign in again and approve a new code. A member who is not an administrator cannot approve the setup permission.

Answer setup questions#

Install the Proofline skills for your agent from the Proofline skills repository.
Ask the agent to set up Proofline.
The agent tells you which setup items are blocked and who can resolve them. It then asks Proofline's next question. Choose an option or answer in your own words. Say that you do not know when you cannot confirm an answer.
Answer each question in turn. To ask for something else, tell the agent; it sends your request to the setup conversation.

Your answers appear in the setup conversation on Installation, and you can continue there at any time.

What stays in the console#

Confirming the setup, connecting cloud accounts and approving access changes happen on Installation. When the agent reaches one of those steps, it tells you to continue in the console. Run proofline setup to open it.

Renew or end access#

Answers need a browser sign-in from the last 24 hours. After that, sign in to Proofline again and run proofline login with the setup permission again.

Signing out of the browser session that approved the CLI ends its setup access. The CLI keeps its other permissions. To remove the CLI entirely, revoke it from Personal tokens.