Set up

Three steps, the same three the Setup wizard walks you through: connect GitHub, connect your coding agent, then set up each repository.

1. Connect GitHub

verifAIed reads your repositories through a GitHub App. Click Connect GitHub, choose the account or organization on GitHub, pick the repositories, and you are sent back when the install is done.

The app gets read-only access to the repositories you pick:

  • Your code, to show source next to its coverage.
  • Your workflow runs, to find the coverage artifact a CI run uploaded.
  • Webhooks, so verifAIed hears when a CI run finishes and when you change which repositories the app can see.

You can grant every repository in the account or only some of them. To change that later, or to remove the app, use your GitHub settings or the Edit button on the repositories list. verifAIed follows the change on its own.

2. Connect your coding agent

Your agent talks to verifAIed in two ways: the verifaied CLI and an MCP server. Pick your agent below for the exact steps.

01

Choose your tool

02

Install with Claude Code

Two commands, no token
1

Install the CLI and log it in

uv tool install verifaied
verifaied login

pipx install verifaied works in place of the first command. verifaied login opens your browser: check the code matches your terminal and click Approve. Once per machine.

2

Connect Claude Code

verifaied setup claude

Registers the verifaied MCP server and the verifaied-recorder browser-test recorder for every repository on this machine, and installs the verifAIed skill. Both use the CLI's login, so there is no token to copy. Restart Claude Code afterwards.

3

Verify the connection

claude mcp list

You should see verifaied and verifaied-recorder connected.

4

Auto-approve verifaied tools

When Claude Code prompts the first time, pick “Yes, and don't ask again for verifaied - * commands”. The choice persists for your user.

To pre-approve before the first call, open Claude Code and run /permissions, then add mcp__verifaied to the allow list — wildcards every tool the server exposes.

Claude Code needs no token. Run verifaied login, approve it in the browser tab that opens, then run verifaied setup claude. It connects the MCP servers and installs the agent skill in one step.

For Codex, Cursor, Antigravity or another MCP client, create a token under Settings → API tokens and paste the command shown for that agent.

CI has no browser to log in with. Create a token under Settings → API tokens and give it to the job as the VERIFAIED_API_TOKEN secret.

3. Set up each repository

Ask your agent to set the repository up. The wizard gives you a line to paste for each repository; it looks like this:

Set up verifAIed for <owner>/<repo> using the verifaied MCP setup tool.

In Claude Code, the /mcp__verifaied__setup prompt does the same. The setup tool reads the repository and returns the steps that are left. Your agent does one, calls setup again to confirm it, and moves to the next:

  • Check that the CLI is installed and logged in.
  • Install the agent skill.
  • Run the tests with per-test coverage and JUnit output.
  • Upload this branch's coverage for the first time.
  • Add the coverage workflow to CI.
  • Finish by asking check_done whether the branch is done.

The setup tool is free. It never changes your repository: your agent writes the files, and you commit them. Commit the workflow and the skill so CI and every teammate's agent get the same setup.

Prefer to do it by hand? CI coverage has the workflow to add, and Agent skill and instructions has the skill and the rules to paste.

The wizard marks a repository as set up once a CI run has delivered coverage for it. Until then it shows Awaiting first CI run. You can skip the wizard and come back to it at any time.

What to do next

Build a feature with your agent walks through the everyday loop once the repository is set up.