Oxagen CLI
Run your agents as a fleet.
The oxagen CLI puts the fleet in your terminal: the same knowledge graph, the same scoped retrieval, and the same audited invoke() boundary as the app. One command installs it.
Installation
Skills, binary, sign in.
Two commands install it and one verifies it, in the order the terminal above types them.
- 01
Install the agent skills
The skills pack carries the reusable skills, workflows, prompts, and tool definitions the CLI loads at startup. One npx command unpacks them to ~/.oxagen/skills.
npx @oxagen/skills@latest install - 02
Install the binary
install.sh detects your platform, downloads the matching oxagen executable, checks its SHA-256, and installs it to ~/.local/bin. If that directory is not on your PATH, the script prints the line to add to your shell profile.
curl -fsSL https://docs.oxagen.sh/install.sh | sh - 03
Verify and sign in
Run oxagen --version to confirm the install. Then run oxagen login to sign in to your organization and workspace.
oxagen --version
install.sh
The install script
install.sh downloads one file and checks it before it installs anything. Read it before you run it.
- Detects your platform. macOS on Apple silicon or Intel, or Linux on x86_64. The script downloads the matching executable from downloads.oxagen.sh.
- Verifies the checksum. The script downloads to a temporary directory and checks the file against its published SHA-256 before it installs anything.
- Installs to ~/.local/bin. If that directory is not on your PATH, the script prints the line to add to your shell profile.
- Never runs sudo. The executable lives in your home directory. To uninstall, delete ~/.local/bin/oxagen. If the script fell back to npm, run npm uninstall -g @oxagen/cli instead.
Other ways to install
On a CI runner or in a container, download the executable for your platform from downloads.oxagen.sh. It carries its own runtime, so it needs no Node.js.
The CLI is also on npm as @oxagen/cli, for Node.js 20 or newer. The installation guide covers each way to install.
Give agents the business context their work requires.
The CLI reads the same knowledge graph and the same record as the app and the API. Sign in and your workspace graph is on the other end of the prompt.