# Chats

A Chat is one conversation with a persistent working File system. Use it to explore a question, make a decision, create a deliverable, or return to work over time. You can collaborate on the same Chat when its owner grants access.

## What stays with a Chat

The conversation, working files, and saved results remain available beyond an individual run. Use [Sources](/docs/services/sources) for supplied inputs, [Files](/docs/configuration/files) for standing background, [Plans](/docs/operator/plans) for reviewed execution, and [Artifacts](/docs/artifacts/overview) for retained interactive experiences. A Chat uses eligible Workspace configuration and connections the person running it is allowed to use. Its chargeable work follows Workspace funding and budget controls.

## When to use something else

Use an [Agent](/docs/agents/overview) for a reusable specialist with its own configuration and API access. Use a [Project](/docs/projects/overview) when the result needs application code, a backend, or development services. You can hand selected Chat work into either resource deliberately. Start with the [Chat quickstart](/docs/chats/quickstart).

A [Workflow](/docs/workflows/steps) can start a fresh Chat and pass selected results to later steps. Use [Create and continue](/docs/chats/lifecycle) to start a new Agent or Project from a Chat instead.

## Context

A Chat uses its conversation and authorized Workspace resources to work on your request. Give it the relevant inputs; a resource existing elsewhere in the Workspace does not mean every person or Chat can use it.

### Add the right material

Attach supplied material as a Source when it should inform a conversation. Keep durable working outputs in the File system. Workspace Files and Skills may provide reusable context and instructions within their access rules. [Services](/docs/services/overview) explains the different lifecycles.

### Use connected tools

An account connection and permission to use it are separate. The Chat can invoke an eligible connection only under the initiating person's current authority and Workspace policy. Connecting an account does not give every collaborator its credentials or administrative control. See [connections](/docs/configuration/connections).

Chat configuration inherits from the Workspace. For a separately configured, callable specialist, use an [Agent](/docs/agents/configuration).

## Example: keep a proposal moving

Use one Chat to turn meeting notes into a proposal, revise the assumptions, and maintain a checklist of open decisions. Save the proposal as a working file so later requests can identify exactly what to change.

A follow-up such as “Update the delivery section to reflect the revised deadline; leave the scope unchanged” gives the Operator a bounded revision. See [Messaging](/docs/composer/messaging) and [File system](/docs/services/file-system).

See [Create with Chats](/changelog/create-with-chats) for the release overview.