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

# Forge

The repository itself — branches, commits, tags and releases — sitting in the channel whose work produced them.

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


This surface is the repository itself: branches, commits, tags and releases.
Project shows the files of one worktree and Terminal shows a shell on it; this
surface shows the repository those two sit inside.

## One unit of work, not three

A branch, a worktree and a <a class="docs-term" href="/docs/reference/glossary/#channel">channel</a> are
one unit of work here rather than three objects a person keeps in step by hand.
A channel created around a branch already has the checkout, the shell and the
repository view;
nothing has to be pointed at anything.

The reverse holds too. A branch here is a channel's branch, so the question
"what is this branch for" has an answer that is a conversation rather than a
name somebody chose six weeks ago.

## How it relates to the other repository surfaces

Three surfaces touch the same code and answer different questions.

| Surface  | The question it answers                                 |
| -------- | ------------------------------------------------------- |
| Terminal | What is running on this checkout right now              |
| Project  | What do the files say, and what did this change touch   |
| Forge    | What does the repository hold: branches, tags, releases |

Review is the fourth, and it is about a proposed change rather than the
repository's contents.

## Commits here, pull requests in Review

An <a class="docs-term" href="/docs/reference/glossary/#agent">agent</a> working in a channel commits to
that channel's branch, and its commits appear here along with everyone else's.
The proposal built from them — the pull request, its checks and its comments —
belongs to Review.

## Where the repository lives

A <a class="docs-term" href="/docs/reference/glossary/#first-party">first-party</a> git host is planned.
Today the repository is held by the connected host, and the
<a class="docs-term" href="/docs/reference/glossary/#provider">provider</a> block above names the store
that holds the <a class="docs-term" href="/docs/reference/glossary/#record">record</a>. A pull request
against that repository, with its checks and its comments, belongs to Review.
Whichever host holds the pull request, the
<a class="docs-term" href="/docs/reference/glossary/#conversation">conversation</a>, the agent roster and
the permission model are the same.