See the complete route index at https://crusible.dev/llms.txt before following links.

# Project

The channel's mounted repositories, a file tree and an editor, plus the diff that the work in this channel actually produced.

<!-- https://crusible.dev/docs/reference/surfaces/project/ · doctype: reference · role: both · reviewed: 2026-09-05 -->


Project is the filesystem of one
<a class="docs-term" href="/docs/reference/glossary/#channel">channel</a>: the repositories mounted into
its worktree, the tree over them, and the diff for the work in hand. It is the
surface a Feature delivery channel opens with.

## The worktree belongs to the channel

The worktree is the channel's own rather than a person's or a machine's. That
is what lets every channel own its files: two channels working on two branches
are two checkouts, and neither can surprise the other. The
<a class="docs-term" href="/docs/reference/glossary/#conversation">conversation</a> and the files sit
beside each other in one frame, so reading a message and reading the code it
refers to are the same act.

## The tree and the editor

The file tree lists the mounted repositories and their contents. Selecting a
file opens it in the editor pane beside the tree. The conversation column can
be resized, collapsed, or set aside entirely when the files are the work.

## The diff

The diff is the point of the surface. When an
<a class="docs-term" href="/docs/reference/glossary/#agent">agent</a> commits, it posts an
<a class="docs-term" href="/docs/reference/glossary/#artifact-card">artifact card</a> to the
conversation naming the files it touched and the lines added and removed, and
that card opens here. A reader who wants the whole change reads it in Project.
A reader who only needed to know that a change happened never leaves the
conversation.

The change a reviewer reads later is the same change. Project shows it as
files in a worktree and Review shows it as a proposal with checks and
comments, but there is one set of commits underneath both, so the two surfaces
never disagree about what was written.

## Commits here, suggestions in Docs

Agents work on the files directly. An agent's edits to a repository are
commits on the channel's branch, attributed to the agent that made them, and
they reach the conversation as cards rather than as prose.

Editing a document is a different surface with different rules. In Docs an
agent's edit arrives as a suggestion that a person accepts or rejects; in
Project it arrives as a commit and a diff.