PUBLIC FIELD TEST · v0.1.0 · NO SIGNUP

Help test what AI can safely know about a host.

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.

COLLECTIONRead-onlyNo network probes
REPORTINGYou review firstNo automatic upload
WHAT WE SEEKEvidenceNot stars or endorsements
WHY REAL MACHINES MATTER

Three operating systems are not three environments.

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?

Windows · PowerShell, CMD, or Git Bash
macOS · Intel or Apple silicon
Linux · different distributions and shells
Multiple Python or Node.js installations
Docker, Podman, NVIDIA, CUDA, or local AI
Restricted, virtualized, or containerized hosts
A SMALL, REPEATABLE PROTOCOL

About ten minutes. No account. No report submission required.

Keep the report on your machine. Share only a minimal, reviewed excerpt when there is something the project can fix.

01

Download & verify

Choose the native archive for your platform and verify its published SHA-256 checksum.

02

Run both views

Read the terminal report, then generate the versioned JSON contract with aihostcheck --json.

03

Compare locally

Check the result against what you already know about the machine and its active developer toolchain.

04

Report the smallest gap

If something is wrong or unclear, submit only the minimum redacted evidence needed to reproduce it.

WHAT TO REVIEW

Look for the point where an AI could make the wrong choice.

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.

PRIVACY BOUNDARY

Your report stays yours.

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 boundary
WHAT A GOOD FIELD TEST PRODUCES

Confirmed evidence, reproducible gaps, and better tests.

There is no target number of stars. One precise report that exposes a limitation is more valuable at this stage than an unqualified endorsement.