Work Products

Work products are what your agents produce in sessions: spreadsheets, PDFs, drafts, charts, images, videos, audio, and links. Each one lives with the session that made it, and all of them collect on the Work Products page, so you can find any deliverable without remembering which conversation produced it.

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

The gallery renders each type natively: PDFs page by page, spreadsheets with their sheet tabs, images and charts inline, markdown and text formatted, and app drafts as previews you can run. Videos and audio play in place, and seeking works however long the recording is; a format your browser can’t play is offered as a download instead. Word documents are packaged for download. Links an agent delivers appear as pills that open the source. When an agent writes to a document or a data table, its card points to the durable entity instead, labeled with where that entity lives.

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	PDF	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
Launch teaser, 20 seconds	Video	An ask to the marketing agent

Videos

Ask for a short video, such as a title card, an animated chart, a product teaser, or captioned slides, and the agent builds it as an animated web page, then renders it frame by frame into an MP4 that plays in any browser. Before handing it over, the agent looks at a sheet of frames from the finished video to check that the text fits and the motion lands where it should. A rendered video can carry a soundtrack, and you can name the length, the frame rate, and the shape: 1920 by 1080 by default, or 1080 by 1920 for a phone.

A video can be narrated. The agent writes the script and a voice model on its workstation reads it aloud, in English, Spanish, French, Hindi, Italian, or Portuguese, with a choice of voices; the agent times the scenes to the voice and can lay music you provide under it. The same voice produces audio on its own, such as a spoken briefing, and the agent checks what it recorded by transcribing it back.

A work product can be up to 4 GiB. Large files and recordings are kept in storage encrypted under your organization’s own key, and play or download from the card through a link that expires after 15 minutes.

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

Search the gallery, filter by agent or by type (text and markdown, PDF and Office files, spreadsheets, images, video and audio, code), and sort by when each was last updated or by title. Rename a card in place when an agent’s title doesn’t say what it is. Filtering by agent turns the gallery into a series archive: filter to the sales agent and sort by Updated, 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. A download is the full file, saved under the card’s title with its extension added, so a video titled “Launch teaser” arrives as launch-teaser.mp4.

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.

Keeping the ones that matter

A work product belongs to its session. When one deserves a life of its own, promote it from the viewer. Save as document copies a markdown or text draft into a document you and your agents can edit, comment on, and keep current. Save as data table copies a CSV or a JSON list of records into a data table, after you confirm each column’s type. Either way you choose the copy’s audience — only you, or everyone in the workspace — and later changes to the copy and the original aren’t synced. An app draft is promoted with Publish as App, covered in Apps.

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 one-off deliverable is fine as a work product; a report the team will revise belongs in a document; a living dataset the team should query belongs in a data table; a tool people interact with belongs in an app.