Your workspace, one command away.
The oxagen CLI brings the governed agent to your terminal — the same knowledge graph, the same RBAC-scoped retrieval, the same audited invoke() chokepoint. Install it in seconds; no shell-profile surgery.
Skills, binary, go.
Two commands to install, one to verify — exactly the sequence the terminal above is typing.
Install the agent skills
The skills pack ships the agent's reusable capabilities — workflows, prompts, and tool definitions the CLI loads at startup. One npx command unpacks them to ~/.oxagen/skills.
$ npx @oxagen/skills@latest installInstall the binary
install.sh detects your platform, fetches the matching oxagen binary, verifies its checksum, and places it in ~/.local/bin — a directory already on your PATH, no shell-profile edits required.
$ curl -fsSL https://cli.oxagen.sh/install.sh | shVerify and go
Run oxagen --version to confirm the install, then oxagen login to connect your organization and workspace. Your first question is one command away.
$ oxagen --versionA boring install script, on purpose.
install.sh does four predictable things and nothing else — read it before you run it, we insist.
- Detects your platform. macOS or Linux, arm64 or x64 — and fetches the matching prebuilt binary.
- Verifies the checksum. The download is checked against a published SHA-256 before anything touches disk.
- Installs to ~/.local/bin. The XDG-standard user binary directory, already on PATH in modern shells — no profile edits.
- Never needs sudo. Everything lives in your home directory; uninstalling is deleting one file.
Prefer a package manager?
The CLI is also published to npm — install it globally with your package manager of choice and get the same binary on your PATH.
Full options — building from source, the portable single-file bundle for CI runners — are in the installation guide.
Installed? Ask something.
The CLI speaks to the same governed platform as the app and the API — log in and your workspace knowledge graph is on the other end of the prompt.