Developer tools

Developer tools

Developer tools

The iohr command line, the client libraries, extensions and the agent, where to get each and what state it is in.

Everything here is open source under Apache-2.0, in two repositories: inorbithr/sdk (the command line and the libraries) and inorbithr/dataplane (the agent).

ToolPackageState on 2026-10-07
Command lineiohr: APT, Homebrew, installers0.1.0-alpha.11, pre-release
Rustinorbithr on crates.io0.2.2
TypeScript@inorbithr/sdk on npm and JSR0.2.2
Pythoninorbithr on PyPI0.2.2
Gogithub.com/inorbithr/sdk/go0.2.3
C#InOrbit.Sdk0.2.2, built from source; not on NuGet yet
Javahr.inorbit:inorbit-sdk0.2.2, built from source; not on Maven Central yet
Extensionsiohr ext, signed OCI artifactspre-release, one extension: the agent
The agentiohr-agent: extension, Helm chart, image, .deb, .rpm0.1.0-alpha.7, pre-release

Versions before 1.0 are pre-releases: commands and output can still change between them. Only the latest release gets fixes.

Where to start

  • Calling the API from a terminal or CI: install iohr, then iohr login and iohr api GET /v1/me.
  • Calling it from code: add the library for your language, or let iohr sdk generate write a client cut to what your credentials may call: Generate an SDK for your account.
  • Checking what our cloud cannot reach: run the agent in your own network. It dials out, obeys a local policy and reports timings, never content.
  • Letting InOrbit act in your other tools (incident, chat, AI providers): Connections.
  • Using InOrbit from an assistant (Claude Code, Cursor and others): the MCP transport.

Checking what you install

Every release in both repositories is built by its release workflow on GitHub Actions and carries build provenance you can check with gh attestation verify. The command line's APT repository is signed with a key used for nothing else; extensions and the agent's image and chart are signed keyless with cosign. Each page here has the commands.