SAI CLI 0.2.0a2

SAI CLI 0.2.0a2 brings the current hardware views and portable site connection workflow to the installable client.

• Lead with the selected job's CPU/NUMA and GPUs so unrelated hardware does not fill the first screen. Expand the full recorded hardware without another query.
• Inspect a job's recorded CPU/NUMA-to-GPU relationships, GPU connections and available node-fabric links. Verified Slurm-to-Linux mappings place the allocated CPUs on NUMA rows; exact IDs and PCIe details expand on demand.
• Keep resource counts beside their bars, distinguish Slurm configuration from physical packages, and preserve usable scrolling, selection and terminal restoration.
• Select a site for remote native reads without copying its cluster or gateway address. The paired Portal connection service supplies explicitly published metadata; local native queries remain independent of Portal.
• Keep a portable query on the selected site when adding a cluster constraint; reject results outside the requested account, state or partition.
• Follow login, additional-permission, device-resume, pagination and account-readback commands without losing the selected configuration or profile.

Python 3.11+ is required. This alpha is qualified on Linux. Native adapters have been exercised with Slurm 26.05.1 and Lustre 2.17. Hardware views require current site-published records and show missing or expired information as unavailable. Allocation and recorded connections do not measure utilization or communication performance. The initial alpha's artifacts remain unchanged.

Download the wheel and SHA256SUMS, verify the checksum, then install with pipx install ./sai_cli-0.2.0a2-py3-none-any.whl. To add the optional Textual interface, including to an existing base installation, use pipx install --force './sai_cli-0.2.0a2-py3-none-any.whl[tui]'. Upgrade an existing pipx installation with pipx runpip sai-cli install --upgrade ./sai_cli-0.2.0a2-py3-none-any.whl.

Read the first-use guide. Site discovery requires a compatible Portal and an explicitly published client read endpoint. Complete protected profiles remain supported. Updating the client changes neither credentials nor permissions.

First-party code, including the shared native readers and bundled Agent guidance, uses Apache-2.0. Optional dependencies retain their upstream licenses. The separate Slurm GPL patch is excluded from Python distributions. Distribution remains on GitHub; no PyPI publication is included.

Validation: 1273 tests, Python 3.11/3.13 CI, isolated builds, package/provenance checks and synthetic HTTP authorization/recovery flows. Prior bounded site checks verified ordinary-user local/remote job and topology agreement. Independent human first-use, all terminal environments, multiple production sites and Web/Pilot adoption retain separate acceptance boundaries.

SAI CLI 0.2.0a1

SAI CLI's first public alpha combines local Slurm/Lustre queries for people with structured, user-authorized SAI operations for scripts and independently chosen Agents.

• Familiar cluster queries and an optional Textual interface with native account selection, directory quota lookup, and GPU/CPU allocation maps.
• Portable configuration and normal Identity sign-in; offline command discovery and matching bundled Agent guidance.
• Authorized account, job, result and cost reads, default-account changes, and recipient invitation acceptance. Broader management remains in development.

Python 3.11+ is required. This alpha is qualified on Linux; native adapters have been exercised with Slurm 26.05.1 and Lustre 2.17. Scheduler allocation is distinct from utilization, and running estimates are distinct from settled charges.

Download the wheel and SHA256SUMS, verify the checksum, then install with pipx install ./sai_cli-0.2.0a1-py3-none-any.whl. Use pipx install './sai_cli-0.2.0a1-py3-none-any.whl[tui]' for the optional interface. Start with the first-use guide.

First-party code uses Apache-2.0. The separate Slurm patch retains upstream GPL terms and is excluded from the Python distributions. This release is distributed through GitHub, not PyPI; installing the client does not install site services or change cluster defaults.

Validation: 1200 tests, wheel/source builds, installed-wheel checks, terminal restoration and disclosure scans. Live installations and human usability retain their separate acceptance boundaries.