Using the Chat

What you can do with Alloy AI — search, analyze, visualize, and create reports through conversation

Alloy AI is a conversational interface available throughout the platform. Ask questions, run analysis, build visualizations, and generate reports — all in natural language.

Where to find it

Home page — the chat is front and center
Chat panel — click the Alloy AI button on the right edge of any page
"Ask AI" buttons — quick-launch buttons on mission summaries and other pages, plus the Ask AI option at the top of Search results

The chat is context-aware — the dotted badge above the input shows the current page included with your next message. Ask a question on the Missions page and it references your current filters. Ask on a report and it can modify that report.

Choose the context

Current page — the dotted badge follows you as you navigate and is always included. It cannot be removed.
Other missions and reports — click @, or type it in the input, to search by name or ID. The picker initially shows five recent items. References you add stay selected when you navigate or reopen the sidebar; starting a new chat clears them.
Continue a task — a clear follow-up such as "apply that title" keeps the agreed target, even after you navigate elsewhere. A new request normally uses the current page. Name the report or mission when you want a different target, or say "keep this in chat" for a response without editing it.

What you can do

Find data across your mission library:

"Find moments where two robots were at the same waypoint but reported different terrain classifications"
"Can you find any joint temperature spikes that correlate with the gait stumbles?"
"Find all perimeter patrols that completed without intervention and summarize the stats"
"Search for images where the robot encountered standing water"

Supports text search, log pattern matching, and image search — describe what you're looking for visually.

Run analysis on your data, including SQL queries and Python code:

"Walking speed should drop from 1.2m/s to 0.3m/s when the robot enters a confined space — find cases where that transition didn't happen"
"Describe path-planning failures and how they lead to missed waypoints on the inspection route"
"Track CPU, GPU, RAM, and joint motor temperatures per robot per mission — identify spikes and how they trend week to week"

Behind the scenes, Alloy can query your data warehouse and run Python with pandas, numpy, matplotlib, geopandas, scikit-learn, and more — all in a secure sandbox.

Create interactive visualizations for reports:

"Plot where the leg servo errors begin and how they accumulate over the patrol"
"Show me a map of all inspection routes overlaid on the facility layout"
"Build a weekly comparison dashboard of system health metrics per robot by serial number"
"Make a timeline of key events during this inspection run"

Visualizations can be embedded in reports for sharing.

Generate and refine custom reports:

"That stair-climb failure you found for QP-07 during the warehouse inspection — make a report about what happened"
"Create a report on how joint calibration drift builds up across back-to-back patrols"
"Remove the battery section and focus on navigation"

See Creating a Report for more.

Set up pattern scanners:

"Create a scenario to flag any patrol where battery drops below 20% before returning to dock"
"Set up a scanner for leg motor fault events"

See Scenarios for more.

Open the Replay Viewer at exactly the moment you're discussing — with the right panels already laid out. Be as vague or as specific as you want:

"Show me the altitude drop around 14:32 on yesterday's patrol"
"Open the replay where the obstacle avoidance kicked in"
"Show me battery and motor-current time-series with the map on top and camera5 in the bottom left"

Alloy AI picks the panels — 3D scene, map, time-series, text log — arranges them, and seeks every stream (video, telemetry, map cursor) to the exact instant in question.

Save the layouts you want to reuse. Once a layout works for the question you're asking, save it — next time you ask something similar, the agent will reopen it instead of rebuilding from scratch.

Analyze attached data files

Attach CSV or text telemetry, RINEX observations and navigation files, RTCM3 correction logs, Septentrio SBF recordings, or ZIP bundles directly in chat. For example: "Summarize the satellites and observation gaps in this RINEX file" or "Compare these odometer counts with the flight telemetry."

RINEX filenames can use .rnx, year-based suffixes such as .26O and .26P, or Septentrio export suffixes such as .sbO and .sbN. RTCM3 logs can use .rtcm, .rtcm3, or .bin; .bin files must contain a recognized format. Septentrio binary recordings use .sbf. ZIP bundles let you attach related files together; Alloy can inspect and analyze selected members.

RINEX 2.10 SBAS L1 broadcast files such as .sbB can also be inspected. Alloy decodes supported message fields and reports records with invalid checksums or unsupported message types. For NTRIP captures, it can remove HTTP chunk framing and use a recorded UTC date when the stream provides one. Missing units, clock information, and status definitions still require the recording's documentation. Upload raw ANPP recordings as missions to use the mission decoding workflow.

Alloy can parse these files, summarize their contents, plot measurements, and export analysis tables. Chat attachments do not automatically become missions or replay recordings. Parsing GNSS observations does not itself calculate an RTK/PPK position solution. When comparing files, provide timestamp conventions, units, and any known synchronization offset.

Uploads are limited to 250 MB per file, 1 GB total, and 10 files per message. For large recordings, ask for a specific time window or satellite selection.

Tips

Iterate — start broad, then refine with follow-ups
Use the context — on a report, ask it to modify sections; from Search, select Ask AI to explore a topic with AI
Highlight text — select text on the Home page, Chat, Missions, or Reports and click "Ask about this" to include it as context