env-sync-check

To check environment sync status, compare local pyproject.toml versions against the Prime Intellect Environments Hub. The audit reads every environments/* directory, matches project names to hub IDs, and reports mismatches using exact version string equality to clearly identify sync drift.

Environment sync drift occurs when local research environment versions differ from the latest published hub versions. Detecting drift requires fetching the hub environment list via the Prime CLI and comparing the local pyproject.toml version strings against the remote hub entries.

You can audit pyproject.toml versions by running the environment sync check script. It reads each environments/* pyproject.toml, maps the project name to the primeintellect/<name> hub key, fetches hub data via Prime CLI, and separates results into in-sync, out-of-sync, and missing-hub cases.

Yes, you need the Prime CLI installed to detect environment version mismatches. The CLI is required to fetch the latest environment lists from the Prime Intellect Environments Hub, which are then compared against your local pyproject.toml version strings to identify sync drift.

For environments missing from the hub, the version auditing process clearly separates them into a distinct not-on-hub reporting section. It uses a dash marker for the hub version when no matching hub entry exists for the local pyproject.toml project name.