Skip to content
Docs

Check a repository with rad doctor

Run the local checks after installation or when planning fails:

Terminal window
rad doctor
rad doctor --json

rad doctor checks manifests, lockfiles, supported languages, test runners, and missing setup. Python checks project metadata, the selected Python environment, pytest, tests, and mutation execution support. TypeScript/JavaScript checks the package and Vitest signals. For Go, it accepts a root go.mod or go.work, requires Go 1.25.x or 1.26.x on Linux or macOS with amd64 or arm64, inspects go env, and runs clean tests with the test cache disabled. A workspace is tested one module at a time. See Language support and Go support for the compatibility details.

The command warns when it finds CGo files, assembly, or build-constrained Go files. Radforge can use those files as dependencies when the active build permits it, but does not mutate CGo or assembly files. It does not modify the repository. Use --language when automatic detection selects the wrong workspace or the repository contains multiple languages.

Fix each reported problem in the project itself. For example, installing Vitest is not enough if the project’s tests use another runner.

Local doctor and hosted doctor answer different questions:

  • rad doctor checks whether the local repository can be planned.
  • rad remote doctor checks the API token, repository access, CLI and server compatibility, supported languages, and upload limits.

Run both before contacting support about a hosted failure. Include their JSON output after removing secrets and private paths.