FAQ
Frequently asked questions
Short answers to the questions that come up first when onboarding a repo.
Why does my upload fail with 401 when the Build token is right?
Server basicAuth gates every route, including uploads. Add upload.basicAuth with LHCI_BASIC_AUTH_USERNAME and LHCI_BASIC_AUTH_PASSWORD to lighthouserc.js.
What is the Admin token for?
Only for renaming or deleting that Project. It is shown once at Registration; keep it out of CI.
Why do I need a second Project for Live audits?
The server keeps one Build per Project and commit hash and rejects a second upload for the same commit with 422. A <repo>-live Project keeps Live audits apart.
How long are scores kept?
30 days by default. A daily job at 03:00 deletes older Builds; set LHCI_RETENTION_DAYS to change the age.
Is there a hosted version or an account to sign up for?
No. You deploy the server yourself. Sign in opens a server’s dashboard, where the browser asks for its basicAuth pair.
Can I install lhci-toolkit from npm?
Not today. lhci-toolkit and the login helpers are built from the lighthouse repo. The lhci-onboarding skill is published on npm.
Is there an MCP server?
No. The toolkit is a CLI, a library of login helpers and one Claude Code skill.
Still stuck? Contact us.