Download & verify
Choose the native archive for your platform and verify its published SHA-256 checksum.
AIHostCheck is ready to leave hosted CI and meet real developer machines. Run it locally, inspect every result, and tell us where the evidence is wrong, ambiguous, or incomplete.
Native CI proves that the project compiles and its automated tests pass on Windows, macOS, and Linux. It cannot reproduce the diversity of shells, permissions, package managers, runtimes, GPUs, or corporate restrictions found on real hosts.
A plain laptop is useful. A complicated workstation is useful. The question is the same: can an AI consumer distinguish what is present from what could not be established?
Keep the report on your machine. Share only a minimal, reviewed excerpt when there is something the project can fix.
Choose the native archive for your platform and verify its published SHA-256 checksum.
Read the terminal report, then generate the versioned JSON contract with aihostcheck --json.
Check the result against what you already know about the machine and its active developer toolchain.
If something is wrong or unclear, submit only the minimum redacted evidence needed to reproduce it.
A missing version, ambiguous shell, or false absence can change the command an assistant proposes. Those details are the field test—not whether the page looks convincing.
AIHostCheck has no telemetry and never uploads a report. Do not paste an unreviewed full report into an issue. Remove usernames, hostnames, private paths, IP addresses, organization details, and unrelated identifiers from any excerpt.
Inspect the data boundaryThere is no target number of stars. One precise report that exposes a limitation is more valuable at this stage than an unqualified endorsement.