T
Tracer-Cloud/opensre
The open-source agent for CI/CD reliability.
★ 13,049·updated 2026-11-19
View on GitHub ↗Direct link · no redirect page
- Star count
- 13,049 ★ · Tracer-Cloud/opensre · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-20 · last seen 2026-11-20 · seen 1× · listed by 1 sources
FAQ (answers come from our records)
Who is it for?
We have no tags recorded for it yet.
Who maintains it?
repository
Tracer-Cloud/opensre;first catalogued 2026-11-20;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
OpenSRE: The open-source agent for CI/CD reliability
Excerpted from the repository README (abridged)
Your CI tells you it broke, but not why or how to fix it. OpenSRE is a CLI agent that reads the failed run, traces the cause and pushes a fix for you to review. Self-hosted, with your own models.
Quickstart ·
Docs ·
FAQ ·
Security
> 🚧 Public Alpha: Core workflows are usable for early exploration, though not yet fully stable. The project is in active development, and APIs and integrations may evolve.
## Before you begin
Make sure you have:
A terminal open in a code project
A Git repository (recommended for the full workflow demonstration)
## Step 1: Install and start opensre
macOS or Linux:
bash
curl -fsSL https://install.opensre.com | bash -s -- -gh
Windows (PowerShell):
powershell
& ([scriptblock]::Create((irm https://install.opensre.com/install.ps1))) -gh
Then start OpenSRE:
bash
opensre
Windows details: Windows.
The installer fetches the latest build from main without requiring sudo. If opensre is not found, follow the PATH instructions printed by the installer or open a new terminal.
For supported platforms and troubleshooting, see Install locally.
## Table of Contents
Before you begin
Install and start opensre
Why OpenSRE?
Quick Start
Deployment
How OpenSRE Works
Integrations
Security
Telemetry
License
Citations
## Why OpenSRE?
AI writes more of the code every month. Someone still has to fix the build.
When CI goes red, it tells you _that_ something failed, not _why_ or how to fix it. Under deadline pressure, teams hit re-run and move on, flaky checks pile up, main stays red, and the real investigation waits for whichever senior engineer has time. OpenSRE is an open-source CI/CD reliability agent that does that investigation for you, built to run on your own infrastructure with your own models:
Recover from red builds faster: it investigates the moment a run fails, reading logs, testing hypotheses and pushing a fix for you to review
Fix the cause, not just the rerun: it separates CI-caused failures from code-caused ones, so you fix the right thing
Know what CI is costing you: failure rate, developer hours lost to unreliable CI, and how long main stays red
Senior-level context for everyone: every engineer gets the same depth of analysis
SWE-bench 1 showed that agents improve fastest with realistic tasks and clear feedback. Pipeline failures are slower, noisier and harder to reproduce than local code tasks, so we hold OpenSRE to the same standard by:
running real-world end-to-end tests across cloud-backed scenarios (tests/e2e)
keeping semantic test-catalog naming so e2e vs unit and local vs cloud boundaries stay obvious (tests/README.md)
Start with the CI/CD overview: analyze a repository's CI reliability, fix failing checks on a PR, or set up an agent that keeps CI green.
1 https://arxiv.org/abs/2310.06770
## Quick Start
Contributors: start at main.py for the process entrypoint map.
Run opensre to sign in and get started. The first launch activates the hosted model.
bash
opensre
Webapp contributors can run opensre setup --dev to authenticate through http://localhost:3000.
Interactive shell — with no subcommand, opensre validates your account and starts a REPL (TTY required). You can exit and stay signed out, but the shell only opens for an active account. Describe incidents in plain language, watch the agent work, and use slash commands for session control (/help, /status, /cost, /sessions, /resume, /compact, /new, /exit) and integrations (/integrations list, /integrations verify). Ctrl+C cancels an in-flight turn without losing session state. See interactive shell commands for the full reference.
Quickstart ·
Docs ·
FAQ ·
Security
> 🚧 Public Alpha: Core workflows are usable for early exploration, though not yet fully stable. The project is in active development, and APIs and integrations may evolve.
## Before you begin
Make sure you have:
A terminal open in a code project
A Git repository (recommended for the full workflow demonstration)
## Step 1: Install and start opensre
macOS or Linux:
bash
curl -fsSL https://install.opensre.com | bash -s -- -gh
Windows (PowerShell):
powershell
& ([scriptblock]::Create((irm https://install.opensre.com/install.ps1))) -gh
Then start OpenSRE:
bash
opensre
Windows details: Windows.
The installer fetches the latest build from main without requiring sudo. If opensre is not found, follow the PATH instructions printed by the installer or open a new terminal.
For supported platforms and troubleshooting, see Install locally.
## Table of Contents
Before you begin
Install and start opensre
Why OpenSRE?
Quick Start
Deployment
How OpenSRE Works
Integrations
Security
Telemetry
License
Citations
## Why OpenSRE?
AI writes more of the code every month. Someone still has to fix the build.
When CI goes red, it tells you _that_ something failed, not _why_ or how to fix it. Under deadline pressure, teams hit re-run and move on, flaky checks pile up, main stays red, and the real investigation waits for whichever senior engineer has time. OpenSRE is an open-source CI/CD reliability agent that does that investigation for you, built to run on your own infrastructure with your own models:
Recover from red builds faster: it investigates the moment a run fails, reading logs, testing hypotheses and pushing a fix for you to review
Fix the cause, not just the rerun: it separates CI-caused failures from code-caused ones, so you fix the right thing
Know what CI is costing you: failure rate, developer hours lost to unreliable CI, and how long main stays red
Senior-level context for everyone: every engineer gets the same depth of analysis
SWE-bench 1 showed that agents improve fastest with realistic tasks and clear feedback. Pipeline failures are slower, noisier and harder to reproduce than local code tasks, so we hold OpenSRE to the same standard by:
running real-world end-to-end tests across cloud-backed scenarios (tests/e2e)
keeping semantic test-catalog naming so e2e vs unit and local vs cloud boundaries stay obvious (tests/README.md)
Start with the CI/CD overview: analyze a repository's CI reliability, fix failing checks on a PR, or set up an agent that keeps CI green.
1 https://arxiv.org/abs/2310.06770
## Quick Start
Contributors: start at main.py for the process entrypoint map.
Run opensre to sign in and get started. The first launch activates the hosted model.
bash
opensre
Webapp contributors can run opensre setup --dev to authenticate through http://localhost:3000.
Interactive shell — with no subcommand, opensre validates your account and starts a REPL (TTY required). You can exit and stay signed out, but the shell only opens for an active account. Describe incidents in plain language, watch the agent work, and use slash commands for session control (/help, /status, /cost, /sessions, /resume, /compact, /new, /exit) and integrations (/integrations list, /integrations verify). Ctrl+C cancels an in-flight turn without losing session state. See interactive shell commands for the full reference.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/tracer-cloud-opensre/)
- Source
- github · https://github.com/Tracer-Cloud/opensre
- Traction
- 13,049 ★
- added
- today