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's agent now runs your team's own tools, with a human approval before any change.

ai investigationsagent extensibilityhuman approvalincident responseintegrations
◆Current state
Investigations, the agent that posts a root-cause hypothesis when an incident opens, is the center of incident.io; it went GA and then doubled its speed in September. In October the company pushed its agent skills out into coding harnesses, then opened Nexus to customers' own tools and know-how. The 10-28 release restates that extension model and adds an explicit step: any change the agent proposes waits for a human approval before it runs.
◆Where it's heading
incident.io is turning its agent into a two-way integration point that can act, not just diagnose. Skills go out to developers' agents, internal tools and team context come in, and the approval gate is what makes write access acceptable during an incident. Dashboards, ticket sync and alert routing keep incident.io as the record the agent reads from and writes to.
◆Prediction
Expect worked examples for common connected systems such as deploy or feature-flag tools, and Investigations that propose concrete remediation steps for approval. The entries do not say how extensions are built or priced.

◆Recent moves

  1. 1d 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 ↗
  2. 10d 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 ↗
  3. 14d 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 ↗
  4. 22d 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 ↗
  5. 1mo ago

    Custom dashboards get more building blocks

    More building blocks for custom dashboards let teams report on incident data without exporting it. This supports incident.io's push to be the system of record for operations.

    View source ↗
  6. 1mo ago

    Investigations are 2x faster

    ⚡ SPARK

    Six weeks after GA, Investigations cut median time to an accurate message from 6.7 to 3 minutes. The number shows the agent is the product's center now, not an add-on.

    View source ↗