Use “incident.io incident brief” in Recued. It provides a read-only incident command brief for one provider record incident.

How it works 19 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (19 steps)

■ incident_id trim

Trim whitespace from setting incident id

◆ incident recued-core.incidentio.incident.read

Read incident on incidentio

◆ updates_raw recued-core.incidentio.incident_update.search

Search incident update on incidentio

◆ actions_raw recued-core.incidentio.action.search

Search action on incidentio

◆ follow_ups_raw recued-core.incidentio.follow_up.search

Search follow up on incidentio

◆ users_raw recued-core.incidentio.user.search

Search user on incidentio

◆ teams_raw recued-core.incidentio.team.search

Search team on incidentio

■ defaults defaults

Apply defaults

■ update_count count

Count items in updates

■ action_count count

Count items in actions

■ follow_up_count count

Count items in follow ups

✦ summarize core.ai.summarize

AI generates a concise summary

■ update_rows slice

Take a subset of

■ action_rows slice

Take a subset of

■ follow_up_rows slice

Take a subset of

■ update_table to_table

Format results as a data table

■ action_table to_table

Format results as a data table

■ follow_up_table to_table

Format results as a data table

■ card to_summary

Format results as a summary card

▼

Output

summary card

table update_table

table action_table

table follow_up_table

Settings 4 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

focus setting = Summarize the incident.io incident for current status, severity, ownership, recent updates, open actions, follow-ups, escalation risk, and concrete next steps. Do not invent facts outside the incident.io data.

row limit setting = 12

max length setting = 900

incident id setting =