DoctorCli

llm4s doctor as a command line. Run it on the application's own classpath, so it checks the provider modules the application depends on and the application.conf it loads: from sbt, sbt "Test/runMain org.llm4s.doctor.DoctorCli" with llm4s-doctor as a test dependency; without a project, cs launch org.llm4s:llm4s-doctor_3:<version> org.llm4s:llm4s-<provider>_3:<version> -- --config application.conf. See docs/reference/doctor.md.

Options: --config <file> to check a file layered over every module's reference.conf instead of the application's own configuration, --classpath <path> to check the provider modules, reference.conf files and (without --config) application.conf on an application's classpath instead of the doctor's own, --local to ask a model server on this machine which models it has, --live to make one small request, --timeout <seconds> for that request, and --json. Without --local or --live nothing is contacted. Exit code: 0 everything passed, 1 warnings only, 2 something failed.