HomeCLI and SDKs

A local scan from the terminal, and SDKs for your own code

The bugrunner CLI runs the synthetic user on your machine with no server. The Go, Python and TypeScript SDKs wrap the same REST API the dashboard uses.

Availability. The CLI builds from the repository today and none of the SDKs is published to npm, PyPI or the Go proxy yet. The TypeScript package is prepared for npm, but publishing it is still a manual step nobody has done. Ask the founder for access.

bugrunner scan

bugrunner scan <url> drives a browser with the same engine as the hosted runner. It needs an OPENAI_API_KEY or an ANTHROPIC_API_KEY in the environment, and bugrunner doctor checks that setup without spending anything.

What the flags do

FlagWhat it does
--stepsMaximum page interactions, 8 by default.
--personanew_user (default), power_user, edge_case or returning_user.
--repeat, --interval, --max-runsContinuous mode: scan again on an interval.
--out and --fail-onWrite a JSON or Markdown report, and exit non-zero when a finding reaches critical, high, medium or low. Use it as a CI gate.
--sessionA Playwright storage state, for apps behind single sign-on.
--email, --passwordLog in through a form.
--allow-internalAllow localhost and private addresses for a local app.
--github-repoFile findings as GitHub issues, with a GITHUB_TOKEN set.

The report includes token usage, the model and an estimated cost in dollars, priced from one table in the code.

Against the hosted service

With an API key from the dashboard the same binary manages projects and runs: bugrunner projects, run start, run wait and reports. Self-hosted and CI setups can set BUGRUNNER_API_KEY and BUGRUNNER_API_URL instead of logging in.

SDKs

LanguagePackage state
GoModule in the repository, not published.
PythonPackage bugrunner version 0.1.0 in the repository, not on PyPI.
TypeScriptPackage @bugrunner/sdk version 0.1.0 prepared, not published.

All three wrap the public REST API described in the repository’s OpenAPI file.