Reports

Use this page to get written analysis of your runs without anyone writing it by hand, and to keep it coming automatically.

The Reports page is where you create and manage reports. Ask the agent to analyse your mission data and it produces a shareable, structured document.

Reports are created through conversation. Describe what you want to know, and the agent searches your data, runs the analysis, and builds the report. You can iterate on it through follow-up messages until it says what you need.

What reports can contain

• Narrative text and analysis
• Interactive charts
• Maps and 3D trajectories
• Metrics with trends
• Event timelines
• Images from your missions
• Links that open Replay at a moment
• Downloadable data files

Filtering charts in a report

Some reports include shared filters, such as a date range and fleet. Change the values and select Apply to update the charts connected to those filters. The end date is excluded from the range. Select Reset to restore the report defaults.

PDF export uses the applied filter values and lists them in the exported report.

Authoring shared filters

Add one alloy-report-filters block to the report Markdown. You can include a date range, a select control, or both. Parameter names must be distinct, and the select default must be one of its options.

```alloy-report-filters
{
  "dateRange": {
    "startParam": "start",
    "endParam": "end",
    "default": { "start": "2026-10-01", "end": "2026-10-04" }
  },
  "select": {
    "param": "fleet",
    "label": "Fleet",
    "options": ["North", "South"],
    "default": "North"
  }
}
```

In each chart that should respond, add reportParams alongside artifact_type and data. Every listed name must be declared in the filter block and have a default in the chart’s source.params. Use $name placeholders in the SQL. For example, this ECharts block queries a small synthetic fixture.

```alloy-artifact
{
  "artifact_type": "native_chart",
  "reportParams": ["start", "end", "fleet"],
  "data": {
    "version": 1,
    "format": "echarts",
    "source": {
      "kind": "sql",
      "sql": "SELECT day, issues FROM (VALUES ('2026-10-02', 'North', 6), ('2026-10-03', 'South', 32)) AS demo(day, fleet, issues) WHERE day >= CAST($start AS VARCHAR) AND day < CAST($end AS VARCHAR) AND fleet = CAST($fleet AS VARCHAR) ORDER BY day",
      "params": { "start": "2026-10-01", "end": "2026-10-04", "fleet": "North" }
    },
    "config": {
      "xAxis": { "type": "category" },
      "yAxis": { "type": "value" },
      "series": [{ "type": "bar", "encode": { "x": "day", "y": "issues" } }]
    }
  }
}
```

To connect a Vega-Lite chart to the same controls, use the same reportParams and SQL source with format set to vega-lite and a Vega-Lite config. Shared filters support inline native_chart blocks backed by Mesh SQL. Use distinct parameters for any chart-level query zoom.

Creating a report

Click Create at the top of the Reports page, or open the agent from anywhere and ask for a report. See Creating a Report for a full walkthrough.

First-look report

New organisations start with a First-look report automation. When an uploaded mission finishes processing, it writes a short report on what happened and what stood out, with the evidence behind it, and pins it as the mission's Pinned report, so it is highlighted on the mission page.

Each First-look report carries a comment from Alloy explaining where it came from. To change what future reports cover, ask the agent to edit the First-look report automation. You can also pause the automation, or pin a different recurring report (Pin this report in its settings).

Comments and attachments

Attach images, documents, or data files to a report comment, then ask the agent to inspect them. It opens the relevant attachments when needed; you do not need to upload them again in chat.

Version history

Each change to a report is kept. Open Version history from the report's menu to see earlier versions and click Restore this version to go back to one (Restore in the new design).

Recurring reports

Reports can run automatically, either each time a new mission arrives or on a schedule. Useful for a review of every run, fleet performance summaries, anomaly digests, or ongoing trend analysis.

In the new design, open the Trigger menu at the top of the Reports page and choose Trigger a report. The schedule option is called Date there.

You can also ask the agent to set one up, for example "Every time a new mission arrives, write a report on battery health." Manage is also where you view, edit or delete your recurring reports, and pause the ones that run on each new mission.

Managing reports

• Filters: narrow reports by Type, Author, Mission, Prompt (the recurring report that wrote it), or pinned and starred reports
• Sort: Newest or Oldest first
• View: click any report to see its full content
• Delete: use Delete report in the report's menu