Public beta: AI SRE is now open to all accounts — no application needed. Sign in to the console and start using it; it’s free during the public beta. Features and the UI may continue to evolve.
Key Concepts (30 Seconds)
Four things to know before you start:
Three Entry Points
There’s no single way into AI SRE — start from wherever you already are:
Chat
For actively investigating an issue, digging deeper, or building up knowledge. Go to AI SRE → Chat → New Chat. Suggestion chips below the composer fill in a ready-made prompt; type@ to reference an incident. → See Chat
Automations
For work that shouldn’t need a human watching it — scheduled inspections, weekly insight reports, alert-noise cleanup. Go to AI SRE → Automations and create one from a built-in template (On-call Incident Analysis, Alert Governance, Weekly Insights, and more) or build one from scratch. Each run happens in a hidden session in the background, and the result lands in the run history where you can open the full trail any time. → See AutomationsIM (@ Mentions + Automatic War Room Diagnosis)
Where incidents actually happen. In any Slack, Feishu, DingTalk, or WeCom group with the bot connected, @ AI SRE to start or continue an investigation — it replies in-thread. Open a war room for an incident and AI SRE automatically runs an initial diagnosis and posts the conclusion back. → See IMYour First Investigation (~5 min)
Prerequisite: at least one incident in your account. AI SRE is open to everyone during the public beta — no application needed. If you don’t have an incident on hand right now, skip ahead to “Growing It Into Your SRE” below.
1
Start a new session
Go to AI SRE → Chat and click New Chat in the sidebar.
2
Bring in the incident context
Type
@ in the composer to open incident search, then pick the incident you want to investigate — it’s inserted as a reference chip. You can also click the Investigate an incident chip below the composer: it fills the input with a ready-made prompt, and you can still append an @ incident reference before sending.3
Send your instruction
Send something like:
4
Watch the investigation unfold
The agent streams its plan, tool calls, and intermediate findings, then delivers a conclusion backed by evidence.
@doesn’t find the incident — confirm it actually exists in this account and the name or ID is spelled correctly;- No response for a while, or it’s stuck on “environment initialization” — the cloud Sandbox or Runner is probably still starting up; give it a moment. For persistent unresponsiveness, see the troubleshooting section in Environments;
- The reply only has a conclusion, no plan — just ask “give me an investigation plan first, then evidence for each point” and the agent will follow up;
- You can’t find the AI SRE entry at all — the entry follows role permissions; ask your account admin to confirm your role has AI SRE access.
Growing It Into Your SRE (As Needed)
Your first investigation is just the starting point. From here you can make analysis automatic, and keep sharpening its diagnoses — the latter depends on how much it knows about your systems and how much real data it can reach. All of this builds up over time, not all at once.
Get every new incident analyzed automatically
Once manual investigations feel routine, make them the default: go to AI SRE → Automations, create a rule from the built-in On-call Incident Analysis template, enable the On-call incident trigger card, and pick the channels and severities to watch. From then on, every matching new incident gets an automatic investigation, and AI SRE writes one summary comment back to the incident — conclusion first, full session link at the end — delivered through the incident’s existing notification channels, so responders see the first analysis right in IM. Configuration details: Automations · On-call Incident Trigger. This is independent of war room auto-diagnosis: this path fires for every matching new incident and writes back to the incident itself; war room diagnosis runs when you open a war room for an incident and posts into the war room group (see IM).Build a team knowledge base
If the agent has to guess “what service is this,” “who owns it,” and “how was this handled last time” on every investigation, it won’t get much sharper. Type/init in a session and the agent interviews you to map out your services, runbooks, on-call routing, and more — confirming each write before it saves anything, and loading it automatically in future sessions. See the full interview flow in Setup (/init) and the knowledge base structure and best practices in Knowledge.
Connect real data sources
By default the agent only sees Flashduty’s own data. To let it query your actual systems — logs, metrics, code repositories, internal databases — connect an MCP server or deploy a BYOC Runner. Publicly reachable services (observability platforms, GitHub, and similar) install and authorize in one click from the MCP directory — see MCP; VPCs, internal databases, or local commands need a Runner deployed on a machine that can reach them — about three minutes, below.Deploy a BYOC Runner (~3 minutes)
1
Create a self-hosted Environment
Go to AI SRE → Environments and click Create on the Self-hosted tab. The name is optional (the first heartbeat fills it in with the machine’s hostname); pick Shared (account-level) or team scope.
2
Run the install command on the target machine
After creation, the setup guide opens with install commands that already include your Token — a Linux one-liner (needs sudo; registers a systemd service), plus Docker and macOS variants. Copy it onto a machine that can reach your target resources and run it.
3
Wait for the status to flip to Online
Back in the list, the status goes from Pending to Online once connected. Heartbeats are evaluated on a ~90-second cycle, so give it a moment after installing; if it stays Pending, the machine almost certainly can’t reach the connect URL shown in the guide (outbound traffic blocked by a firewall).
4
Use it in a session
When starting a new chat, the environment picker at the bottom of the composer defaults to Auto — it prefers an online Runner when one is available; you can also select this self-hosted Environment explicitly. Note that the environment locks once the session starts and cannot be changed afterwards.
What’s Next
Product Overview
What AI SRE is, its full capability set, and console navigation.
Chat
Creating and managing sessions, streaming, forking, and context compaction.
IM Platform
@ the agent in IM to troubleshoot, and learn about automatic war room diagnostics.
Environments
Cloud Sandbox vs. BYOC Runner, deployment, and permission configuration.