Issues
Issues are recurring problems, errors, or system degradation that Firetiger agents have identified. Each issue is scoped to the agent that discovered it, giving you a clear view of what each agent is observing across your systems.
You can see your issues at /issues.
How issues get created
Issues are created by your Firetiger Agents. When an agent runs and discovers a problem according to its Plan, it will escalate that problem to be classified as follows:
- If the problem matches an existing Issue for that agent, the existing issue’s observation count is incremented and timestamps are updated — no duplicate is created.
- If the problem is new, a new Issue is created with an auto-assigned call sign (e.g. FT-1, FT-2) and an Issue Expert Agent that is responsible for triaging the Issue, and managing its lifecycle moving forward.
- If the problem matches a previously dismissed Issue, the recurrence is suppressed.
This means Issues are automatically deduplicated at the per-agent level. The same underlying problem reported across multiple agent runs gets consolidated into a single Issue to be triaged and fixed.
Workflow states
Each issue progresses through a defined lifecycle:
| State | Meaning |
|---|---|
| Investigating | Root cause analysis is in progress. This is the initial state. |
| Actionable | The issue has been triaged and warrants attention. Root cause may or may not be identified yet. |
| Verifying Fix | A fix has been applied and Firetiger is confirming whether it worked. |
| Closed | Terminal state. See the closure reason for why. |
Issues can move backward through the workflow when hypotheses are invalidated. For example, from Verifying Fix back to Investigating if a fix didn’t work, or from Actionable back to Investigating if the initial root cause turns out to be incorrect.
Issue Closure
Issues can be closed by you, the user, or the Issue Expert Agent.
When an issue is closed, you can record why:
| Reason | Meaning |
|---|---|
| Resolved | The issue was fixed and verified with evidence. |
| Accepted Risk | A real issue, but intentionally dismissed or won’t fix. |
| False Positive | Not a real issue. |
| Duplicate | Closed in favor of another canonical issue. |
| Not Useful | The signal may be real, but the issue isn’t actionable or relevant enough to track. |
Closed issues aren’t deleted: they remain queryable and visible. If a closed issue recurs, the Agent Issue Manager may choose to reopen it if there is material evidence to justify doing so.
Observation tracking
Each issue tracks how often it’s been observed:
- First/last observation time — when the problem was first and most recently seen.
- Observation count — how many times agents have reported this problem.
- Source sessions — which agent sessions reported it.
This gives you a clear picture of whether an issue is a one-off or a persistent pattern, without creating duplicate issue records.
The Issues List
The issues list at /issues shows all your issues, filterable by workflow state. By default it shows actionable issues — the ones that have been triaged and are ready for attention.
Issue Details
Clicking into an issue shows:
- Title — a concise description of the root cause.
- Description — impact-first summary of the problem
- Details — investigation evidence including code references, log lines, metric queries, and trace IDs.
- Tags — categorization labels.
- Links — external references like GitHub PRs, Linear tickets, or Slack threads.
Additionally, you can chat with the Issue’s Expert Agent via the chat panel. The Issue Expert owns that specific issue and can gather data, verify fixes, or check whether error patterns are still occurring.
Notifications
By default, issues don’t notify anyone. To set up notifications, go to /issues/notifications.
The notifications page has a chat interface where you describe your notification policy conversationally. You tell it which connections should receive notifications — for example, a Slack channel — and the planner agent configures the routing rules.
Notifications get sent when an Issue transitions to Actionable (a new problem needs attention) or Closed (a problem was resolved or dismissed).