AI-powered game testing that never stops clanking
active 2026-02-23 → 2026-06-12 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 110 days from 2026-02-23 to 2026-06-12. Pushes: 57 total, peak 6 in a day. Pull requests: 6 total, peak 1 in a day. Issues: 25 total, peak 17 in a day. Comments: 2 total, peak 2 in a day. Stars: 0 total, peak 0 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| RandVid | 31 | 3 | 2 | 2 |
| DanilaOdesser | 30 | 29 | 1 | 0 |
| aircode610 | 28 | 25 | 1 | 0 |
| sabatsirekidze | 2 | 0 | 2 | 0 |
Recent activity
Latest issues, pull requests and releases
- Pull request#92RandVid2026-05-11 19:39
- Issue#72aircode6102026-04-27 00:52S3.C1: Add all new Pydantic models and SSE events to `backend/models.py` — `BugReportRequest`, `BugContinueRequest`, `ExportRequest`, `TriageResult`, `MechanicsAnalysis`, `ReproductionPlan`, `ResearchFindings`, `BugReport`, `BugReportResponse`, `BugStageChangeEvent`, `BugCheckpointEvent`, `ResearchProgressEvent`, `BugReportResultEvent`, `ExportReadyEvent`, `IntegrationStatus`, `IntegrationSettingsResponse`
- Pull request#84sabatsirekidze2026-04-27 00:52
- Issue#57RandVid2026-04-26 23:45Dev A: Implement Bug Reproduction Pipeline — Stages 1–3 + Evaluators + Frontend Drawer
- Issue#64RandVid2026-04-26 23:45S3.B1: Implement research stage — query all configured external sources, synthesize evidence into `ResearchFindings` (`backend/agent/stages/bug_research.py`, budget 20 calls)
- Issue#67RandVid2026-04-26 23:45S3.B4: Add P2 evaluator section to `bug_evaluators.py` — `bug_pipeline_health`, `research_coverage`, `report_completeness`, `report_actionability` (LLM judge), `evidence_quality` (LLM judge), `tool_efficiency`, `graceful_degradation` (`backend/evals/bug_evaluators.py`)
- Issue#66RandVid2026-04-26 23:45S3.B3: Wire the full StateGraph — 8 nodes (triage → mechanics → checkpoint_mechanics → reproduction → research → checkpoint_research → report → submit), two conditional edges, `build_bug_reproduction_graph()` entry point, `run_bug_agent()` and `continue_bug_agent()` streaming functions (`backend/agent/bug_agent.py`)
- Issue#65RandVid2026-04-26 23:45S3.B2: Implement report generation stage — assemble all stage outputs into a final `BugReport`, optionally link Jira issue (`backend/agent/stages/bug_report.py`, budget 5 calls)
- Pull request#83DanilaOdesser2026-04-26 21:56
- Issue#77RandVid2026-04-25 15:16S3.C6: Add TypeScript interfaces and API client functions for all new models — extend `frontend/src/services/types.ts` and `frontend/src/services/api.ts` with `startBugReport()`, `continueBugReport()`, `exportBugReport()`, `getIntegrations()`, `updateIntegration()`
- Issue#75RandVid2026-04-25 15:16S3.C4: Implement `backend/export.py` — `export_markdown(report)` returning `(content, filename)`, `export_pdf(report)` returning `(bytes, filename)` via `fpdf2`; add `fpdf2` to `requirements.txt`
- Issue#76RandVid2026-04-25 15:16S3.C5: Build `SettingsPanel` frontend component — integration cards for Jira, Notion, Confluence, Grafana, Kibana, Postman; status indicators (connected/unhealthy/not-configured); credential fields; Test Connection button; Save All action (`frontend/src/components/SettingsPanel.tsx`)
- Issue#70RandVid2026-04-25 15:16Dev C: Models, API Endpoints, Sessions, Export, Settings UI — Merge First
- Issue#73RandVid2026-04-25 15:16S3.C2: Add five new API endpoints to `backend/main.py` — `POST /bug-report`, `POST /bug-report/{id}/continue`, `GET /bug-report/{id}/status`, `POST /bug-report/{id}/export`, `GET /settings/integrations`, `POST /settings/integrations` — all streaming endpoints follow the existing `StreamingResponse` SSE pattern; Sprint 2 routes must remain untouched
- Issue#72RandVid2026-04-25 15:16S3.C1: Add all new Pydantic models and SSE events to `backend/models.py` — `BugReportRequest`, `BugContinueRequest`, `ExportRequest`, `TriageResult`, `MechanicsAnalysis`, `ReproductionPlan`, `ResearchFindings`, `BugReport`, `BugReportResponse`, `BugStageChangeEvent`, `BugCheckpointEvent`, `ResearchProgressEvent`, `BugReportResultEvent`, `ExportReadyEvent`, `IntegrationStatus`, `IntegrationSettingsResponse`
- Issue#74RandVid2026-04-25 15:16S3.C3: Extend `backend/agent/sessions.py` — add `SessionType` enum, extend `Session` dataclass with `session_type`, `bug_description`, `bug_report` fields; update `create_session()` signature
- Issue#79RandVid2026-04-25 15:15S3.D2: Wire all integrations into `backend/agent/tools.py` — Notion/Confluence community MCP configs, Grafana/Kibana/Postman custom server configs (all conditional on env vars), `BUG_RESEARCH_TOOLS`, `BUG_REPORT_TOOLS`, `get_available_integrations()`; implement `make_sniffer_tools()` in `backend/agent/sniffer.py` and `check_all_integrations()` in `backend/agent/tool_health.py`; update `.env.example` with all new variables
- Issue#81RandVid2026-04-25 15:15S3.D4: Build `BugReportView` frontend component — header with severity/category/confidence, reproduction steps, expected vs actual, root cause block, Evidence tabs (delegates to `ResearchPanel`), affected components, recommendations, Export Markdown/PDF and Push to Jira actions (`frontend/src/components/BugReportView.tsx`)
- Issue#80RandVid2026-04-25 15:15S3.D3: Build `BugInputPanel` frontend component — textarea for description, environment/severity/repo/jira/attachments fields, integration availability dots from `GET /settings/integrations`, Analyze Bug button disabled until description filled, Jira ticket format validation (`frontend/src/components/BugInputPanel.tsx`)
- Issue#82RandVid2026-04-25 15:15S3.D5: Update `frontend/src/App.tsx` — add Bug Reproduction tab alongside Impact Analysis, Settings gear icon overlay, `useBugReproState` hook wiring all SSE event handlers (`bug_stage_change`, `agent_step`, `research_progress`, `bug_checkpoint`, `bug_result`) to `BugTraceDrawer`, `BugCheckpointDialog`, and `BugReportView`
- Issue#78RandVid2026-04-25 15:15S3.D1: Implement three custom MCP servers — Grafana (`grafana_query_logs`, `grafana_query_metrics`, `grafana_get_annotations`), Kibana (`kibana_search`, `kibana_get_log_entry`), Postman (`postman_list_collections`, `postman_get_collection`, `postman_get_request`, `postman_run_request`) — all follow the `mcp.server.Server` stdio template (`backend/mcp_servers/`)
- Issue#72RandVid2026-04-25 14:36S3.C1: Add all new Pydantic models and SSE events to `backend/models.py` — `BugReportRequest`, `BugContinueRequest`, `ExportRequest`, `TriageResult`, `MechanicsAnalysis`, `ReproductionPlan`, `ResearchFindings`, `BugReport`, `BugReportResponse`, `BugStageChangeEvent`, `BugCheckpointEvent`, `ResearchProgressEvent`, `BugReportResultEvent`, `ExportReadyEvent`, `IntegrationStatus`, `IntegrationSettingsResponse`
- Issue#79RandVid2026-04-25 14:35S3.D2: Wire all integrations into `backend/agent/tools.py` — Notion/Confluence community MCP configs, Grafana/Kibana/Postman custom server configs (all conditional on env vars), `BUG_RESEARCH_TOOLS`, `BUG_REPORT_TOOLS`, `get_available_integrations()`; implement `make_sniffer_tools()` in `backend/agent/sniffer.py` and `check_all_integrations()` in `backend/agent/tool_health.py`; update `.env.example` with all new variables
- Issue#70RandVid2026-04-25 14:32Dev C: Models, API Endpoints, Sessions, Export, Settings UI — Merge First
- Issue#65RandVid2026-04-25 14:30S3.B2: Implement report generation stage — assemble all stage outputs into a final `BugReport`, optionally link Jira issue (`backend/agent/stages/bug_report.py`, budget 5 calls)
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.