Artifacts & exports

When the deliverable is a document rather than a chat reply — a memo, a dataset, a script — the analyst creates an artifact: a card in the conversation that opens in its own panel, with version history and download actions.

How do I get one?

The fastest route: type /memo or /sheet in the composer. Or simply ask for the deliverable by name — “write this up as a memo” produces a document, “put this in a table I can download” produces a spreadsheet, “give me that as a Python script” produces code. A plain question stays a chat answer; the analyst creates an artifact when you ask for something you’ll keep or refine. Already have the answer in chat? Ask retroactively: “turn that table into a downloadable sheet.”

There’s no need to ask for a PDF or an Excel file — formats are chosen at download, not at creation. When the artifact’s card appears, open it and pick the format from the actions at the panel’s bottom right: Markdown, PDF, or Word for documents; Excel or CSV for sheets. Two more one-click actions sit there on sheets: Format and clean data and Chart this data.

Text documents

Memos, notes, and write-ups, formatted as rich text. Download as Markdown, PDF, or Word (.docx). Text artifacts are revised through chat — tell the analyst what to change and a new version appears; a version pager lets you compare. For hand-editing, export to Word and continue there.

Sheets

Tabular deliverables — comparison tables, screen results, computed panels — live as spreadsheet artifacts. Download as Excel (.xlsx) or copy as CSV. From a sheet you can also ask for a cleanup pass or “chart this data” directly.

Code

When you ask for a script — say, the analysis translated into something you can run in your own environment — it lands as a code artifact you can copy out.

Charts

Charts are not artifacts but carry their own export: a download button on each chart card exports the plotted series as CSV. See Charts.

A note on numbers in documents

Artifacts follow the same grounding rules as answers: tables are built from data fetched or computed this session — the analyst is instructed never to invent rows. The same caveat applies too: check before the numbers leave the building. See Does Quantesta make up numbers?