Installation
A3S Box provides native launchers for every supported host:
install.shfor Linux and macOS, without requiring PowerShell.install.ps1for Windows, without requiring Bash.
Both launchers resolve a GitHub release, verify its SHA-256 digest before extraction, validate the package layout and reported version, and replace a previous installer-managed copy as one staged operation.
Supported release targets
Intel macOS and Windows on ARM are rejected rather than receiving an incompatible archive. The installer does not enable KVM, HVF, WHPX, or Linux Sandbox host capabilities.
One-line installation
Linux or macOS:
Windows PowerShell 5.1 or newer:
Homebrew on Linux or macOS:
Open a new terminal if the current process does not see the updated PATH,
then verify the runtime:
A network pipe executes the current main installer. Download and review the
launcher first when your environment requires a pinned or audited script.
Pin a version or destination
Pass Unix options after sh -s --:
Invoke downloaded PowerShell text as a script block when options are needed:
The corresponding environment variables are A3S_BOX_VERSION,
A3S_BOX_INSTALL_DIR, A3S_BOX_ARCHIVE, and A3S_BOX_SHA256.
Managed upgrades
Every successful install writes .a3s-box-install.json in its destination. A
later installer run may replace a directory carrying that marker. A non-empty
directory without the marker is left untouched unless force is explicit.
The new package is copied to a sibling staging directory and checked before activation. If activation or the final version check fails, the previous managed directory is restored.
Uninstall
Delete the exact installation directory reported by the installer. On Unix,
remove the block between # >>> a3s-box installer >>> and
# <<< a3s-box installer <<< from the selected shell profile. On Windows,
remove that installation directory from the per-user PATH.
Uninstalling binaries intentionally does not delete runtime state stored elsewhere.
Next step
Continue with the quick start or review the platform matrix before running production workloads.