ShvIA
SIGN IN

ShvIA Desktop

Version — · manifest generated —

  • — the published version, read from the manifest
  • — platforms only what has actually been published
  • auto-update install once — the app updates itself from this same manifest
  • sha256 on every file, to check what you downloaded

Every published file

One row per artifact, with the size and the full sha256 the manifest declares. Nothing here is estimated — if the manifest cannot be read, the list stays empty and says why, because a made-up version number is worse than no list.

Windows

Windows is not in the published manifest. The project builds for Windows, but no Windows artifact has been published to the channel this page reads, so none is listed. This absence is the honest reading, not an omission — the page shows what exists and nothing else.

Checking what you downloaded

Every file carries a sha256 in the manifest. Compare it against the file you got:

terminal — checksum 
# Linux — paste the filename from the row above
$ sha256sum FILE
# macOS
$ shasum -a 256 FILE

Some rows are also marked signed: those carry a minisign signature, which is what the updater itself verifies before installing an update. The rows marked sha256 only are the ones the updater does not consume — for those, the checksum is the check.

Where this comes from

The desktop client is a native window over the same ShvIA the browser serves, and it carries the anna CLI inside the installer. It updates itself: you install once, and the app pulls later versions from the very manifest that filled this page. That is why this list cannot fall behind what the app trusts — there is only one file, and both read it.