Download the Nexa CLI

Verify your download

Every artifact's SHA-256 checksum is listed above. After downloading, confirm it matches before running the binary:

shasum -a 256 <downloaded-file>

On Linux, sha256sum does the same thing. Compare the result to the checksum in the table above; if they differ, do not extract the archive.

Install

Extract the archive and run the installer inside it. It puts Nexa under your home directory and links it onto your PATH, so it never asks for a password and never touches a system directory.

tar -xzf nexa-macos-arm64.tar.gz
./nexa-macos-arm64/nexa install

nexa install reports whether ~/.local/bin is already on your PATH and prints the single line to add if it is not — macOS does not include it by default. It does not edit your shell startup files itself. A startup file applies to shells started afterwards, so open a new terminal before continuing.

Check it works

nexa --version

If the shell reports that the command is not found, ~/.local/bin is not on your PATH yet.

Connect it to Rinko Hub

Nexa works entirely on its own — you can create repositories, record versions and synchronize with peers without an account. Connect it only when you want hosted repositories:

nexa login

Running it opens your browser, where you approve this device. After that the CLI can reach the repositories your account is permitted to use. Nothing is copied out of the browser and no token is ever pasted into a terminal — approval happens in Rinko Hub and the CLI collects the result itself.

Updating

Once Nexa is installed it updates itself. nexa update --check reports whether a newer release exists without changing anything; nexa update installs it. The installation nexa install creates is exactly the one the updater maintains, so nothing has to be reconfigured later.

An update replaces one file: the nexa binary. Your repositories, your Development Roots, your configuration and your device authorization are untouched, because none of them live inside it. A download that fails verification leaves the version you are running active.

Installing somewhere else

nexa install is the supported path, and where it puts things is its own business — the layout is internal and may change between releases. If you would rather place the binary yourself, extract the archive and put nexa anywhere on your PATH. It runs from any location.

A copy placed by hand is not a managed installation, so nexa update declines to replace it and says so rather than writing over a file it does not own. Run nexa install once to convert it into one. A Nexa installed by a package manager stays that package manager's to update.

mkdir -p ~/.claude/skills
unzip -o rinko-hub-skills-claude-code-1.0.0.zip 'rinko-hub-*/*' -d ~/.claude/skills

mkdir -p ~/.agents/skills
unzip -o rinko-hub-skills-openai-codex-1.0.0.zip 'rinko-hub-*/*' -d ~/.agents/skills