Skip to main content
A thread works with files in two directions: you bring files in as context (see Thread and composer for attaching one with @ or by dragging it in), and a thread produces files as it works. This page covers the second kind, the outputs a thread produces, often called artifacts.

Where outputs live

1

In the thread that produced them

Every file a thread produces stays attached to that thread, next to the work that created it. Open the thread to see its outputs alongside the conversation that led to them.
2

In Settings → Files

Every output across your threads and projects also collects in one place, under Settings → Files. Go there when you want to find a file without hunting through the thread that made it.

Preview, download, and restore

Outputs come in a few types: doc, sheet, code, and image. Click a file to preview it without leaving the page.
1

Preview

Open the file to see its content rendered in place, matching its type.
2

Download

Download the file to save a copy outside Sidekick.
3

Check version history

Every edit to a file is kept in its version history, each entry with a change note describing what changed.
4

Restore an earlier version

Open version history and restore an earlier version if a later edit went the wrong way. Restoring doesn’t erase the versions in between; they stay in the history.

Scope files by project

From Settings → Files, filter the list down to a single project when you only want to see the outputs that belong to it, instead of every file across your work.

Where to go next

Thread and composer

The anatomy of a thread and how the composer sends work to it.

Projects

Group related threads, files, and context into a single project.