Getting started
Create an organization and workspace, register an agent, and inspect its recorded work.
Give an agent an identity, then set its authority, budget, tools, and skills in its mandate. Oxagen checks actions routed through its control plane and records the result.
Create your organization and workspace
- Open app.oxagen.sh and choose Sign up.
- Enter your name, email, and password. Follow the verification email when the deployment requires it.
- Name your organization and its first workspace on the New organization screen.
- Review their slugs and create the organization.
The first workspace opens at /{org}/{workspace}. This is Runs. Local development skips email verification. See Local development.
Find the right page
| Page | What you manage |
|---|---|
Runs, /{org}/{workspace} | Recorded agent activity and work awaiting attention |
| Agents | Agent identities and enrollment |
| A run | The recorded steps, decisions, and cost for that run |
| A mandate | The authority and equipment assigned to an agent |
| Tools | Tool registry, connections, kill switches, and the mandate ledger |
| Steering | Instructions and rules |
| Spend | Recorded usage and cost |
| Skills | Skills assigned to agents |
Organization, /{org} | Workspaces and membership |
| Organization → Roles | Roles and their permissions |
| Organization → API keys | Keys scoped to a workspace |
| Organization → Audit | Security event records |
| Organization → Billing | Subscription and credits |
| Organization → Model funding | Who pays for model calls |
Install the Oxagen app
Install the app on the machine that runs the agent. On first launch it links the oxagen command onto your PATH, and the enrollment command below needs it.
The newest Oxagen app for each platform
Every version, with SHA-256 checksumsmacOS 12 or newer. Open the .dmg and drag Oxagen to Applications. Builds are not yet notarized, so macOS refuses the first launch. Choose Done, then click Open Anyway in System Settings > Privacy & Security.
- Apple silicon (.dmg)Oxagen_aarch64.dmg
- Intel (.dmg)Oxagen_x64.dmg
Windows 10 or newer, x64.
- Installer (.exe)Oxagen_x64-setup.exe
- Installer (.msi)Oxagen_x64_en-US.msi
x86_64. Install the package for your distribution.
- .deb (Debian, Ubuntu)Oxagen_amd64.deb
- .rpm (Fedora, RHEL)Oxagen.x86_64.rpm
- AppImage (any distribution)Oxagen_amd64.AppImage
On first launch the app links the oxagen and tacho commands onto your PATH, so a new terminal can run them.
On macOS, the app installs new versions on its own and runs them after your next restart. Windows and Linux ask first. How updates work and how to turn them off.
Register and enroll an agent
Open Agents and follow the registration flow. Run the enrollment command it gives you on the machine that runs the agent:
oxagen agent enroll --token <one-time-enrollment-token> --harness claude-code
oxagen agent statusThe token identifies the organization, workspace, and registered agent. It expires after 30 minutes and can be used once. Enrollment installs the collector and the selected harness hooks. See Wrap an agent for the recording boundary and custom agents.
Run a task in the wrapped harness. Open Runs to inspect the record that arrived. Observe mode records what the policy would decide on a governed call and lets the call go ahead. Operator controls, and the budget and model limits on model calls routed through Oxagen, still apply. Hook checks depend on the installed wrapper, and calls outside the routed boundary are not governed by Oxagen.
Use the CLI, API, or MCP
Run oxagen login for a browser-authorized CLI credential. For a script or MCP client, create a workspace-scoped key at Organization → API keys and copy it when shown.
API authentication explains the different key purposes. The API overview provides a first request. Connecting to MCP provides client configuration.
Next steps
- CLI quickstart: inspect a budget, run, and workspace memory.
- Agent roles: choose the authority an agent needs.
- Security overview: inspect the controls and their scope.