Product
Industries
Roles
Research
Resources

Developers

You run three agents while you work on something else, each in its own terminal, each with its own scrollback. Oxagen records each run as it happens, so you can read it, steer it, and answer it from one place without changing your editor or your harness.

The Runs page with illustrative data, in a browser and on a phone. Twenty runs are live across Claude Code, Codex, stella, and Cursor, and two wait on a person.

The Runs page in a browser and on a phone

Setup

Setup runs on the computer where the agent works.

  1. Install the Oxagen app

    It puts the oxagen command on your PATH.

  2. Enroll your harness

    oxagen agent enroll --harness claude-code adds Oxagen's hooks to Claude Code's settings. Codex, Cursor, and Stella enroll the same way.

  3. Check what is active

    oxagen agent status lists each wrapped harness and whether its hooks are present. Which controls work depends on the harness.

  4. Start a run

    The next run reports to Oxagen.

Steering and skills

Turn a useful correction into guidance the team can reuse. Your team's rules, instructions, and skills live in the workspace's steering repository. Oxagen delivers them to each run when it starts.

The run keeps the steering versions it received. oxagen run show <run-id> prints them, so you can tell what this run was told apart from what the repository says today.

The steering record Read CHANGELOG.md once per run, with illustrative data. It tells agents not to re-read CHANGELOG.md after the first read in a run and to quote the lines the work needs. A change to it waits in pull request #42.

A constraint the team reviewed

Live steering

Send a running agent a message from the run page or the CLI: oxagen steer "Leave the migrations alone and run the tests first" --agent billing-bot. On a host that supports it, the message lands after the tool call in progress. Otherwise it waits for the agent's next prompt. You can cut the model call in flight on runs whose model traffic passes through Oxagen.

The record shows when you sent it and whether the run took it. Cursor takes a message at the end of its turn.

A live run's page with illustrative data, printed the way Claude Code prints it. The transcript holds the prompt and each tool call, and the side column holds the run's tasks, changes, and context.

A live run printed the way Claude Code prints it

Approvals and questions

When a rule sends a call to a person on an agent that waits for the answer, everyone allowed to answer is notified, and the run page shows the call with the rule that sent it. When an agent stops to ask you a question, the run page shows it and you answer there.

Steering a run needs an organization Owner, or a workspace Admin or Member.

Run records

Each run's page shows the transcript the way the harness prints it, with each step's time and cost. It lists the files the run changed, its commits, and the pull requests they landed in, with each pull request's checks.

Oxagen locks the run's record when the agent's host ends the run. Locked means any change after that point shows. A run that starts again is locked again when it ends.

Agent setup

Choose your agent and follow its current install guide.