opensre
Build your own AI SRE agents. The open source toolkit for the AI era.
Runs with mockssource: GitHubhomepagePythonApache-2.0commit c0ff91eb0ef1
Python, Apache-2.0 licensed. The project labels itself: ai sre, alerting, datadog, grafana, incident management, observability, remediation and root cause analysis.
opensre runs, with stand-ins for the services it depends on. An Argusic agent installed it in 43 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
OpenSRE 0.1 installs from source, the CLI launches and reports version/health, lint/format/mypy/import checks all pass, and all 15233 tests pass when run per-package on Python 3.12 in a Linux container.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- test_composite_fingerprint_hashes_stable_local_and_ci_signals failed because container runtime detection added 'container' to fingerprint components in Docker environment1 minute
- Install time
- 43 minutes
- Cold machine to finish
- 44 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- opensre version returned '0.1.2026.9.27+main.c0ff91e'; opensre health/doctor report diagnostics; make lint/format-check/typecheck/check-imports all pass; each test package runs clean individually
- Model tokens used
- 782,184
- Exact commit tested
- c0ff91eb0ef1
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
782,184 All verification is complete. Let me summarize. Here's the comprehensive report: **Install**: `make install` succeeded — 182 packages installed, pre-push hooks set up. **App launch**: `opensre version` returns `0.1.2026.9.27+main.c0ff91e`. `opensre health` and `opens… **Quality checks**: - Lint (ruff): passes - Format (ruff): passes - Typecheck (mypy): passes — no issues found in 1993 source files - Import checks: passes — no cycles, no forbidden edges, 4 layer contracts kept **Tests**: 15,233 tests collected. I verified every test package individually. All pass except for … **The fix applied**: Added `monkeypatch.setattr(provider, "detect_container_runtime", lambda: None)…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 43 minutes.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.21 |
Topics (from GitHub)
ai-srealertingdatadoggrafanaincident-managementobservabilityremediationroot-cause-analysissite-reliability-engineeringslacksre
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/opensre)Questions
- Does opensre run?
- opensre runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 43 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test opensre?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c0ff91eb0ef1. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test opensre?
- The run that produced this verdict cost $0.21: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does opensre take to install?
- 43 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does opensre need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing opensre?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for opensre?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.