Agents

Data Analyst

Data Analyst answers questions about a CSV or Excel file you attach โ€” with charts and a short note on how it worked the answer out โ€” and cleans or extends a workbook by handing back an edited copy with a change log. Your original file is never changed.

At a glance

Handle@data-analyst
AvailabilitySeeded in every organisation
Tagsdata, analysis, charts
Model tierdefault
Autonomysupervised
Toolscode_execution, calculate (and render_chart in web chat)
Max turns12
FilesCSV, TSV, XLSX, XLSM (read as data โ€” macros never run). Up to 25 MB per file.

How it works

  1. It sees the shape of your data first

    When you attach a spreadsheet, the agent is given its outline โ€” every sheet, each column with its type, the row count and the first rows โ€” so the analysis is right the first time.
  2. The analysis runs in the sandbox

    Your file is copied into an isolated sandbox with no network access, and the agent works on it there with pandas. Nothing it writes can leave except the results it hands back.
  3. Charts from the computed result

    A summary table the analysis produces becomes a chart directly โ€” the numbers are never retyped โ€” and you can explore it like any chart in chat.
  4. A Method note, and the script

    Every answer ends with which sheet and rows were used, what was excluded and why, and how it was calculated. The script that produced it comes back as analysis.py, so "show me how" is a download.

Cleaning or changing a workbook

Ask it to "clean up the dates", "add a margin column" or "remove the duplicate rows" and you get <your file> (edited).xlsx back. It is edited in place on a copy, so formatting and formulas it did not touch survive, and it carries a Change log sheet listing every change โ€” sheet, cell or column, before, after and why.

Legacy .xls files The old binary .xls format can't be read. Open it in Excel and use Save As โ†’ Excel Workbook (.xlsx), then attach it again.

How the router finds it

Attach a spreadsheet and ask one question about it, and the request reaches the agent tagged data before any model is asked. A request that also asks for something else โ€” "analyse this and book me a flight" โ€” is planned across agents instead, so nothing you asked for is dropped. Without an attachment, the router decides as usual.

It is a normal agent, so you can change it Every built-in is an ordinary org-ring registry agent with a versioned Agent.md. Edit it, publish a new version, roll back โ€” the platform only re-publishes its own definition when you have not taken it over. See Build & promote.