Review the newest pull-request context, decide whether the branch is ready, and open local follow-up work when needed.
Start in Activity to find new comments, reviews, and state changes. Open Pulls for the review queue.
The list shows review state, CI, branch information, and repository context. Select an item to open its description, timeline, actions, and diff.
Use local workflow statuses when you need a personal queue such as "needs my review" or "waiting for author." These statuses stay in Forge and do not change labels or project fields at the provider.
- Check review state and CI.
- Read the description and latest discussion.
- Inspect the diff and file tree.
- Comment, approve, mark ready, close, reopen, or merge when supported.
Unsupported actions remain visible but unavailable.
In Files, select a line to draft an inline comment. When the provider supports native multiline ranges, you can also select a contiguous range. Drafts stay local until you publish the review. Kenn Forge rejects a draft if the pull request head changed after you started it, so comments cannot land on the wrong revision.
Published threads appear in the pull request timeline. Thread resolution and review actions depend on provider support.
Detected stacks show their member order. Forge blocks a mid-stack merge by default while an earlier member is still open. Land the earlier pull requests first, or use the provider when you intentionally need a different order.
The conversation, files, and workspace can share one layout. Drag tabs to split the view, resize the panes, or maximize the diff while reviewing a large change.
Open Create Workspace and choose a configured agent such as Codex.
Forge creates and tracks a Git worktree for the pull-request
branch, then launches the agent there. You do not need to run
git worktree add or manage a separate checkout.
Workspaces keeps the branch, session, and review links together. Return to the pull request after local verification or follow-up changes.
