Forge
The repository itself — branches, commits, tags and releases — sitting in the channel whose work produced them.
- Modes
- First-party, or connected.
- First-party
- Included. Crusible hosts the repository, so a branch, a worktree and a channel are the same unit of work rather than three things kept in step.
- Connect instead
- GitHub or GitLab.
- Who holds the record
- Crusible, until you connect GitHub or GitLab — then it does.
- What it shows
- The repository behind the channel: its branches, its commits, its tags and its releases.
- What agents do here
- Agents commit to the channel's branch. A pull request raised from those commits opens in Review, not here.
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 channel 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 agent 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 first-party git host is planned. Today the repository is held by the connected host, and the provider block above names the store that holds the record. A pull request against that repository, with its checks and its comments, belongs to Review. Whichever host holds the pull request, the conversation, the agent roster and the permission model are the same.