The incident list command lists incidents: everything that needs (or needed) a reaction, such as downtime, failing synthetic tests, firing alarms, production errors, unhealthy stacks, and expiring certificates. It shows each incident's ID, status, severity, title, project, stage, open time, and contributing signals. The default ACTIVE view includes both open and acknowledged incidents.
Usage
List active incidents (returns up to 25 incidents when no limit is provided):
List active incidents for a specific project and stage:
Flags reference
stacktape incident listCLI options-h, --helpstringShow Help
If provided, the command will not execute and will instead print help information.
--status"ACTIVE" | "OPEN" | "ACKNOWLEDGED" | "RESOLVED" | "ALL"Incident Status Filter
Filter incidents by status. ACTIVE (the default) means OPEN + ACKNOWLEDGED.
--limitnumberLimit
Maximum number of items to return.
--log-level"info" | "debug" | "error"Log Level
The level of logs to print to the console.
info: Basic information about the operation.error: Only errors.debug: Detailed information for debugging.
--projectstringProject Name
The name of the Stacktape project for this operation.
Commands that target a stack take it from projectName in the project's config when the flag is absent.
--quietbooleanQuiet
Hide progress, banners, success messages and hints. Command output, warnings and errors are still printed.
-s, --stagestringStage
The stage for the operation (e.g., production, staging, dev-john). You can set a default stage using the defaults set command. Stage names use lowercase letters, numbers and dashes, with at least 2 characters. The project name, a dash and the stage form the CloudFormation stack name, which can have at most 128 characters. Stacktape shortens an AWS resource name that would be too long and adds a hash.
Examples
List resolved incidents, up to 50:
Get JSON output for scripting or AI coding assistants. In agent mode, the command prints the returned incidents as a pretty-printed JSON array instead of a table.
Output
In interactive mode, the command prints a table with the following columns:
| Column | Description |
|---|---|
| ID | Unique incident identifier (used with the other incident commands) |
| Status | OPEN, ACKNOWLEDGED, or RESOLVED |
| Severity | INFO, WARNING, ERROR, or CRITICAL |
| Title | Truncated incident title (up to 50 characters) |
| Project | Project name |
| Stage | Stage name |
| Opened | When the incident opened |
| Signals | Each contributing signal, prefixed with ✗ while it is active and ✓ once it recovered |
Accepted --status values are ACTIVE (the default: open and acknowledged), OPEN, ACKNOWLEDGED, RESOLVED, and ALL.
Related commands
incident show— print an incident's self-contained handoff bundle for a developer or coding agentincident ack— record that someone is working on the incidentincident watch— wait until the incident stays resolved after a fixincident resolve— resolve an incident manually after verifying a fix
See Incidents for what opens an incident, its lifecycle, and how signals recover.