codeready-toolchain/tarsy-bot

Intelligent Site Reliability Engineering agent for automatic alert processing

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 37 minutes ago
Added to GitGenius on June 28th, 2026
Created on June 23rd, 2025
Open Issues & Pull Requests: 0 (+0)
Number of forks: 8
Total Stargazers: 7 (+0)
Total Subscribers: 4 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 46.4 days
Mean response time: 63.6 days
90th percentile: 182.1 days
Tracked items: 11

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • good first issue (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Tarsy-bot is a Site Reliability Engineering agent that automatically processes alerts through sequential agent chains and retrieves runbooks using the Model Context Protocol.

The tool addresses the challenge of manual alert triage and incident response by automating the analysis of incoming alerts. It uses agent chains to sequentially process alerts, retrieves relevant runbooks, and leverages MCP servers to gather system information for multi-stage incident analysis. This approach reduces the manual work required from SRE teams when responding to alerts.

The project is now deprecated, with all further development having moved to a new Go and Python hybrid rewrite. Developers should not adopt this Python-based implementation for new deployments and should instead use the successor repository, which offers better performance, type safety, and scalability through a Go orchestrator paired with a stateless Python LLM service.

The project is no longer actively developed, as indicated by the deprecation notice in the README directing users to the new implementation.