Project
Mounted files, editing, working changes and comparisons for the channel.
- Modes
- First-party only.
- First-party
- Included. The worktree is Crusible's own filesystem — that is what lets every channel own its files.
- Connect instead
- Nothing to connect — Crusible provides this one.
- Who holds the record
- Crusible. There is no provider to hand it to.
- What it shows
- The repositories mounted into the channel's worktree, a file tree, an editor pane, and the diff for the work in hand.
- Controls
- File selection, search, editing, supported file operations, changes and comparison views.
- What agents do here
- Agents work on the mounted files; changes remain separate from pull request review.
Files and repository scope
Project displays the files mounted for the channel. The file tree and the current file belong to that mount. A pull request in Review is a separate view of a proposed change; its head can differ from the current working files.
The tree supports file selection and search. The editor shows the selected file and its path. Large or shortened content can limit editing and comparisons. The current location matters when another channel has a different checkout.
Editing and file operations
Editing is available when the connected agent supports writes. File and folder creation, rename, move, copy and deletion each depend on the operations that connection supports. An unavailable operation does not become available by reloading the page.
Saved file changes are working files. They do not by themselves create a commit, open a pull request or merge a branch. Changes and comparisons show differences within the selected checkout.
Conflicting edits
A file changed elsewhere can conflict with an unsaved edit. The conflict controls provide comparison, keeping both versions or overwriting the workspace version when the connection supports the required operation. Keeping both requires permission to create another file. An overwrite replaces the workspace version, so it can remove another edit.
Connection loss can leave local edits waiting to save. A visible local draft is not confirmation that the workspace received it. A read-only or disconnected state does not grant permission to overwrite files.
Worktrees and other tools
A worktree has its own checked-out files. Opening another channel does not move unsaved edits into that channel’s checkout. A worktree picker is not available in Project. Worktree creation and changes remain separate from selecting a file in the tree.
The terminal control opens Terminal when that action is available. Project does not provide a separate run dock or a preview launcher. Repository membership, repository settings and project dashboard administration are not file-tree operations.