Skip to content

A conversation holds the exchange around a task: your messages, the Operator's responses, activity, and results. A run is the work performed in response to an accepted request. As you review and refine a result, one conversation can contain several runs.

Where conversations belong

ProductConversationsShared context
AgentMultipleThe Agent's configuration and working resources.
ChatOne per ChatIts working files and eligible Workspace configuration.
ProjectMultipleProject source, development configuration, and working resources.

Use the same conversation when a follow-up depends on the current task. In an Agent or Project, a separate conversation can organize a different objective, but it does not create private copies of the resource's files or a separate access boundary.

Example: revise a report

After reviewing a generated report, make the revision specific:

Update customer-report.md with the corrected April figures in this attachment. Keep the recommendations section, but flag any recommendation that the new figures no longer support.

The Operator has the existing exchange as context, and the filename identifies the working result. Open the saved file afterward to confirm the correction.

If someone else is editing the same Agent or Project files from another conversation, coordinate the changes. Separate message histories do not isolate shared working files.

Inputs and results

ContentRole
ArtifactsRetained interactive experiences.
File systemEditable working files and ordinary generated results.
PlansProposed work and its reviewable execution scope.
SourcesInputs supplied for the conversation to use.

A link in an earlier response can refer to a particular result or revision. The current working file may have changed since that response; use the linked version when reviewing what was delivered at the time.

Guide work in progress

Prepare requests with the Composer. When work is running, distinguish a correction to the current task from a follow-up task: Messaging explains steering and queuing, along with stopping and resending behavior.

The Operator guide explains how a request becomes work. For recurring tasks, use Schedules: each occurrence starts a fresh conversation rather than continuing the exchange that created it.