Install & Connect

Install

The TUI ships as a single static binary — no runtime, no dependencies.

One-liner

The installer downloads the right binary for your platform from the latest release, puts it on your PATH, and (optionally) connects you in one shot. Re-run it any time to update.


# Linux / macOS
curl -fsSL https://raw.githubusercontent.com/ParendumOU/Nexora-CLI/main/install.sh | bash


# Windows (PowerShell)
powershell -c "irm https://raw.githubusercontent.com/ParendumOU/Nexora-CLI/main/install.ps1 | iex"

To install and join an instance in a single command (this is exactly what an admin’s invite one-liner does — see Connect → Zero-touch join):


curl -fsSL https://raw.githubusercontent.com/ParendumOU/Nexora-CLI/main/install.sh | bash -s -- --join <INVITE_TOKEN> --url https://nexora.example.com

Overrides: NEXORA_CLI_VERSION (pin a version, e.g. v0.6.0), NEXORA_CLI_BIN_DIR (install location).

Prebuilt binary

Download the binary for your platform from the project releases , make it executable, and put it on your PATH:


chmod +x nexora
sudo mv nexora /usr/local/bin/
nexora version

Builds are provided for Linux, macOS, and Windows (nexora.exe).

From source

The repo cross-compiles all platforms through a Go container (no Go toolchain needed on the host):


git clone https://github.com/ParendumOU/Nexora-CLI.git
cd nexora-cli
make build          # native binary → ./bin/nexora
make build-all      # linux / darwin / windows → ./dist/

The built binary runs natively; only the build step is containerized.

Connect to an instance

NexoraCLI is a pure client — it connects to your Nexora or NexoraCloud server. Point it at the instance URL, then authenticate with one of four methods.

Zero-touch join

The simplest path for a new teammate: an org admin sends an invite token (from Org → Invites → Invite to the terminal), and join redeems it — creating the account if needed, joining it to the org, and pairing the terminal, all without a prior login.


nexora join --url https://nexora.example.com --token <INVITE_TOKEN>


Account created and joined "Engineering". Saved instance "default". Run `nexora` to start.

The admin’s copy-paste one-liner combines the install and this join into a single command (see Install → One-liner). Both --url and --token can also come from the NEXORA_URL / NEXORA_JOIN_TOKEN environment variables. See Organizations → Zero-touch CLI onboarding for the endpoints behind it.

Interactive login with email/password (and TOTP if 2FA is enabled on the account):


.\nexora.exe login --url https://nexora.example.com

You’ll be prompted for email, password, and — if enabled — your 6-digit TOTP code. Tokens are saved to the config file and auto-refresh on expiry.


Instance URL: https://nexora.example.com
Email: you@example.com
Password:
Logged in. Saved instance "default". Run `nexora` to start.

Device pairing

Pair the terminal as a device using a code from the web UI (Settings → Devices → Add device), the same flow the mobile app uses:


.\nexora.exe pair --url https://nexora.example.com

Paste the device code shown in the browser. The CLI receives a device token (nxd_…) stored in the config; it’s independently revocable from Settings → Devices without affecting other sessions.


Instance URL: https://nexora.example.com
Pairing code: FE3JHGSH
Paired as you@example.com. Saved instance "default". Run `nexora` to start.

API key

Use a personal API key (prefix nxr_…, created in the web UI under Settings → API keys) for non-interactive / scripted setups. Pass it to login with --api-key; the key is saved to the instance config so you don’t pass it each launch:


.\nexora.exe login --url https://nexora.example.com --api-key nxr_xxxxxxxxxxxx

Then run .\nexora.exe to launch the TUI against that instance.

Tokens auto-refresh on a 401. If the refresh token itself is invalid (e.g. the account password was reset, bumping the token version), the TUI prompts you to re-run .\nexora.exe login.

Launch the TUI

Running .\nexora.exe with no subcommand opens the full-screen interface against the current instance:


.\nexora.exe

Multiple instances

The config file can hold several instances; switch the active one without re-authenticating:


.\nexora.exe instance list          # show configured instances + which is active
.\nexora.exe instance use staging   # switch the active instance

The active instance is marked with *:


* default          https://nexora.example.com (you@example.com)

Configuration file

Credentials and instance settings live in a TOML file at the OS config dir:

Platform	Path
Linux	`~/.config/nexora/config.toml`
macOS	`~/Library/Application Support/nexora/config.toml`
Windows	`%AppData%\nexora\config.toml`

The file is written with mode 0600 (owner-only) because it holds tokens. Override the location with the NEXORA_CONFIG environment variable.

The config file contains access/refresh/device tokens. Keep it private and never commit it to version control.

It also stores client-side preferences that persist across launches: the local-execution toggle (local_exec), YOLO auto-approve (local_yolo), and the interface mode (ui_mode, simple / advanced). See Local Execution and The Interface.