LoginSign Up
← Back to all sparks
I

incident.io

INFRA · APIS
Velocity7.5

Incident management, on-call, and status page platform for engineering teams

incident.io ↗

incident.io now drafts status page updates with AI while the team edits together.

ai investigationsincident communicationsstatus pagesagent extensibilityadmin controls
◆Current state
incident.io's center is Investigations, the agent that posts a root-cause hypothesis when an incident opens. October pushed its skills into coding harnesses and opened Nexus to customers' own tools. November turns to incident communications: the 11-03 release set org-wide guidance for how summaries and updates are written, and the 11-10 release lets a team draft status page updates together, with an AI first draft.
◆Where it's heading
After a month of agent extensibility, the AI is moving into the outward-facing part of an incident: what customers read. The guidance control and the shared drafting fit together, the first setting the tone and the second putting AI drafts in front of the people who approve them.
◆Prediction
Expect more of the incident write-up flow, such as post-mortems or customer emails, to start from AI drafts governed by the same org-wide guidance.

◆Recent moves

  1. 3d ago

    Write status page updates together, with AI drafts

    Status page updates can now be drafted collaboratively, with AI proposing the first version. It builds on last week's writing guidance and keeps a human edit step before anything reaches customers.

    View source ↗
  2. 10d ago

    Org-wide guidance for how summaries and updates are written

    Organizations can now set how incident summaries and updates are written, a governance layer on top of the AI that drafts them. It follows the approval gate added in October: both give teams control over agent output rather than new agent capability.

    View source ↗
  3. 16d ago

    Plug your skills and tools into the agent

    A follow-up to the 10-19 Extensions launch: teams connect their own systems, teach the agent how they work, and must approve any change before it runs. The approval step is the new piece, and it moves the agent from read-only diagnosis toward gated remediation.

    View source ↗
  4. 25d ago

    Extensions connect internal tools and know-how to the Nexus agent

    ⚡ SPARK

    A week after shipping its skills out to coding agents, incident.io opens Nexus up to the customer's own tools. Together the two releases make the agent the integration layer, with the incident UI as one surface among several.

    View source ↗
  5. 1mo ago

    The incident.io plugin: our skills, in your agent

    ⚡ SPARK

    The Investigations agent was the core of the product; this plugin takes the same skills out of incident.io's UI and into the coding agents engineers already run. It is the distribution step after September's speed gains.

    View source ↗
  6. 1mo ago

    Dark mode

    Dark mode leads a bundle that also includes paused notifications, shift-conflict policies and new SDK support. It is the kind of polish an on-call tool used at 3am should have.

    View source ↗