Work Products
Work products are the durable output of agent work — “documents, spreadsheets, and other artifacts your agents produce along the way.” They outlive the session that produced them and collect on the Work Products page.
This matters because agent output accumulates quickly. A weekly report assignment alone produces fifty-two documents a year; add a few research requests and a couple of drafting agents and the deliverables number in the hundreds. The gallery is where all of it stays findable, and provenance is what keeps it trustworthy — every artifact traces back to the run that made it.
What agents produce
Section titled “What agents produce”The gallery renders each type natively: PDFs page by page, spreadsheets with their sheet tabs, images inline, markdown and text formatted, and published apps as previews. Word documents are packaged for download. Links an agent delivers appear as pills that open the source, and data-table outputs jump straight to the table.
A week of output in a busy workspace might look like this:
| Work product | Type | Where it came from |
|---|---|---|
| Pipeline report — week of June 8 | The sales agent’s weekly assignment | |
| Campaign performance breakdown | Spreadsheet | An ad-hoc ask in a session |
| Launch announcement, third draft | Markdown | The content agent |
| Competitor pricing pages | Images | The research agent’s Friday sweep |
Asking for the right deliverable
Section titled “Asking for the right deliverable”The shape of a work product is decided where the work is described — in an assignment’s instructions or in your message to the agent. The assignments guidance puts it directly: “produce a document with a summary table and week-over-week changes” beats “summarize the pipeline.” Naming the format, the structure, and the audience gets you a deliverable you can forward without rework:
Deliver the analysis as a PDF. Page one is a summary a VP can read in two minutes: a table of open deals by stage, then the five largest at-risk deals with a one-line reason each. Put the detail behind it. Title it “Pipeline report” with the week’s date.
Finding and using them
Section titled “Finding and using them”Search the gallery, filter by agent or by type (documents, spreadsheets, images, code), and sort by date or name. Filtering by agent turns the gallery into a series archive: filter to the sales agent and sort by date, and a year of weekly reports reads in order.
Every work product keeps its provenance: the card links to the agent and to the session that produced it, so the full reasoning behind any artifact is one click away. A session records every thought, tool call, and result, which means “where did this number come from?” has a real answer — open the session and read the run. Open a work product itself to page through it, copy its text, review its version history, or download it.
Work products also meet you where decisions happen: when an agent finishes something worth showing, it can send it to your Inbox, where attached work products open right from the thread.
Patterns that work
Section titled “Patterns that work”- The standing report — a scheduled assignment delivers a document on cadence, and the gallery becomes the archive nobody had to file. See the weekly report guide.
- Research on demand — one-off asks (“compare these three vendors,” “summarize this contract”) leave durable artifacts you can search long after the conversation is forgotten.
- The right surface for the job — a readable deliverable is a work product; a living dataset the team should query belongs in a data table; a tool people interact with belongs in an app.
For the complete site index, see llms.txt.