oxagenDocs
Releases

v5.5.0 (beta)

5.5.0 is the last beta before general availability. It ships cloud sandboxes for coding agents, a prepaid billing wallet, 31 dashboards, a work items board, and production on Google Cloud.

Get 5.5.0

Every file has a SHA-256 in SHA256SUMS.txt.

Oxagen app for macOS

macOS 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.

Oxagen app for Windows

Windows 10 or newer, x64.

Oxagen app for Linux

x86_64. Install the package for your distribution.

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.

Command line, without the app

The same recorder and oxagen executables the app links onto your PATH, one file each, on downloads.oxagen.sh beside the installers. Each has a .sha256 beside it. Rename the file to recorder or oxagen, make it executable, and put it on your PATH.

Platformrecorderoxagen
macOS, Apple silicon
aarch64-apple-darwin
recorderoxagen
macOS, Intel
x86_64-apple-darwin
recorderoxagen
Linux, x86_64
x86_64-unknown-linux-gnu
recorderoxagen
Windows, x64
x86_64-pc-windows-msvc
recorder.exeoxagen.exe
Also in this release

Beta pre-production release. 5.5.0 is the last beta of Oxagen before general availability.

What changed

5.5.0 ships cloud sandboxes for coding agents, a prepaid billing wallet with allowance alerts, 31 dashboards, a board view for work items, and production on Google Cloud.

Coding agents run in cloud sandboxes

A person can start a Claude Code, Codex, or Stella run in a cloud sandbox from the app, a Stella thread, oxagen sandbox run, or the launch_sandbox_run MCP tool. A send from a Stella thread waits as an approve or deny card. Each run checks out every repository the workspace links. A Claude Code run that hits every model account's usage limit waits for the reset and continues. A headless Stella run that hits its limits ends instead. Several agents can share one sandbox by taking turns, when the workspace turns that on. The run terminal opens in a drawer and pauses the run before anyone types. Broken sandbox configuration is refused at launch, and a run that passes its work item's time limit ends cleanly.

Billing wallet, allowance alerts, and credit refunds

Seats are paid up front, and every wallet change writes one keyed ledger row. A model call on Oxagen's key is priced before it runs. Actions count against the month's allowance, and new runs wait when the wallet passes its floor or a seat payment fails, while started runs finish. Billing owners get an in-app notice and an email at 50, 80, and 100 percent of the month's allowance. Credit refunds, a billing portal session, and sandbox slot purchases are available through the API and MCP. Enterprise contracts invoice yearly with credits that expire in 12 months.

31 dashboards

/{org}/dashboards lists 31 dashboards, each with the questions it answers. They cover spend and outcomes, unproductive spend, operator ranking, task completion, model and effort fit, ready work, CI, codebase health, duplicate code, module coupling, documentation gaps, and more. The Console shows a few of them by default. Spend moved under Reports and takes any set of workspaces, a calendar range, and a comparison. The codebase dashboards need the code graph.

Work items board and bulk review

Work items display as a board. A drop opens the action the move means, such as approve, send, retry, or close, and the card moves once the write lands. Reviewers accept results in bulk, edit work rows in place, and record who accepted and approved. Stella, MCP, and the CLI add, edit, delete, or re-triage up to 100 items per call. The Done Checklist ticks when a person accepts the work.

Run page, transcript, and task plan

The Run page shows the agent's task plan under Run details. The transcript reads as a conversation, with XML messages drawn as readable panels, or as a timeline that replays from the first step. The page lists loops, refusal groups, setup failures, and failing MCP tools, and a refused model call shows its model and reason. Runs on a phone show a scope switch, one filter sheet, and two-line rows with linked work.

MCP Studio and model credentials

The MCP server Test tab opens with sample arguments in the tool's input shape, and every field of a server's tools is editable in the Tools table. Model credentials belong to the person and serve their runs in every organization they work in. A run on a laptop moves to the next saved credential when one is out of usage. A refused model login is repaired on the owner's enrolled machine, and oxagen workspace use points a device at one workspace.

Production on Google Cloud

Production runs in Google Cloud's Virginia region. Every main commit that passes CI deploys to production. The CI controller runs on Google Cloud, and the code graph worker runs with its own database login and limited privileges.

Pricing and the website

Team and Business seats, one credit pack, and sandbox slots are sold from the Billing page. The website draws the control plane, team runs, and spend, and shows the Team and Business prices.

On this page