Start
Install
Install an exact IAS CLI version from the private release assets, check its identity, and keep your saved work when switching versions.
Get the private release
Version 0.1.1 is distributed through private release assets. You need access to those assets; there is no npm install for this CLI.
Download ias-0.1.1.mjs, ias-install.mjs, release-manifest.json and release-manifest.sha256 from the authorized ias-cli-v0.1.1 release into one directory. Before running the installer, compare its SHA-256 with the trusted release instructions:
shasum -a 256 /path/to/download/ias-install.mjs
For version 0.1.1, expect this installer digest:
6dd9e50d42419fe4364a8045ac95e410f7425261a553869be42e86413d8b0923
If another IAS version is running, stop its service before switching:
ias service stop
Run the installer with the exact version and digest:
node /path/to/download/ias-install.mjs \
--from /path/to/download \
--version 0.1.1 \
--sha256 27ba91b802c3c0e3e906d361d2a4e4d2b847fbed09aa439d55a22a1565224103
Replace the example paths with your download directory. The digest above is specific to version 0.1.1; use the trusted digest for a different version. The installer checks the CLI bytes against the digest and stores the release in ~/.local/share/ias/cli. It links ~/.local/bin/ias to that installed version. Keep ~/.local/bin on your PATH.
IAS_CLI_STORE overrides the default store; otherwise an absolute XDG_DATA_HOME changes its parent. The store must be private and owned by you. Installed files are regular, read-only files. If an existing path is unsafe, the installer refuses it rather than changing its permissions or taking ownership.
Check what you installed
ias --version --json
ias --help
Version output includes the release version, source commit and SHA-256 digest of the running file. For version 0.1.1, compare these fields from the version output with your trusted release instructions:
{
"version": "0.1.1",
"commit": "b160d8c317dbafe65da43695ff37223b2bb9bcbc",
"sha256": "27ba91b802c3c0e3e906d361d2a4e4d2b847fbed09aa439d55a22a1565224103"
}
This check does not sign in or start provider work.
To install without changing a launcher, add --no-link. The installer prints the stored executable path; use node <installed-path> in place of ias in these guides. --store <directory> selects a different private store, and --bin-dir <directory> selects a different launcher directory.
Choose where runs live
IAS keeps runs in ~/.local/state/ias/runs-v1 by default. To select another location, set IAS_HOME to an absolute path outside your repository:
export IAS_HOME="$HOME/ias-state"
Start with a fresh directory instead of records from earlier IAS tools. An optional private config.json in that directory holds local settings. See requirements for directory and provider constraints.
Update or return to a version
Stop the current service, then install the chosen release with its exact version and digest. Check ias --version --json before resuming work. Keep your saved runs and follow that release's compatibility instructions; do not edit records to force an incompatible version to accept them. A refused record needs explicit recovery, not deletion of its history.
Build from source
Developers with repository access can also build a development executable:
pnpm --filter @lucentive/ias-cli build
node packages/ias-cli/dist/ias.mjs \
--help
That standalone file requires Node.js but no workspace packages at runtime. A development build does not identify itself as the versioned private release.
Remove a launcher
Stop the service with ias service stop. If you signed in to One, ias logout requests token revocation and removes local credentials. Remove the launcher you installed, for example rm ~/.local/bin/ias. A --no-link installation has no launcher to remove.
Removing the launcher leaves installed versions and saved runs in their directories. Keep any records you still need to inspect or reconcile.
Next
First run: check your provider and run a local goal.