Control file context

File context is branch-aware. The composer lets you build a selection from files associated with the current node, the active ancestor path, or the entire conversation.

Choose a scope shortcut#

In the Files panel, use:

• Node — select files uploaded or used at the current node;
• Branch — select files associated along the active path;
• Conversation — select available files from anywhere in the conversation.

These controls update the explicit file selection. Review the selected count and tiles before sending; the scope label is not a permanent automatic policy for every future request.

Why branch scope matters#

Suppose one graph branch analyzes a confidential draft while a sibling analyzes a public brief. Using Branch limits the working set to the selected lineage. Conversation scope is broader and can mix material from alternatives, so use it only when the prompt truly needs cross-graph files.

Inspect what a message used#

After sending, a file-count action beneath the message opens Included Files. It lists the exact file records carried into that turn with type, size, and date. Use this record when reviewing provenance or diagnosing why an answer referenced an unexpected document.

Generated attachments shown on the answer are outputs, not necessarily inputs. File citations are retrieved source chunks, while Included Files records the request’s file context.

File references can carry forward#

The active path preserves selected-file snapshots and branch-local file history. Generated images can also establish branch-local reference lineage for later edits or continuity prompts. Visiting a sibling branch does not intentionally replace the selected branch’s reference history.

Still, make important references explicit. Write “Edit the most recent kitchen image on this branch” or select the intended file rather than relying on an ambiguous pronoun.

Clear context#

Use Clear selected files in the panel when the next prompt should not include the current selection. A new branch can inherit contextual history, so inspect the file count after selecting an older node.