Command line

iohr is the InOrbit command line: it signs you in, keeps each account you use as a profile, manages API tokens and makes authenticated calls. It is open source (Apache-2.0) in inorbithr/sdk and talks only to api.inorbit.hr and auth.inorbit.hr: no telemetry, no update check.

InstallCopy Anchor Link

brew install inorbithr/tap/iohr

The scripts are short; read install.sh or install.ps1 before you pipe them to a shell. Each downloads the archive for your machine from the GitHub release, refuses it unless its SHA-256 matches the release's SHA256SUMS, checks its build attestation when the GitHub CLI is installed and signed in, and copies one binary. Every release also has plain archives, a .deb and an .msi: github.com/inorbithr/sdk/releases.

Checking what you installedCopy Anchor Link

The APT repository is signed with a key used for nothing else. Compare what you fetched:

gpg --show-keys /etc/apt/keyrings/iohr.gpg

Every release file carries a build provenance attestation from the SDK repository's release workflow:

gh attestation verify iohr-0.1.0-alpha.11-x86_64-unknown-linux-musl.tar.gz --repo inorbithr/sdk

Sign inCopy Anchor Link

iohr login
iohr whoami

On a machine with a browser, iohr login opens the InOrbit sign-in page and waits up to five minutes for it to come back to the terminal. Over SSH, in a container or without a display it prints a link and a short code instead: open the link on any device, sign in, and enter the code. --web and --device choose one. Only ever enter a code that you started yourself.

A signed-in session keeps a 15-minute access token and a 30-day refresh token, replaced on every use, in the operating system's credential store (macOS Keychain, Windows Credential Manager, the Secret Service on Linux); iohr refreshes it on its own. The console's sign-in devices list shows the session and can end it. iohr logout revokes it at the sign-in service, then forgets it on this machine.

ProfilesCopy Anchor Link

A profile is one way of calling the API: who signed in, and which account the calls count against. Keep one per account:

iohr login --profile acme          # a second sign-in, for your team's account
iohr profile list
iohr profile use acme              # the default from now on
iohr whoami --profile personal     # or pick one per command

--profile wins over IOHR_PROFILE, which wins over the default. Nothing depends on a global switch, so two terminals can use two profiles at once.

API tokensCopy Anchor Link

iohr token create --name ci --scope radar:read --days 30
iohr token list
iohr token revoke <id>

token create prints the token once, on its own line, and nowhere else. A token never goes on the command line, where shell history and the process list would keep it; to sign in with one, pipe it in:

iohr login --with-token --profile ci < token.txt

In CICopy Anchor Link

Set IOHR_TOKEN and nothing is written to disk:

IOHR_TOKEN="$INORBIT_TOKEN" iohr api GET /v1/radar/digests -f limit=5

iohr api <METHOD> <PATH> makes one call with the active credential and prints the JSON answer; -f key=value adds a string field, -F key=json a typed one, --input file a body.

An SDK for your accountCopy Anchor Link

iohr sdk generate --lang rust --for personal --for ci --out src/iohr   # or typescript, go, python, csharp, java
iohr sdk check

sdk generate writes a client with exactly the operations each profile's credential may call, and sdk check fails in CI when that set has moved: Generate an SDK for your account.

Exit codesCopy Anchor Link

Every command takes --json for machine-readable output and --verbose for method, path, status, time and request id on stderr (never a header, a query value or a body).