Agent Platform

Getting Started

Upload your first mission and get a report on it from the agent

Use this page to get your first run into Alloy and a first report on it, usually in one sitting.

When a robot misbehaves, the answer is usually in a large log, often across several runs. Step one is to get those logs into Alloy. Each upload becomes a mission. Alloy processes it, and the agent can then investigate it with you.

New Agent Platform workspaces start with a sample mission, so you can try the agent before your own data arrives.

Quick start: Browser upload

Go to Missions in the sidebar
Click Upload in the top right
Click Click to upload to pick files, or drag and drop them into the window
Optional: add a Mission Title. Without one, Alloy names the mission for you.
Optional: add a Mission Description. The agent uses it as context, so add the issue, field notes or a Jira ticket link.
Click Upload N files (the button shows how many files you added)

All the files in one browser upload become one mission. The uploader does not read folder names. This is useful when several robots ran together, or when one run is split across several log files.

Supported file types

Missions accept MCAP (.mcap) and a standard set of robotics log formats: ROS 1 .bag, MAVLink .tlog, PX4 .ulg/.ulog, and ArduPilot .bin. You can combine them in one upload. Alloy converts them to MCAP during processing. You can also add metadata.json (or .yml/.yaml) files with your data, see Metadata.

The uploader skips other file types. To analyse a CSV, text log or other file once, attach it in the chat instead. The agent can also convert telemetry like this to MCAP and create a mission from it once you confirm. Support for other formats is available on request.

Other ways to get data in

If your robots or ground stations already upload runs to a bucket, keep that flow. Alloy watches the bucket and creates missions from new runs, with no manual uploads.

  • Each new top-level folder under the watched path becomes one mission
  • Files in nested folders are included in that folder's mission
  • Include a metadata.json file to attach structured metadata (operator, vehicle, location, etc.)

See the setup guides for AWS S3 and Google Cloud Storage.

Alloy Edge runs on your robot or a machine next to it, and uploads new recordings to Mesh Storage automatically.

Go to Mesh Storage → Devices in the sidebar and click Add device
Follow the guided setup to install Alloy Edge and link it to your organisation
Point Alloy Edge at the folder where your recorder saves files

Edge uploads land in Mesh Storage. If your organisation has both Mesh Storage and the Agent Platform, Alloy creates missions from new Edge recordings automatically. To change how files are grouped into missions, open organisation settings, go to the Missions tab and choose Create missions from Mesh. See Alloy Edge setup for the full guide.

Attach .mcap files in the web chat and ask the agent to make them a mission. It is processed like a browser upload. See Create a mission from chat.

Folder structure for cloud storage

When Alloy watches a bucket, it maps folders to missions:

  • Each folder at the top level of the watched path becomes a separate mission
  • All files inside a folder are grouped into that mission, at any depth
runs/
├── 2026-03-15_survey-north/        → one mission
│   ├── robot1/
│   │   ├── recording.mcap
│   │   └── metadata.json
│   ├── robot2/
│   │   ├── recording.mcap
│   │   └── metadata.json
│   └── metadata.json               ← mission-level metadata
└── 2026-03-16_survey-south/        → another mission
    └── recording.mcap

Metadata JSON

Add a metadata.json file to a mission to attach structured metadata. A metadata.json next to a recording applies to that recording. These values become filters in the mission library.

{
  "operator": "Jane Smith",
  "vehicle": "AUV-03",
  "location": "Harbour East",
  "firmware_version": "2.4.1",
  "notes": "Post-maintenance checkout dive, calm conditions"
}

All fields are optional and flexible. Use the key-value pairs that fit your workflow. The values appear as filter options in the mission library.

What happens during processing

After your data arrives (by any method), Alloy processes it. The mission card on the Missions page shows progress in three steps.

  • Early Access appears on the card when the mission's data is ready to query. You can start asking the agent about the run before processing finishes.
  • When processing finishes, your report automations run. New organisations start with a First-look report: what happened, the key findings, metrics, charts and a timeline, with the evidence behind them.

Processing time depends on the size of your files.

Viewing your results

When processing finishes, click View mission on the mission card (in the new design, click the card). The mission page shows the mission's report, its metadata, plots and a map when the data supports them, and comments from your team. Click Ask AI on the mission to ask the agent about it. See Missions for a full tour.

What's next?

On this page