When an investigation finishes, Opriven proposes one or more fixes on the
Fixes
tab of the issue. Opriven does not apply fixes on your behalf. Every fix is reviewed and shipped by an engineer.
What a fix looks like
A fix is one or more steps with rationale — a CLI command, a config change, a code change, or a mix of these.
Every issue produces both an immediate and a comprehensive fix:
Category
What it solves
Immediate
The active symptom. Stops the bleeding so the issue isn’t compounding while you investigate.
Comprehensive
The root cause. Prevents the issue from recurring.
Executing a fix yourself
Use the copy button on a code block to grab a snippet and run it from your terminal, admin console, or pipeline. The
Open in
menu at the top of the fix sends the full plan to your coding agent of choice. Opriven does not run CLI commands or hit provider APIs for you.
Opening a PR
🧪
PR creation is experimental.
Engineers are responsible for validating every change before merging. Opriven will never merge for you.
When a fix includes a code change, you can ship it as a PR directly from Opriven. Before generating the change, Opriven reads your
AGENTS.md
,
CLAUDE.md
, and any Cursor or Copilot rules files in the repo, alongside its memory of your system and past incidents — so the change follows your team’s code style and conventions.
Opriven does not run your tests or builds against the fix. Validate the change locally or in CI before merging.
The action menu gives you two paths: ship the PR (or a draft) straight from Opriven, or take the diff to your own editor or coding agent.
Ship from Opriven
Create PR
opens a pull request on your repo, branching from the default branch. Requires the
GitHub integration
. Once it’s open, treat it like any other PR: push more commits, rebase, or rewrite the diff.
Create draft PR
does the same as a draft, so reviewers aren’t pinged while you tighten things up. Mark it ready when it’s where you want it.
Take it to your editor
Open in Codex / Cursor / Devin / GitHub Copilot
hands the fix and its context off directly so you can keep iterating in your editor.
Copy fix as prompt
copies the fix and surrounding context as a prompt you can paste into any IDE or coding agent.
What an Opriven PR looks like
The PR is authored by
opriven[bot]
, so reviewers can tell at a glance that the change came from an agent.
Opriven tags matching
CODEOWNERS
and assigns a directly responsible engineer for the change, picked by scoring each contributor’s history with the affected code paths.
How to respond to an Opriven PR
When an Opriven PR lands in your queue, you have four paths:
Approve and merge
if the diff is correct as-is.
Take it over the line
by adding commits, rebasing, or rewriting parts of the diff before merging.
Request changes
if the approach is right but the diff isn’t. Leave inline review comments and add any context you have — feedback on what’s off or what the agent missed helps Opriven learn.
Close as not relevant
if the underlying issue no longer applies or the agent misread the situation.