CLI overview

oxagen is the terminal for fleet management on the Oxagen agent control plane. It answers the questions an operator asks about a fleet: what each agent did, what context it had, what it cost, and what its mandate lets it ask for next.

Oxagen governs, grounds, explains, meters, and rates agents. It does not run them. The coding agent is the stella CLI, which reaches Oxagen over MCP and the platform API.

Who this is forCopy Anchor Link

These docs are for developers and platform operators. You should be comfortable with a terminal, a package manager (npm or pnpm), and environment variables. No Oxagen-specific knowledge is assumed.

What you can doCopy Anchor Link

• Map the code. oxagen codegraph indexes a repository on this machine for your agents and uploads CI results into the Oxagen code graph.
• Meter and bill. oxagen budget sets and reads hard period-to-date spend ceilings for an org or workspace, with live burn against each one. oxagen cost prices token usage from the rate card built into the CLI before you spend anything.
• Explain a run. oxagen run turns <run-id> lists each turn of one run with its model and tool steps, tokens and cost. oxagen run transcript <run-id> prints what the agent did.
• Ground answers. oxagen graph search runs a bounded, workspace-scoped semantic search over the knowledge graph. See Knowledge graph from the CLI.
• Curate what agents learn. oxagen memory lists the memories your agents wrote in their harnesses, ranked by how often runs used them, and promotes the ones worth keeping into steering records.
• Govern the workspace. Manage environments and the workspace default (oxagen env), and read or write the workspace's encrypted credential vault (oxagen secret).
• Route by cost. oxagen router reads the verified-outcome market router: observed outcomes per task class and model, and the governed routing policy.

One credentialCopy Anchor Link

The CLI needs one credential: an Oxagen API key (ox_…) plus the org and workspace it acts in. The key identifies you, the person running the CLI, to the Oxagen API. oxagen login mints and stores all three.

The CLI makes no LLM calls of its own, so there is no model provider key to configure.

oxagen cost, oxagen logs, and oxagen telemetry work offline with no credential.

Next stepsCopy Anchor Link

• Installing the CLI: get the oxagen binary onto your machine.
• Account setup: create an Oxagen account and authenticate the CLI.
• CLI quickstart: link a project, then read your first run and budget.
• Command reference: every command and flag.