Files It Produces
The problem this solves
An assistant that answers in chat leaves you with the last step still to do: turning the answer into the thing you actually needed. A deck. A sheet your finance lead can open. A document you can send.
AI Partner finishes that step. Ask for the artefact and the artefact is what you get — built, checked that it actually opens, and waiting in one place.
Open Work → Generated Files to see everything it has made.
What it can produce
Real PowerPoint files — slides, layouts, charts, speaker notes. Not a text outline you then have to build.
Excel workbooks with live formulas, multiple sheets and formatting — openable and editable, not a CSV in disguise.
Word documents with headings, tables and structure, ready to send or put under review.
Self-contained HTML reports with charts and tables — one file, opens in any browser, nothing to install.
For anything that has to look the same everywhere, or be signed, filed or attached.
/image <prompt> generates an image. /video <prompt> generates a short clip. Both land here with everything else.
You don't pick a generator. Ask for "a deck comparing our top five competitors" and you get a deck; ask for "the same thing as a spreadsheet I can filter" and you get a workbook. Naming the format in the request is enough.
A goal that was asked for a file isn't considered finished until the file exists and opens. A run that produced only a chat summary when you asked for a deck is treated as incomplete, not as success.
Working with what it made
Each file in the list shows its type, its size and when it was made. All / PPTX / XLSX / DOCX / HTML / PNG filters narrow a long list.
| Action | What it does |
|---|---|
| Download | Saves the file to your machine |
| Open in new tab | Previews HTML reports and images in the app, without downloading first |
| Delete | Removes it |
Images preview inline in the list, so you can see what was generated without opening anything.
Preview before you download when you're iterating. Asking for "the same report with the chart as a bar chart" and glancing at the result is much faster than a download-open-discard loop.
Where files arrive
Every file lands in Generated Files regardless of how it was made, so there's one place to look:
- Produced by a goal — also linked from that run's progress panel
- Produced by a workflow — linked from the step that made it
- Produced by a job — linked in the job's thread, run by run
- Produced by a proactive briefing — and pushed to your messaging channel
- Asked for directly in chat with
/imageor/video
When a file is produced by scheduled or proactive work, it's delivered as well as stored — attached to the message on your messaging channel, so a report generated at 7am is on your phone, not just waiting in a list.