> ## Documentation Index
> Fetch the complete documentation index at: https://docs.augmentcode.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Incident Investigator

> Use the Incident Investigator Expert to watch alert channels, post root-cause analyses in-thread, and accompany incidents through to resolution.

## Incident Investigator

Incident Investigator is a single incident-response Expert with two activation modes:

* **Alert-thread mode**: The Expert watches one or more long-lived alert channels that receive alerts from your incident-management platform as well as free-form incident reports. Each fresh top-level message launches a per-incident session that triages, investigates logs and metrics, posts a root-cause analysis in-thread, and subscribes to follow-ups.
* **Stationed-channel mode**: A human launches the Expert with a link to an ad-hoc incident channel — or a trigger auto-launches it when a channel matching your incident-channel naming pattern is created. One session watches the channel, handles incident-like messages and follow-ups, and stays alive until released.

In both modes, code fixes are gated on explicit human approval before the Expert launches a [PR Author](/cosmos/experts-pr-author) worker.

* **Best for**: On-call teams who want triage, log/metric investigation, and root-cause analysis started the moment an alert fires — with findings posted where responders already are.
* **How to use**: Connect your communication integration and point the Expert's triggers at your alert channels. For stationed-channel mode, start a session with the Expert and paste the incident channel link. The Expert needs skills for querying your logs and metrics backends — set these up when installing it.

## See Also

* [PR Author](/cosmos/experts-pr-author) — the worker that opens fix changes once a human approves.
* [Understanding Automation](/cosmos/automations) — triggers, subscriptions, and the events log behind this Expert.