Skip to main content
AI triage reads a new issue and writes a short summary: the likely cause, the impact, and a next step. It runs on its own for new production issues, and you can start it by hand on any issue.

​
When triage runs on its own

Automatic triage runs on a new issue when all of these are true:
  • The issue is new. Triage does not run again when an existing issue gets more events.
  • The level is error or fatal.
  • The environment is production or prod. An issue without an environment is not triaged.
  • The project has not used its budget of 50 automatic triages for the day (UTC).
When automatic triage is on, Squasher assigns every new issue to Squasher Agent, also in other environments. When you assign a person, Squasher Agent stops being the assignee. To triage issues from production, set the environment in your SDK (environment in init) or in the deployment.environment.name resource attribute for OpenTelemetry. You cannot change the environments, the level, or the daily budget in the dashboard.

​
Triage of monitor incidents

When a monitor opens an incident, Squasher starts an investigation of the incident on its own. This applies to every monitor type, including log, metric, and trace query monitors. The investigation reads the monitor, its recent checks, and the project’s telemetry, and it posts its findings in the incident’s chat. Automatic incident triage runs when all of these are true:
  • The incident severity is at or above the selected severity (SEV-2 or higher by default).
  • The incident stays open for the minimum open time (5 minutes by default).
  • The project has not used its daily limit of automatic incident triages (10 a day, UTC, by default).
  • The organization has AI credits left.
Each incident triage uses 10 AI credits, one time for each incident. A retry of the same incident and later questions in the same chat use no more credits. See AI credits. To change these settings or turn automatic incident triage off, open Settings in the sidebar, select the Incidents tab, and edit Automatic triage.

​
What triage reads

Triage reads the issue record: the title, the error type, the level, the environment, the service, the event count, and the first and last seen times. It also reads the latest events of the issue, with their stack traces. It can query the project’s issues, events, logs, traces, metrics, and deployments. Triage can only read. It does not change data, and it does not read your code. Because triage reads error messages and event data, do not put personal data in error messages. See Privacy and data handling.

​
Read the result

The issue page shows the summary in the Squasher triage card, with the suspected cause, its confidence, the next step, and the evidence. The full result has more fields: From the CLI or the API, read the summary on the issue: squasher errors get --project "$SQUASHER_PROJECT_ID" <error_group_id> returns triage_summary, triage_fix, and triage_status. See Error groups. When the disposition is remediate and automatic fixes are on, Squasher can open a pull request. See Auto-fix.

​
Run triage by hand

Open the issue and select Run triage in the Squasher triage card. After a run, the button is Run triage again. A manual run starts a fresh triage, on any issue and in any environment. Manual runs do not count toward the daily budget. The API, the CLI, and MCP do not start triage runs. To investigate an issue from another place, ask the Squasher Agent and paste the link to the issue. You can ask in dashboard chat, in Slack, or with squasher ask. See Ask Squasher Agent.

​
Turn automatic triage off

  1. Open your project and select Settings in the sidebar.
  2. Select the Response Policy tab.
  3. Turn off Automatically triage new signals, then select Save policy.
Only owners and admins can save the policy. AI triage of issues is on every plan and uses no AI credits. See AI credits.

​
Ask Squasher Agent

To ask about one issue, select Investigate in the issue header. It opens a chat with the issue as context and fills in a message about the issue. For questions that go beyond one issue, select Squasher Agent in the sidebar and start a New chat. A filled-in message shows Pre-filled from under the message box. Squasher never sends a filled-in message for you. Edit it, then press Enter or select the send button. Shift+Enter adds a new line. Type in Search chats at the top of the chat list to find a chat by its title. The filter button in the search box selects All chats, My chats (chats that you started), or Automated (chats that incidents and monitors start). Each chat’s ⋯ menu opens it in a new tab, copies its link, or deletes it. A chat that an incident opened shows No findings in this chat yet until Squasher posts its findings. Select Investigate now to start an investigation in that chat. You can attach up to five text files, of at most 40 KB each. Remove secrets from files before you attach them. You can also ask in Slack or from the terminal. Paste the link or the short ID of the issue, so that the agent knows which issue to read. Do the same for an incident or a monitor.
See Squasher Agent and the Chat API.

​
Next steps

Auto-fix

Let Squasher open a pull request for an issue.

Issues

See how Squasher groups errors into issues.