Software and SaaS
Connect software work to agent runs, pull requests, checks, and costs across supported tools. Review what changed before accepting the work.
Work
A billing bug arrives from GitHub as work. One engineer runs Claude Code on it, a teammate reviews in Codex, and a third adds a regression test in Cursor. The reason for the change ends up spread across three tools and a pull request.
Give each work item a record your whole team can follow. Oxagen puts them on one work item. The work comes from your tracker, each run comes from the agent that did the work, and the pull request and its required checks come from GitHub. A person approves the Done Checklist before the work is sent and accepts the head commit after reviewing it, with the checks recorded beside the acceptance.
How work moves across agents
An illustrative billing work record from a tracker, with a Claude Code run that wrote the fix, a Codex run that reviewed it, a Cursor run that added a test, its pull request, and acceptance still open.
A work item with runs from several agents
- Work
- Credit a paid invoice once when the webhook repeats
- Claude Code
- Wrote the fixDone
- Codex
- Reviewed the pull requestDone
- Cursor
- Added a regression testDone
- Pull request
- Required checks passed on the head commitDone
- Acceptance
- Waiting for a personOpen
Mandates
Each repository's agents start from the same reviewed steering, the same tools, and the same rules, whichever engineer's laptop they run on. When an agent asks to merge to main or run a migration through Oxagen, a rule your team wrote allows it, denies it, or routes it to a named person.
Runs
Open the run behind the pull request to see the prompts, the tool calls with the rule that answered each one, the files git reports as changed, and the cost of the model calls Oxagen recorded. Cursor's model calls go to its own servers, so their cost is not in the record.
Product walkthrough
Bring a piece of software work and review its runs, checks, and result.