Back to browse
GitHub Repository
2 starsPython

Autopsy CLI – Open-source AI incident diagnosis in 30s

by zeelpatel27·Mar 11, 2026·1 point·0 comments

AI Analysis

●●SolidSolve My ProblemShip It

SQLite history and Markdown postmortems help, but incident diagnosis via LLM is a crowded category.

Strengths
  • Local SQLite DB preserves diagnosis history across terminal sessions for audit trails.
  • --postmortem flag generates full incident reports with timelines and action items.
  • Zero code changes needed—works with existing CloudWatch and GitHub setups.
Weaknesses
  • Only supports OpenAI and Anthropic—no local model or self-hosted LLM options.
  • Root cause analysis via LLM is already served by Datadog, PagerDuty, and others.
Target Audience

SREs and DevOps engineers

Similar To

Datadog AI · PagerDuty · Incident.io

Post Description

Hi HN,

I've been building Autopsy, an open-source CLI tool to solve a problem I hate: manually digging through CloudWatch logs during a 3 AM page.

It pulls your CloudWatch logs and GitHub deploys, passes them to an LLM, and returns a structured root cause analysis in your terminal in about 30 seconds.

The early version worked, but the diagnosis vanished the moment you closed your terminal. I just shipped v0.2.2 to make it actually fit into an SRE/DevOps workflow:

Local History: Every run now saves automatically to a local SQLite DB. You can search, browse, and export past incidents (autopsy history list).

Instant Post-Mortems: Passing --postmortem generates a full incident report in Markdown, including a timeline, evidence, and checkbox action items.

Slack Integration: Passing --slack pushes the diagnosis directly to your incident channel via webhook.

You can chain them: autopsy diagnose --postmortem --slack

A big priority here is privacy. It’s built with Python, runs locally, and your logs never leave your machine (aside from the direct payload you choose to send to the LLM).

GitHub: https://github.com/zeelapatel/autopsy PyPI: pip install autopsy-cli

I'd love for you to try it out. I'm especially looking for feedback on the LLM's diagnosis accuracy across different types of stack traces and log formats. Happy to answer any questions!

Similar Projects