> ## Documentation Index
> Fetch the complete documentation index at: https://test-8ad8522e-feat-doc-review-auto-fix.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# AI SRE Product Overview

> Flashduty's autonomous SRE agent platform — use natural language to let AI independently investigate incidents, diagnose root causes, and accumulate reusable operational knowledge, deeply integrated with Flashduty's incident response system and IM collaboration

<Info>
  **Public beta**: AI SRE is in public beta, rolling out gradually to accounts on On-call Pro or higher, at no additional charge during the beta. To get access, submit the [AI SRE beta application form](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH). Features and the UI may continue to change.
</Info>

## What Is AI SRE

***

AI SRE is Flashduty's autonomous SRE agent platform. You give the AI instructions through conversation, and it independently investigates incidents, diagnoses root causes, calls tools to run diagnostics, and captures the operational knowledge gained from each investigation for future reuse.

It is not a simple Q\&A chatbot — it is a **hands-on troubleshooting worker**: it plans its own steps, reads and writes files, queries monitoring and logs, executes commands, calls external tools (MCP), and delegates subtasks when needed, ultimately delivering conclusions backed by a full investigation trail.

AI SRE is deeply integrated with Flashduty's incident response system. When Flashduty generates an incident or opens a war room, you can directly trigger an AI SRE session so the agent enters the investigation with full incident context — you can collaborate either in the console or by **@ mentioning it directly in your IM group (Slack / Feishu / DingTalk / WeCom)**.

<CardGroup cols={2}>
  <Card title="Conversation as Troubleshooting" icon="comments">
    Describe the problem in natural language. The agent plans autonomously, calls tools, and delivers an investigation trail and conclusion — no manual scripting required.
  </Card>

  <Card title="Integrated with Incident Response" icon="bug">
    Launch a session with one click from an incident or war room. The agent enters the investigation with full incident context, and the knowledge it accumulates feeds back into the next response.
  </Card>
</CardGroup>

## Typical Use Cases

***

AI SRE is more than a chat box in the console — it covers multiple collaboration entry points across the full lifecycle from incident trigger to retrospective:

<CardGroup cols={2}>
  <Card title="Conversational Troubleshooting" icon="comments">
    Ask questions proactively in the console's Chat workspace: why a service is behaving abnormally, the root cause of an alert, or the blast radius of a change. The agent streams its planning, tool calls, and intermediate findings before delivering a final conclusion.
  </Card>

  <Card title="On-Demand in IM" icon="comment-dots">
    No context switching needed — in Slack, Feishu, DingTalk, or WeCom group chats or direct messages, **@ AI SRE** to start or continue an investigation. It replies **in-thread** so all team members stay in the loop. See [IM Integration](/en/ai-sre/im).
  </Card>

  <Card title="Automatic War Room Diagnosis" icon="people-group">
    When a war room is opened for an incident, AI SRE **automatically runs an initial diagnostic** and posts the conclusion back to the war room — by the time your team starts investigating, a first-pass analysis is already in the channel.
  </Card>

  <Card title="Usage Insights" icon="gauge-high">
    Use [`/insight`](/en/ai-sre/insight) to review the past 30 days of sessions, quantify where you're spending time, identify missing runbooks and repeatedly copy-pasted context, and receive actionable improvement suggestions.
  </Card>
</CardGroup>

## Public Beta & Requirements

***

AI SRE is currently in public beta. To use it, you need:

<AccordionGroup>
  <Accordion title="Subscription Requirement" icon="key">
    AI SRE is available to accounts on **On-call Pro or higher**. Consistent with other professional capabilities such as Status Page and alert ingestion, it is unavailable on lower tiers, and the UI will prompt you to upgrade.
  </Accordion>

  <Accordion title="Gradual Rollout" icon="users">
    Access during the public beta rolls out gradually. If you don't yet see the AI SRE entry in your account, submit the [AI SRE beta application form](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH) and we'll enable it for you as soon as possible.
  </Accordion>

  <Accordion title="Public Beta Billing" icon="gift">
    AI SRE is not billed separately during the public beta. Flashduty will share billing information ahead of general availability.
  </Accordion>

  <Accordion title="Human Authorization" icon="user-check">
    Production changes, restarts, rollbacks, and external notifications all require your confirmation before they execute.
  </Accordion>
</AccordionGroup>

## Core Capabilities

***

AI SRE is built around "conversational troubleshooting + knowledge accumulation + autonomous execution," with every capability configurable and manageable from the console.

<CardGroup cols={2}>
  <Card title="Conversational Troubleshooting" icon="comments" href="/en/ai-sre/sessions">
    Collaborate with the agent session by session. A session handles your messages one at a time, with streaming output, cancellation at any time, automatic context compaction for long conversations, and one-click launch from an incident.
  </Card>

  <Card title="IM Platform" icon="comment-dots" href="/en/ai-sre/im">
    @ the agent in Slack / Feishu / DingTalk / WeCom to start or continue an investigation, and receive automatic initial diagnostics in incident war rooms.
  </Card>

  <Card title="Skills" icon="wrench" href="/en/ai-sre/skills">
    Skill packages that the agent can invoke, encapsulating reusable troubleshooting workflows. Scope can be set to account or team; once enabled, they are loaded on demand during sessions.
  </Card>

  <Card title="Manage Knowledge" icon="book" href="/en/ai-sre/knowledge">
    Knowledge packages indexed via DUTY.md as the entry point and @-reference links, carrying service catalogs, runbooks, on-call routing, and other long-lived context — loaded in layers by account and team.
  </Card>

  <Card title="MCP (External Tools)" icon="plug" href="/en/ai-sre/mcp">
    Connect external tools and data sources via the Model Context Protocol. MCP servers are not pre-connected; the agent establishes, uses, and closes connections on demand when making a call.
  </Card>

  <Card title="Agent" icon="satellite-dish" href="/en/ai-sre/agents">
    Delegate tasks to external remote agents via the standard A2A protocol. AI SRE also exposes its own Agent Card so external clients can invoke it in reverse.
  </Card>

  <Card title="BYOC" icon="server" href="/en/ai-sre/environments">
    The execution layer for the agent: uses Flashduty-managed cloud sandboxes by default, or deploy a persistent Runner on your own machine to let investigations reach your private network.
  </Card>

  <Card title="Usage Insights" icon="gauge-high" href="/en/ai-sre/insight">
    Use /insight to review the past 30 days of AI SRE sessions and receive a quantified overview, narrative summary, and actionable operational improvement suggestions (read-only; nothing is applied automatically).
  </Card>

  <Card title="Automations" icon="robot" href="/en/ai-sre/automations">
    Have AI SRE run a hidden session on a cron schedule or via an API trigger to automatically produce periodic inspections, insights, or post-mortems.
  </Card>

  <Card title="Apps" icon="grid-2" href="/en/ai-sre/apps">
    Authorize external applications (currently GitHub) so AI SRE can work directly inside your code repositories: understand code, investigate PRs and commits, and open a PR or file an issue on request.
  </Card>
</CardGroup>

## Console Navigation

***

After entering AI SRE, the top navigation is organized into the following four areas (menu names match the console):

| Area         | Menu Name        | Purpose                                                                                                                                                                                                                                                                        |
| ------------ | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Chat         | **Chat**         | The primary workspace for collaborating with the agent on troubleshooting. The left panel shows your session list (with search, filtering, pinning, and archiving); the right panel shows the conversation and investigation trail.                                            |
| Plugins      | **Plugins**      | Manage extensible resources the agent can invoke, organized into four sub-tabs: **Apps** (authorized external applications, e.g. GitHub), **Skill** (skill packages), **Agents** (A2A remote agents), **MCP** (external tools).                                                |
| Knowledges   | **Knowledges**   | Manage Knowledge Packs. At most one per target: account-level (visible to all agents) plus per-team (loaded only in that team's sessions).                                                                                                                                     |
| Environments | **Environments** | Manage self-hosted Runners. The persistent process handles the agent's tool, Skill, and MCP calls; if none is available, sessions fall back to the cloud sandbox.                                                                                                              |
| Artifacts    | **Artifacts**    | View and manage the files and reports the agent publishes to the artifact gallery via the present\_files tool: search, and filter by personal / team scope; each artifact can be copy-linked, downloaded, renamed, or deleted (renaming and deletion require edit permission). |

<Note>
  Visibility of each area is determined by your access permissions in the account: menus or sub-tabs you do not have permission for will not appear in the navigation.
</Note>

## Quick Start

***

For the full walkthrough from activating access to finishing your first investigation, see [Quickstart](/en/ai-sre/quickstart).

## Next Steps

***

<CardGroup cols={2}>
  <Card title="Console" icon="comments" href="/en/ai-sre/sessions">
    Learn about sessions, streaming output, cancellation and context compaction, and how to launch an investigation from an incident.
  </Card>

  <Card title="IM Platform" icon="comment-dots" href="/en/ai-sre/im">
    @ the agent in Slack / Feishu / DingTalk / WeCom, and learn about automatic war room diagnostics.
  </Card>

  <Card title="Usage Insights" icon="gauge-high" href="/en/ai-sre/insight">
    Use /insight to review the past 30 days of sessions and surface operational friction such as repeated context and missing runbooks.
  </Card>
</CardGroup>