Between October 25 and 27, AI SRE gained two new entry points: one in your terminal, one next to the RUM query box.
Sessions in the terminal: flashduty safari send and watch
flashduty safari send "what to investigate" sends one message and starts a session when --session-id is omitted; the text can also come from --message-file or a pipe, and --file uploads files as session attachments. On success it prints a single receipt line with the session ID and this request's ID. Replies go out on the CLI channel (reply_only); if the server does not accept that channel, the command fails and prints the session and request IDs instead of falling back to another delivery method.
Then read the replies with flashduty safari watch --session-id <id>: one JSON object per line, carrying only the progress notes and conclusions the agent sends itself, not tool calls or plain reasoning. After a disconnect it resumes from the event cursor, and --root-invocation-id follows one request only.
Manage channel-owned integrations from the CLI
flashduty channel integration-* now covers the whole life of a channel-owned (dedicated) integration — list, get, create, update, delete, enable, disable, and rotate key — separately from flashduty integration-* for shared integrations in the integration center. Reads need Channels Read, Channels Manage, or Integrations Read; writes need Channels Manage; and you must be able to see and manage the target channel.
RUM Explorer: one sentence becomes a query that runs
The sparkle at the left of the query box opens AI SRE now — on an account with AI SRE enabled, for a member who may chat in it; ⌘ + Enter in normal query mode does the same, Ctrl + Enter on Windows and Linux. Say in one sentence what you are looking for, and AI SRE writes it into the page: the box's conditions, the event type, the time range, and the chart in analytics, then runs the query itself.
The status bar under the query box reports the turn — filling in the query, querying (counting seconds past 3), N found, query complete, no data, query failed, stopped. Undo change puts the page back the way it was before the write, and works only while the box still holds what AI SRE wrote. Stop ends a running turn; clicking the status bar or pressing Esc only folds the conversation without ending it, leaving the results in view. An account without AI SRE, or one out of AI SRE credits, keeps the basic natural-language query at the same entry: a sentence becomes DQL, previewed before you apply it.
The composer predicts your next message
After a turn settles, with an empty composer, AI SRE offers your likely next message as grey text after the caret. Press Tab or → to accept it and fill the whole sentence in, or Esc to ignore it; once you start typing, it keeps only the remainder that still matches what you typed. Three ignores in a row in one session pause it for 24 hours, and any acceptance restores it — there is no switch in the console. It does not appear in a session opened read-only from someone else's share.
A batch incident reference opens a list
Select several incidents in the incident list and press AI analysis: the message you send carries an Incident list (N) reference capsule. Clicking it now lists every incident behind it — severity, number, title, and handling status — and each row opens that incident. The header reads Status when sent, because those statuses are a snapshot from the moment you sent the message and do not follow later changes.
Get started
Start with flashduty login for the CLI. The RUM entry sits at the left of the query box under RUM → Explorer.
Product docs: CLI, Data query syntax guide, AI SRE sessions.