Skip to main content
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.

​
Overview

An artifact is a file AI SRE produces in a session with the present_files tool and then publishes to the artifact gallery with the publish_artifact tool. The most typical case is a self-contained HTML report or page — for example, the operational insight report generated by typing /insight in a session — but publishable types go well beyond that: Files outside the publishable range don’t show a “Publish to artifact gallery” button in the session. A published artifact initially inherits its source session’s scope: artifacts from a personal session belong to their creator (“Personal”); artifacts from a session bound to a team belong to that team and can be shared with other account members. Users with edit permission can change the scope later. Entry point: AI SRE → Artifacts in the left navigation, route /ai-sre/artifacts.
The artifact gallery has no entry point for manually uploading or creating files — every artifact is produced and published by the agent using tools during a session. The console only lets you browse, search, and manage artifacts that already exist.

​
List Page

​
Search and scope filter

  • Search box: fuzzy-search published artifacts by title; the query fires automatically 300ms after you stop typing.
  • Scope: a three-way All / Personal / Team switch (the same two-level scope shared with the other resources under AI SRE). Selecting “Team” expands a searchable, multi-select team picker; selecting no team means “all teams visible to me.”

​
Artifact cards

Each card shows:
  • A kind icon in the preview area: determined by file extension and content type — images, PDF, HTML, Markdown, tables (CSV / TSV), JSON, archives, and source code each get a dedicated icon, falling back to a generic file icon when the type can’t be recognized;
  • The title (single line, truncated beyond that; hover to see the full title);
  • A Created … relative timestamp shown first — just now / N minutes ago / N hours ago / N days ago, or a specific date beyond 30 days. An Edited … line appears alongside only when the edit time differs from the creation time (the artifact was updated after creation); legacy rows without created_at show only “Edited …”;
  • A scope badge in the bottom right: team artifacts show the team name (highlighted green); personal artifacts show the creator’s name (gray).
Clicking the card body opens the artifact’s detail page. Hovering over a card reveals a “More actions” button in the top-right corner (always visible on touch devices).

​
Creating an artifact

Click New artifact in the upper-right corner of the page to jump to the chat page with a prefilled draft prompt:
I want to build a publishable Artifact in Flashduty AI-SRE: a self-contained web page or report, published to the artifact gallery when done. Ask me a few focused questions about the audience, content/data, interactions, and visual style, then build it and publish it.
The agent first asks you about the target audience, content/data source, interactions, and visual style, then builds and publishes the artifact — there is no form to fill out directly.
Separately, any file shown in a session with present_files also has a “Publish to artifact gallery” button next to it, letting you publish a file that session already produced directly as an artifact — a more direct path than “New artifact” when you don’t need a fresh conversation.

​
Card Actions

The “More actions” menu on each card offers:

​
Detail Page

The detail page route is /ai-sre/artifacts/:artifactId. The top toolbar offers:
  • Title: if you have edit permission, click the title to edit it inline (no separate form) — press Enter to save, Esc to cancel;
  • Creator: shown below the title as “Artifact by [creator]”;
  • Share: opens the share panel, where you can choose between “Account only” and “Public link” visibility — see Share an artifact below;
  • Delete: shown only when you have edit permission; requires confirmation;
  • More actions: this menu appears only when at least one of the following is available —
    • Download: shown when the artifact is linked to a file.
    • Change scope: shown when you have edit permission. You can move the artifact to an accessible team; the creator can also change it back to Personal.
Below the title there is a source-session strip:
  • It shows the artifact’s own “Created …” / “Edited …” timestamps (like the list cards: both are shown only when they differ);
  • When you still have access to the artifact’s source session, the strip also shows a “Recently updated from session 〈session name〉” button — the session name is resolved from the source session via /safari/session/get, and clicking it opens that session’s full conversation (chat?session_id=<sessionID>, messages, tool calls, artifact history). If the source session was deleted or you no longer have access, the button is hidden and the artifact itself remains fully viewable.
The body renders the artifact according to its actual content type (for example, an HTML report renders inline as a page).

​
Share an artifact

The Share button in the detail page toolbar opens the share panel. Manage permission at the top lists who can manage sharing for this artifact (the creator is labeled “Owner”; team artifacts also list team members). Visibility below offers two modes:
Plan requirement: Public links require an On-call Pro or higher subscription, opening together with the AI SRE public beta. Learn more
After you choose Public link, the panel first shows a content preview and a risk notice; the link only takes effect once you click Generate public link:
Once you generate a public link, anyone who gets the link can view this artifact, and the link can be forwarded further. Don’t share secrets, personal information, or unauthorized third-party content.
On success, the link is copied to your clipboard automatically (a “Public link generated and copied to clipboard” toast appears). The public link takes the form https://<console-domain>/share/artifact/<artifact-id> — it’s identified by the artifact’s own ID and carries no token; anonymous access is served entirely by the CDN, without going through any endpoint that requires sign-in. Visitors who open a public link see a read-only content page: next to the title, the top of the page carries the disclaimer “Content is user-generated and unverified.” and a “Feedback” entry — clicking it opens a report form (pre-filled with the current link) so anyone can report inappropriate content to Flashduty. The page also provides a “Sign in” entry that leads visitors to the console.
Artifacts larger than 16 MiB can’t generate a public link — you’ll see a notice that the artifact exceeds the size limit. You can still share it using “Account only” mode.

​
Permissions

Whether an artifact is editable (rename, change scope, delete) is determined by the can_edit field returned by the backend. Any one of the following grants management access: Artifacts you cannot edit only expose read-only actions such as “Copy link” and “Download” — the “Rename” and “Delete” buttons do not appear.
This differs from the automation rule permission model: the account Owner / admins have management access to any artifact, including other members’ personal artifacts — there is no “no exemption for personal resources” restriction here.

Console

Learn how sessions surface files with the present_files tool — the source of every published artifact.

Usage Insights

The operational insight report generated by /insight is itself an artifact, manageable from the gallery like any other.

Automations

Reports produced by scheduled automation runs can also be published as artifacts, giving them a permanent home in the gallery.