AI in Firefight
Firefight’s AI features share one goal. Turn the raw record of an incident, its timeline and its channel conversation, into answers people need, without anyone re-reading five hundred messages. They all work from the incident’s own data, and they all run where you already are, in Slack and in the dashboard.
The features
Section titled “The features”| Feature | Where | What it does |
|---|---|---|
| Catch-up | /ff catchup in an incident channel | Posts a concise summary of what has been investigated, decided, and blocked, for responders joining late |
| Live summary | Behind the scenes | A continuously maintained summary of the channel narrative that keeps every other AI feature current without reprocessing the whole history |
| Incident responder | Mention @Firefight in an incident channel | Answers questions about the incident from its record, or summarizes a single thread when mentioned inside one |
| Timeline notes | Automatic, once an incident ends | Reads the channel and adds the milestones of the investigation to the incident’s timeline, each linked to the message it came from |
| Postmortem drafting | /ff postmortem or the incident’s page in the dashboard | Generates a structured postmortem draft from the timeline and the channel narrative |
| Section rewrite | The postmortem editor | Rewrites a selected passage of the postmortem according to your instruction |
Catch-up and the live summary
Section titled “Catch-up and the live summary”The live summary is the backbone. It tracks the conversational narrative of the incident, the theories tested, the decisions made, the open questions, and updates incrementally as new messages arrive. /ff catchup and the responder build on it, so answers stay fast even in long incidents. See Summaries & catch-up.
The incident responder
Section titled “The incident responder”Mentioning @Firefight in an incident channel gets you an answer grounded in that incident’s record. Ask what the current status is, who is leading, or what has been tried. Mention it inside a thread and it summarizes just that thread. See The incident responder.
Timeline notes
Section titled “Timeline notes”When an incident is resolved or cancelled, Firefight reads its channel once and writes the genuine milestones onto the timeline: the theories, the findings, the root cause, the mitigation. Each note names who said it, sits at the time they said it, and links to the message. Nothing is posted to the channel, and a note that reads a conversation wrong can be dismissed. See Timeline notes.
Postmortems
Section titled “Postmortems”Once an incident is closed, Firefight can draft the postmortem for you. It is written from the timeline, including the notes above, so the reasoning chain arrives with its authors and times rather than being worked out a second time.
The draft is structured into sections covering the summary, impact, resolution, contributing factors, what went well, and action items, and it lands as an editable document, not a final verdict. Run /ff postmortem in the closed incident’s channel or generate from the incident’s page in the dashboard. Inside the editor, select any passage and tell the AI how to rewrite it, and it revises just that selection in place. You can also skip generation entirely and start from a blank document.
What the AI sees
Section titled “What the AI sees”Every feature works from data Firefight already holds about the incident, and channel messages are scrubbed for known secret formats before they are ever stored. For the full picture of what is stored, what is redacted, and what is sent to models, see AI data handling.