Skip to main content
The Ekso CLI is a single self-contained binary — no .NET runtime, no package manager, no setup. Download one file, run it. Releases live at github.com/EksoHQ/CLI/releases. One archive per platform, ~30 MB each.

​
Install

VERSION=$(curl -sS https://api.github.com/repos/EksoHQ/CLI/releases/latest | grep tag_name | cut -d'"' -f4 | sed 's/^v//')
curl -L "https://github.com/EksoHQ/CLI/releases/download/v$VERSION/ekso-$VERSION-osx-arm64.tar.gz" | tar xz
xattr -d com.apple.quarantine ./ekso   # one-time: clears Gatekeeper
sudo mv ./ekso /usr/local/bin/
ekso --version
That’s it. No runtime install, no PATH edits beyond moving the binary into /usr/local/bin.

​
Update

Re-run the install command. It always pulls the latest release.

​
macOS Gatekeeper

Binaries aren’t yet signed with an Apple Developer ID, so Gatekeeper quarantines them on first download. The xattr -d com.apple.quarantine ./ekso line in the macOS install steps clears it. If you see “ekso cannot be opened because the developer cannot be verified”, run that command against the downloaded binary, or right-click → Open in Finder once. Code signing is on the roadmap.

​
Verify the download

Each release ships a SHA256SUMS file alongside the archives: 
curl -LO "https://github.com/EksoHQ/CLI/releases/download/v$VERSION/SHA256SUMS"
shasum -a 256 -c SHA256SUMS --ignore-missing

​
Alternative: .NET global tool

Already have .NET 10 installed and prefer the dotnet-tool ecosystem? The CLI is also published to NuGet: 
dotnet tool install -g Ekso.Cli
ekso --version
This is intended for .NET developers who manage CLIs through dotnet tool already. Everyone else: use the standalone binary above. Update with dotnet tool update -g Ekso.Cli. All versions, including pre-releases: nuget.org/packages/Ekso.Cli.

​
Next steps

  • Authenticate — sign in to your tenant via device flow, or supply an API key.
  • Configure — set defaults via environment variables so you don’t repeat --tenant on every call.