The forge panel shows the pull requests a Session created or pushed in a right-sidebar tab, with a Session header button and branch label, and lets a new Session start in its own Git worktree from the New Session options row. The forge bundle ships the panel with the forge registry, the GitHub provider, the Session bindings, and an isolated worktree service. The panel listens to the agent-controller/admission stage. It holds the first message of a Session with a worktree request while it creates and enters the worktree as Agent maintenance, and refuses messages while the worktree the Session works in is gone. A failed or stopped creation returns the message to the composer: the card above the composer shows the failure, sending again retries with a new branch name, and Continue without a worktree withdraws the request. A removed worktree can be checked out again or left for the source checkout. A message that enters without admission still gets its worktree at the first step proposal.
description, kind
| description | kind |
|---|---|
| Enable the pull request panel and worktree Sessions from the Plugins page. | package-bundle |
@deepseek-ai/dsh-experimental-forge-bundle
English | 中文
Summary
Show the pull requests each Session creates with their checks and reviews, and let a new Session start in its own Git worktree. Enable Pull requests & worktrees on the Web or Desktop Plugins page; shipped profiles leave it disabled. GitHub status comes from the gh CLI signed in on the Host; without it, the panel still shows the branch and the worktree option still works.
Table of Contents
- Use this package
- Understand the implementation
- Further Exploration
- Model Experience
- Known Limitations and Deferred Work
- Dev Note
Use this package
Open Plugins and enable Pull requests & worktrees in the Official group. In a Git workspace, check Worktree in the composer before the first message to start the Session in a new worktree. In a Session whose directory is inside a Git checkout, the header button opens the panel. Pull requests that the Session creates with gh pr create, or that a later git push updates, appear without further steps. Run gh auth login --hostname <host> in a terminal to sign in; the panel shows the command when sign-in is missing. The panel package describes each control.
Understand the implementation
Maintainer details — click to expand
The bundle patch inserts the forge registry, the GitHub provider, and the Session bindings as Host rows, and a group that isolates the worktrees service, holding a worktree service row and the panel's two-face package, whose Client half the Web and Desktop clients load while the row is enabled. The isolation lets the bundle coexist with the Git Worktrees bundle, whose model tool keeps its own service. The rows need the Session projection registry, working-directory, filesystem, subprocess, and sandbox services that every base-backed profile composes.
Further Exploration
Forge subsystem · Session bindings · Panel
Model Experience
None, as the composed packages add no model tool or prompt; the directory notice of a Session that starts in a worktree reaches the model through the working-directory service, as described by the panel.
KV Cache effect
None from the bundle; see the panel for the worktree notice.
Known Limitations and Deferred Work
- GitHub is the only code host provider, and the bundle serves github.com only; a GitHub Enterprise host needs a profile patch that lists it in the
forge-githubrow'shosts. No provider recognizes GitLab or other hosts. - The model has no tool for bound pull requests yet.
Dev Note
Working context for maintainers — click to expand
None.