# Projects

> Group conversations around one body of work and give an agent standing context it reads on every run.

A **project** groups the [conversations](/docs/work/conversations/) that belong to the same body of work, and carries context every conversation inside it can read.

## When to use it

Use a project when you notice yourself re-explaining the same background in thread after thread — the client, the codebase, the launch, the quarter. The project holds that background once.

| Put it in | When |
| --- | --- |
| The [system prompt](/docs/build/system-prompt/) | It is true of everything the agent ever does |
| A project | It is true of this body of work |
| [Memory](/docs/capabilities/memory/) | It is true of you, across all work |
| A message | It is true of this one task |

## What a project gives an agent

A conversation inside a project starts with the project's context available. The agent can also read the project's current state and update it as work progresses — so a status the agent maintains stays current without you transcribing it.

That makes a project useful as a shared working record: what this work is, where it stands, what was decided.

## Working in one

Open the project and start a conversation from it, and that conversation belongs to the project. The project page lists its conversations, so returning to a body of work does not mean hunting through a global recency list.

<Aside type="note" title="A project is not a permission boundary">
  Putting a conversation in a project changes what the agent *reads*, not what it
  can *reach*. Access still comes from the [connections and skills](/docs/connect/overview/)
  bound to the agent.
</Aside>

## Limits

- A conversation belongs to one project.
- Project context is available to conversations in that project — it is not shared with the agent's other threads.
- Projects group work; they do not grant access, and they are not a place to store documents. Output belongs in [artifacts](/docs/capabilities/artifacts/).

## Related

<CardGrid>
  <LinkCard
    title="Conversations"
    href="/docs/work/conversations/"
    description="The threads a project groups."
  />
  <LinkCard
    title="Artifacts"
    href="/docs/capabilities/artifacts/"
    description="Where the output of a project's work lands."
  />
  <LinkCard
    title="Memory"
    href="/docs/capabilities/memory/"
    description="Context that follows you rather than the work."
  />
</CardGrid>