Skip to main content
OpenSRE reads your GitHub Actions history, tells you what unreliable CI costs your team, fixes failing checks on a pull request, and can keep doing that on a schedule. Everything runs against the repositories you already have, on your machine or on your organization’s hosted gateway.

​
Pick a starting point

Measure CI reliability

A 30-day report for one repository: failure rate, CI-caused versus code-caused failures, developer hours lost, red time on the default branch. The recommended first demo.

Fix failing CI on a PR

Read the failing checks, apply a fix with a coding agent, push to the PR branch, and wait for the new checks.

Keep CI green with an agent

A recurring reliability report, a bounded repair loop for one PR, or the managed service that runs repairs for your organization.

Find every red PR

One read-only scan across all repositories your token can see: which PRs and branches are failing, and on which checks.

​
Before you begin

1

Install and sign in

Follow Install. Signing in activates the hosted model; no LLM key is needed.
2

Connect GitHub

The demo offers this when GitHub is not connected yet. To do it yourself:
Choose Authorize in browser, or paste a token that can read Actions history. Fixing and pushing needs Contents and Pull requests write access on the repository. See GitHub.
3

Pick the demo, or ask directly

Start opensre and choose A in the demo picker, or type any of the prompts below.

​
Your first CI/CD tasks

Type these in the shell, with your own repository:
Analysis and the health scan are read-only. Fixing and repair loops push commits; they refuse pull requests opened from forks and never push directly to a protected branch such as main.

​
What each capability does

​
From a script or a CI job

opensre ask runs one turn and exits. The read-only tasks, analysis and the health scan, run headless as they are:
Fixing a PR or scheduling an agent uses tools that need approval, and a headless run has nobody to approve. Authorize the tool the task uses, for that run only:
Each --allowed-tool covers one tool; a task that needs two takes the flag twice. A machine that is not signed in needs LLM_PROVIDER and a provider key plus a GitHub token in the environment. See Headless CLI for --allowed-tool, --json output and exit codes.

​
Where the results go

  • Analysis reports print in the shell; the scheduled agent also saves the raw figures under ~/.opensre/ci_reliability_reports/.
  • A repair pushes to the pull request’s own branch and reports the commit and the check results. /loops show <task-id> prints a finished repair’s report with its evidence links.
  • The banner’s CI/CD fixes counter shows how many distinct repairs pushed checks that passed.