gitkraken · Roberto-Vizcarra · Aug 25, 2026 · Aug 25, 2026 · Aug 25, 2026 · Sep 3, 2026
diff --git a/_images/gl-17-7-recompose-branch-01-v3@2x.png b/_images/gl-17-7-recompose-branch-01-v3@2x.png
diff --git a/_images/gl-17-8-compose-in-wip-01-v4@2x.png b/_images/gl-17-8-compose-in-wip-01-v4@2x.png
diff --git a/_images/gl-17-8-recompose-selected-commits-01-v4@2x.png b/_images/gl-17-8-recompose-selected-commits-01-v4@2x.png
diff --git a/_images/gl-access-composer-1-17-4-01-v3@2x.png b/_images/gl-access-composer-1-17-4-01-v3@2x.png
diff --git a/_images/gl-access-composer-2-17-4-01-v3@2x.png b/_images/gl-access-composer-2-17-4-01-v3@2x.png
diff --git a/_images/gl-access-launchpad-01-v3@2x.gif b/_images/gl-access-launchpad-01-v3@2x.gif
diff --git a/_images/gl-add-repo-to-workspace-01-v2@2x.png b/_images/gl-add-repo-to-workspace-01-v2@2x.png
diff --git a/_images/gl-agent-kanban-01-v2@2x.png b/_images/gl-agent-kanban-01-v2@2x.png
diff --git a/_images/gl-agent-working-01-v2@2x.png b/_images/gl-agent-working-01-v2@2x.png
diff --git a/_images/gl-ai-branch-summary-01-v3@2x.png b/_images/gl-ai-branch-summary-01-v3@2x.png
diff --git a/_images/gl-ai-commit-explain-01-v2@2x.png b/_images/gl-ai-commit-explain-01-v2@2x.png
diff --git a/_images/gl-ai-commit-generate-01-v2@2x.png b/_images/gl-ai-commit-generate-01-v2@2x.png
diff --git a/_images/gl-ai-create-pr-01-v2@2x.png b/_images/gl-ai-create-pr-01-v2@2x.png
diff --git a/_images/gl-ai-generate-changelog-01-v2@2x.png b/_images/gl-ai-generate-changelog-01-v2@2x.png
diff --git a/_images/gl-ai-generated-commit-message-01-v2.gif b/_images/gl-ai-generated-commit-message-01-v2.gif
diff --git a/_images/gl-ai-generated-commit-message-01-v3@2x.gif b/_images/gl-ai-generated-commit-message-01-v3@2x.gif
diff --git a/_images/gl-ai-stash-01-v2@2x.png b/_images/gl-ai-stash-01-v2@2x.png
diff --git a/_images/gl-auto-ai-rebase-01-v2@2x.png b/_images/gl-auto-ai-rebase-01-v2@2x.png
diff --git a/_images/gl-auto-rebase-resolve-01-v2@2x.png b/_images/gl-auto-rebase-resolve-01-v2@2x.png
diff --git a/_images/gl-autolinks-01-v3@2x.png b/_images/gl-autolinks-01-v3@2x.png
diff --git a/_images/gl-branches-view-01-v2@2x.png b/_images/gl-branches-view-01-v2@2x.png
diff --git a/_images/gl-cloud-integrations-01-v3@2x.png b/_images/gl-cloud-integrations-01-v3@2x.png
diff --git a/_images/gl-cloud-patch-create-01-v2@2x.webp b/_images/gl-cloud-patch-create-01-v2@2x.webp
diff --git a/_images/gl-code-lens-01-v3@2x.png b/_images/gl-code-lens-01-v3@2x.png
diff --git a/_images/gl-code-suggest-01-v2@2x.png b/_images/gl-code-suggest-01-v2@2x.png
diff --git a/_images/gl-column-gl-settings-01-v3@2x.png b/_images/gl-column-gl-settings-01-v3@2x.png
diff --git a/_images/gl-commit-composer-17-4-01-v5@2x.png b/_images/gl-commit-composer-17-4-01-v5@2x.png
diff --git a/_images/gl-commit-composer-composed-17-4-01-v6@2x.png b/_images/gl-commit-composer-composed-17-4-01-v6@2x.png
diff --git a/_images/gl-commit-graph-01-v3@2x.png b/_images/gl-commit-graph-01-v3@2x.png
diff --git a/_images/gl-commit-graph-compact-graph-01-v2@2x.gif b/_images/gl-commit-graph-compact-graph-01-v2@2x.gif
diff --git a/_images/gl-commit-graph-full-01-v2@2x.png b/_images/gl-commit-graph-full-01-v2@2x.png
diff --git a/_images/gl-commit-graph-settings-01-v3@2x.png b/_images/gl-commit-graph-settings-01-v3@2x.png
diff --git a/_images/gl-commit-search-moving-arrow-keys-02-v3@2x.gif b/_images/gl-commit-search-moving-arrow-keys-02-v3@2x.gif
diff --git a/_images/gl-commits-view-01-v2@2x.png b/_images/gl-commits-view-01-v2@2x.png
diff --git a/_images/gl-commits-view-merge-01-v2@2x.png b/_images/gl-commits-view-merge-01-v2@2x.png
diff --git a/_images/gl-commits-view-rebase-01-v2@2x.png b/_images/gl-commits-view-rebase-01-v2@2x.png
diff --git a/_images/gl-connect-remote-integration-01-v2@2x.png b/_images/gl-connect-remote-integration-01-v2@2x.png
diff --git a/_images/gl-connect-remote-integration-manager-01-v2@2x.png b/_images/gl-connect-remote-integration-manager-01-v2@2x.png
diff --git a/_images/gl-connect-to-remote-ghe-01-v2@2x.png b/_images/gl-connect-to-remote-ghe-01-v2@2x.png
diff --git a/_images/gl-context-menu-01-v2@2x.gif b/_images/gl-context-menu-01-v2@2x.gif
diff --git a/_images/gl-contributors-view-01-v2@2x.png b/_images/gl-contributors-view-01-v2@2x.png
diff --git a/_images/gl-convert-workspace-to-cloud-01-v2@2x.png b/_images/gl-convert-workspace-to-cloud-01-v2@2x.png
diff --git a/_images/gl-create-cloud-patch-example-01-v2@2x.png b/_images/gl-create-cloud-patch-example-01-v2@2x.png
diff --git a/_images/gl-create-vs-workspace-from-gl-01-v2@2x.png b/_images/gl-create-vs-workspace-from-gl-01-v2@2x.png
diff --git a/_images/gl-create-workspace-01-v2@2x.png b/_images/gl-create-workspace-01-v2@2x.png
diff --git a/_images/gl-current-line-blame-01-v3@2x.png b/_images/gl-current-line-blame-01-v3@2x.png
diff --git a/_images/gl-delete-cloud-patch-01-v2@2x.png b/_images/gl-delete-cloud-patch-01-v2@2x.png
diff --git a/_images/gl-enable-debug-log-01-v3@2x.png b/_images/gl-enable-debug-log-01-v3@2x.png
diff --git a/_images/gl-export-logs-01-v3@2x.png b/_images/gl-export-logs-01-v3@2x.png
diff --git a/_images/gl-file-history-view-01-v2@2x.png b/_images/gl-file-history-view-01-v2@2x.png
diff --git a/_images/gl-file-history-view-merge-conflict-01-v2@2x.png b/_images/gl-file-history-view-merge-conflict-01-v2@2x.png
diff --git a/_images/gl-filter-options-2-01-v3@2x.png b/_images/gl-filter-options-2-01-v3@2x.png
diff --git a/_images/gl-git-command-palette-01-v3@2x.png b/_images/gl-git-command-palette-01-v3@2x.png
diff --git a/_images/gl-gitlab-github-integration-01-v3@2x.png b/_images/gl-gitlab-github-integration-01-v3@2x.png
diff --git a/_images/gl-graph-compare-01-v2@2x.png b/_images/gl-graph-compare-01-v2@2x.png
diff --git a/_images/gl-graph-compose-01-v2@2x.png b/_images/gl-graph-compose-01-v2@2x.png
diff --git a/_images/gl-graph-details-panel-01-v2.png b/_images/gl-graph-details-panel-01-v2.png
diff --git a/_images/gl-graph-info-01-v2@2x.png b/_images/gl-graph-info-01-v2@2x.png
diff --git a/_images/gl-graph-review-01-v2@2x.png b/_images/gl-graph-review-01-v2@2x.png
diff --git a/_images/gl-graph-sidebar-01-v2.png b/_images/gl-graph-sidebar-01-v2.png
diff --git a/_images/gl-graph-wip-bar-01-v2.png b/_images/gl-graph-wip-bar-01-v2.png
diff --git a/_images/gl-gutter-blame-01-v2@2x.png b/_images/gl-gutter-blame-01-v2@2x.png
diff --git a/_images/gl-gutter-heatmap-01-v2@2x.png b/_images/gl-gutter-heatmap-01-v2@2x.png
diff --git a/_images/gl-hide-refs-01-v2@2x.gif b/_images/gl-hide-refs-01-v2@2x.gif
diff --git a/_images/gl-home-view-v16-01-v2@2x.png b/_images/gl-home-view-v16-01-v2@2x.png
diff --git a/_images/gl-home-view-v16.png b/_images/gl-home-view-v16.png
diff --git a/_images/gl-hovers-annotations-01-v2@2x.png b/_images/gl-hovers-annotations-01-v2@2x.png
diff --git a/_images/gl-hovers-annotations-changes-01-v2@2x.png b/_images/gl-hovers-annotations-changes-01-v2@2x.png
diff --git a/_images/gl-hovers-annotations-details-01-v2@2x.png b/_images/gl-hovers-annotations-details-01-v2@2x.png
diff --git a/_images/gl-hovers-current-line-01-v2@2x.png b/_images/gl-hovers-current-line-01-v2@2x.png
diff --git a/_images/gl-hovers-current-line-changes-01-v2@2x.png b/_images/gl-hovers-current-line-changes-01-v2@2x.png
diff --git a/_images/gl-hovers-current-line-details-01-v2@2x.png b/_images/gl-hovers-current-line-details-01-v2@2x.png
diff --git a/_images/gl-inspect-commit-details-01-v2@2x.png b/_images/gl-inspect-commit-details-01-v2@2x.png
diff --git a/_images/gl-inspect-overview-01-v2@2x.png b/_images/gl-inspect-overview-01-v2@2x.png
diff --git a/_images/gl-inspect-side-bar-01-v2@2x.png b/_images/gl-inspect-side-bar-01-v2@2x.png
diff --git a/_images/gl-jira-integration-01-v2@2x.png b/_images/gl-jira-integration-01-v2@2x.png
diff --git a/_images/gl-launchpad-code-suggest-01-v2@2x.png b/_images/gl-launchpad-code-suggest-01-v2@2x.png
diff --git a/_images/gl-launchpad-pin-or-snooze-01-v2@2x.png b/_images/gl-launchpad-pin-or-snooze-01-v2@2x.png
diff --git a/_images/gl-launchpad-quickpick-01-v2@2x.png b/_images/gl-launchpad-quickpick-01-v2@2x.png
diff --git a/_images/gl-launchpad-view-experimental-01-v2@2x.png b/_images/gl-launchpad-view-experimental-01-v2@2x.png
diff --git a/_images/gl-line-history-view-01-v2@2x.png b/_images/gl-line-history-view-01-v2@2x.png
diff --git a/_images/gl-link-repositories-in-workspaces-01-v2@2x.png b/_images/gl-link-repositories-in-workspaces-01-v2@2x.png
diff --git a/_images/gl-locate-repo-in-workspace-01-v2@2x.png b/_images/gl-locate-repo-in-workspace-01-v2@2x.png
diff --git a/_images/gl-menu-branch-history-01-v2@2x.png b/_images/gl-menu-branch-history-01-v2@2x.png
diff --git a/_images/gl-menu-commit-details-01-v2@2x.png b/_images/gl-menu-commit-details-01-v2@2x.png
diff --git a/_images/gl-menu-commit-file-details-01-v2@2x.png b/_images/gl-menu-commit-file-details-01-v2@2x.png
diff --git a/_images/gl-menu-commit-search-01-v2@2x.png b/_images/gl-menu-commit-search-01-v2@2x.png
diff --git a/_images/gl-menu-file-history-01-v2@2x.png b/_images/gl-menu-file-history-01-v2@2x.png
diff --git a/_images/gl-menu-repo-status-01-v2@2x.png b/_images/gl-menu-repo-status-01-v2@2x.png
diff --git a/_images/gl-menu-stash-details-01-v2@2x.png b/_images/gl-menu-stash-details-01-v2@2x.png
diff --git a/_images/gl-menu-stash-list-01-v2@2x.png b/_images/gl-menu-stash-list-01-v2@2x.png
diff --git a/_images/gl-menus-01-v2@2x.png b/_images/gl-menus-01-v2@2x.png
diff --git a/_images/gl-menus-example-01-v2@2x.png b/_images/gl-menus-example-01-v2@2x.png
diff --git a/_images/gl-minimap-2-01-v2@2x.png b/_images/gl-minimap-2-01-v2@2x.png
diff --git a/_images/gl-minimap-gl-settings-01-v3@2x.png b/_images/gl-minimap-gl-settings-01-v3@2x.png
diff --git a/_images/gl-move-view-01-v2@2x.gif b/_images/gl-move-view-01-v2@2x.gif
diff --git a/_images/gl-open-as-vscode-workspace-01-v2@2x.png b/_images/gl-open-as-vscode-workspace-01-v2@2x.png
diff --git a/_images/gl-output-01-v3@2x.png b/_images/gl-output-01-v3@2x.png
diff --git a/_images/gl-prefer-commit-graph-location-01-v2@2x.png b/_images/gl-prefer-commit-graph-location-01-v2@2x.png
diff --git a/_images/gl-proxy-settings-01-v3@2x.png b/_images/gl-proxy-settings-01-v3@2x.png
diff --git a/_images/gl-pull-request-icon-01-v2@2x.png b/_images/gl-pull-request-icon-01-v2@2x.png
diff --git a/_images/gl-rebase-01-v2@2x.gif b/_images/gl-rebase-01-v2@2x.gif
diff --git a/_images/gl-remotes-view-01-v2@2x.png b/_images/gl-remotes-view-01-v2@2x.png
diff --git a/_images/gl-remove-repo-from-wrokspace-01-v2@2x.png b/_images/gl-remove-repo-from-wrokspace-01-v2@2x.png
diff --git a/_images/gl-repositories-view-01-v2@2x.png b/_images/gl-repositories-view-01-v2@2x.png
diff --git a/_images/gl-revision-navigation-01-v2@2x.gif b/_images/gl-revision-navigation-01-v2@2x.gif
diff --git a/_images/gl-rich-commit-search-02-v2@2x.png b/_images/gl-rich-commit-search-02-v2@2x.png
diff --git a/_images/gl-scroll-markers-01-v2@2x.png b/_images/gl-scroll-markers-01-v2@2x.png
diff --git a/_images/gl-search-and-compare-view-01-v2@2x.png b/_images/gl-search-and-compare-view-01-v2@2x.png
diff --git a/_images/gl-search-options-01-v2@2x.png b/_images/gl-search-options-01-v2@2x.png
diff --git a/_images/gl-settings-01-v3@2x.png b/_images/gl-settings-01-v3@2x.png
diff --git a/_images/gl-settings-account-01-v2.png b/_images/gl-settings-account-01-v2.png
diff --git a/_images/gl-settings-ai-01-v2.png b/_images/gl-settings-ai-01-v2.png
diff --git a/_images/gl-settings-commit-graph-01-v2.png b/_images/gl-settings-commit-graph-01-v2.png
diff --git a/_images/gl-settings-dates-01-v2.png b/_images/gl-settings-dates-01-v2.png
diff --git a/_images/gl-settings-hovers-01-v2.png b/_images/gl-settings-hovers-01-v2.png
diff --git a/_images/gl-settings-integrations-01-v2.png b/_images/gl-settings-integrations-01-v2.png
diff --git a/_images/gl-settings-views-01-v2.png b/_images/gl-settings-views-01-v2.png
diff --git a/_images/gl-show-commit-graph-01-v2@2x.gif b/_images/gl-show-commit-graph-01-v2@2x.gif
diff --git a/_images/gl-sign-in-4-01-v3@2x.png b/_images/gl-sign-in-4-01-v3@2x.png
diff --git a/_images/gl-sign-in-ls-update-01-v3@2x.png b/_images/gl-sign-in-ls-update-01-v3@2x.png
diff --git a/_images/gl-sign-out-4-01-v3@2x.png b/_images/gl-sign-out-4-01-v3@2x.png
diff --git a/_images/gl-sign-out-ls-update-01-v3@2x.png b/_images/gl-sign-out-ls-update-01-v3@2x.png
diff --git a/_images/gl-source-control-01-v2@2x.gif b/_images/gl-source-control-01-v2@2x.gif
diff --git a/_images/gl-source-control-detach-01-v2@2x.png b/_images/gl-source-control-detach-01-v2@2x.png
diff --git a/_images/gl-stashes-view-01-v2@2x.png b/_images/gl-stashes-view-01-v2@2x.png
diff --git a/_images/gl-status-bar-01-v2@2x.png b/_images/gl-status-bar-01-v2@2x.png
diff --git a/_images/gl-tags-view-01-v2@2x.png b/_images/gl-tags-view-01-v2@2x.png
diff --git a/_images/gl-terminal-links-01-v2@2x.gif b/_images/gl-terminal-links-01-v2@2x.gif
diff --git a/_images/gl-view-pull-request-01-v2@2x.png b/_images/gl-view-pull-request-01-v2@2x.png
diff --git a/_images/gl-visual-file-history-01-v2@2x.png b/_images/gl-visual-file-history-01-v2@2x.png
diff --git a/_images/gl-workflows-2-cleaning-and-prep-context-me-01-v2@2x.png b/_images/gl-workflows-2-cleaning-and-prep-context-me-01-v2@2x.png
diff --git a/_images/gl-workflows-2-cleaning-and-prep-launchpad-01-v2@2x.png b/_images/gl-workflows-2-cleaning-and-prep-launchpad-01-v2@2x.png
diff --git a/_images/gl-workspace-indicators-01-v2@2x.png b/_images/gl-workspace-indicators-01-v2@2x.png
diff --git a/_images/gl-workspaces-sidebar-01-v2@2x.png b/_images/gl-workspaces-sidebar-01-v2@2x.png
diff --git a/_images/gl-worktrees-multi-wip-01-v2@2x.png b/_images/gl-worktrees-multi-wip-01-v2@2x.png
diff --git a/_images/gl-worktrees-tab-open-01-v2@2x.png b/_images/gl-worktrees-tab-open-01-v2@2x.png
diff --git a/_images/gl-worktrees-view-01-v2@2x.png b/_images/gl-worktrees-view-01-v2@2x.png
diff --git a/gitlens/GL-Branch-Prep-to-ship.md b/gitlens/GL-Branch-Prep-to-ship.md
@@ -38,7 +38,7 @@ Development rarely produces perfectly organized commits on the first pass.
 Use Commit Composer to turn working changes into clean, logical commits that make the work easier to understand and review.
 
 <figure>
-  <img src="/wp-content/uploads/GL-Graph-Compose.png" class="help-center-img img-bordered">
+  <img src="/wp-content/uploads/gl-graph-compose-01-v2@2x.png" class="help-center-img img-bordered">
 </figure>
 
 With Compose, you can:

diff --git a/gitlens/GL-Cloud-Patches.md b/gitlens/GL-Cloud-Patches.md
@@ -45,7 +45,7 @@ A Cloud Patch can be created from **Working Changes, Commits, Stashes, or Compar
 - The **Share** submenu in applicable GitLens views  
 
 <figure>
-  <img src="/wp-content/uploads/gl-create-cloud-patch-example.png" class="help-center-img img-bordered" alt="Creating a Cloud Patch from working changes in GitLens" />
+  <img src="/wp-content/uploads/gl-create-cloud-patch-example-01-v2@2x.png" class="help-center-img img-bordered" alt="Creating a Cloud Patch from working changes in GitLens" />
   <figcaption style="text-align: center; color: #888">Example of creating a Cloud Patch</figcaption>
 </figure>
 
@@ -80,7 +80,7 @@ Cloud Patches shared with you appear under **Shared with Me** in the Cloud Patch
 2. Select **Delete Cloud Patch…**  
 
 <figure>
-  <img src="/wp-content/uploads/gl-delete-cloud-patch.png" class="help-center-img img-bordered" alt="Deleting a Cloud Patch in GitLens" />
+  <img src="/wp-content/uploads/gl-delete-cloud-patch-01-v2@2x.png" class="help-center-img img-bordered" alt="Deleting a Cloud Patch in GitLens" />
   <figcaption style="text-align: center; color: #888">Deleting a Cloud Patch</figcaption>
 </figure>
 

diff --git a/gitlens/GL-Commit-Graph.md b/gitlens/GL-Commit-Graph.md
diff --git a/gitlens/GL-GK-AI.md b/gitlens/GL-GK-AI.md
@@ -20,12 +20,16 @@ GitLens integrates powerful AI capabilities across different subscription tiers,
 
 Generate clear, descriptive commit messages based on your code changes, saving time and ensuring consistency across your repository. The AI analyzes your staged changes and creates meaningful messages that accurately describe what you've modified.
 
+In addition to single commit messages, GitLens offers AI Generate Commits, which creates multiple logical commits from your working tree changes, and AI Rebase, which restructures an existing branch onto a target commit with AI-generated commits. Both commands include undo support and first-time confirmation dialogs.
+
 **How to access:**
 - From the Command Palette: `GitLens: Generate Commit Message with AI`
+- From the Command Palette: `GitLens: Generate Commits with AI` (creates multiple commits from working changes)
+- From the Command Palette: `GitLens: AI Rebase` (restructures branch commits)
 - From the SCM panel: Click the "Generate Commit Message" button
 - During the commit process: Look for the AI option in the commit interface
 
-<img src="/wp-content/uploads/GL-ai-commit-generate.png" class="help-center-img img-bordered">
+<img src="/wp-content/uploads/gl-ai-commit-generate-01-v2@2x.png" class="help-center-img img-bordered">
 
 ### AI Stash Messages`Pro`
 **Available in:** Pro, Advanced, and Business plans
@@ -37,7 +41,7 @@ Create intelligent descriptions for stashed changes, making it easier to find an
 - When creating a stash: Look for the AI option in the stash creation interface
 - From the stash view: Generate descriptions for existing stashes
 
-<img src="/wp-content/uploads/GL-ai-stash.png" class="help-center-img img-bordered">
+<img src="/wp-content/uploads/gl-ai-stash-01-v2@2x.png" class="help-center-img img-bordered">
 
 ### AI Commit Explain `Pro`
 **Available in:** Pro, Advanced, and Business plans
@@ -53,8 +57,9 @@ Understand the reasoning behind changes with AI-generated explanations of commit
 <img src="/wp-content/uploads/GL-ai-commit-explain.png" class="help-center-img img-bordered">
 
 ### AI Changes Explain `Preview`
-Gitkraken AI can also be used to generate summaries in Branches, Working changes, and Stashes.
+Gitkraken AI can also be used to generate summaries for Commits, Branches, Working Changes, and Stashes.
 
+What a specific commit introduced – ✨Explain Commit
 What changed across all commits in a branch – ✨Explain Branch
 What you’ve modified in your working directory – ✨Explain Working Changes
 What you’ve previously stashed – ✨Explain Stash
@@ -64,6 +69,7 @@ You’ll find ✨Explain options for commits, branches, stashes, and working cha
 - In the Commit Graph
 - Available as commands in the command palette
 - In many GitLens views: Commits, Branches, Stashes, Search & Compare, etc.
+- In editor blame hovers via the ✨Explain button
 
 ### AI Changelog Creation `Pro`
 **Available in:** Advanced and Business plans only
@@ -87,6 +93,43 @@ Open Pull Requests: Automatically generate clear PR titles and descriptions dire
 
 <img src="/wp-content/uploads/GL-ai-create-pr.png" class="help-center-img img-bordered">
 
+### AI Review `Pro`
+**Available in:** Pro, Advanced, and Business plans
+
+Review commits and working changes with AI-powered analysis that surfaces severity-tagged insights directly in the Commit Graph details panel. AI Review identifies potential issues, highlights notable patterns, and provides actionable feedback on your changes.
+
+**How to access:**
+- In the Commit Graph: Select a commit or working changes, then open the Review mode in the details panel
+- Customize review behavior with the `gitlens.ai.reviewChanges.customInstructions` setting
+
+You can configure separate AI models for different features (such as compose and review) to optimize for your preferred balance of speed and quality.
+
+### AI Auto Rebase `Pro`
+**Available in:** Pro, Advanced, and Business plans
+
+Automate rebasing with AI-assisted conflict resolution. AI Auto Rebase handles the end-to-end rebase process, automatically resolving conflicts based on a configurable confidence threshold. A rebase summary sheet shows what was resolved and how, and full undo support lets you revert the operation if needed.
+
+**How to access:**
+- From the Command Palette: `GitLens: AI Auto Rebase`
+- From the Commit Graph: Right-click a branch and select AI Auto Rebase
+
+**Key settings:**
+- `gitlens.ai.autoRebase.confidenceThreshold` — Set the minimum confidence level (0-1) for automatic conflict resolution
+- `gitlens.ai.resolveConflicts.customInstructions` — Provide custom instructions for how conflicts should be resolved
+
+### Compose and Recompose `Pro`
+**Available in:** Pro, Advanced, and Business plans
+
+Shape your commit history with AI-assisted commit crafting and branch restructuring.
+
+- **Compose**: Craft clean, logical commits from your uncommitted working changes using the Commit Composer in the Commit Graph
+- **Recompose**: Restructure existing commits on a branch using AI. Recompose commands let you reorganize, split, or combine commits for a clearer history
+
+**How to access:**
+- From the Commit Graph: Enter Compose mode to create commits from working changes
+- From the Commit Graph context menu: Right-click commits to access Recompose Branch, Recompose from Commit, or Recompose Selected Commits
+- From the Command Palette: `GitLens: Recompose Branch`
+
 ---
 ## AI Credit Allocation by Plan
 
@@ -106,6 +149,7 @@ GitLens offers flexibility in choosing your AI provider:
 3. **Custom Provider** (BYOK): Connect your own key from supported AI services
 >
 - New OpenAI and Google models
+- Mistral
 - Self-hosted Azure AI models
 - OpenAI-compatible API providers
 - Local Ollama models
@@ -128,6 +172,14 @@ To configure your AI provider:
 - **Credit usage monitoring**: Track your credit consumption for better allocation management
 - **Default AI mode**: Choose between concise or detailed outputs for each feature
 
+### AI File Exclusions
+
+Control which files are included in AI context to protect sensitive data:
+
+- **Ignore files**: GitLens respects `.aiignore`, `.cursorignore`, and `.aiexclude` files in your repository to exclude matching paths from AI prompts
+- **Exclude setting**: Use the `gitlens.ai.exclude.files` setting to define additional file patterns to exclude
+- Common files like lock files, minified assets, and build output directories are excluded by default
+
 ### Organization-Level Controls `Business`
 
 - **Enforceable AI rules**: Set organization-wide policies for AI usage

diff --git a/gitlens/GL-Integrations.md b/gitlens/GL-Integrations.md
@@ -14,7 +14,8 @@ GitLens supports a wide range of remote providers to enhance your Git workflow i
 - Gitea
 - Gerrit
 - Bitbucket (Cloud and Server)
-- Azure DevOps
+- Azure DevOps (Cloud and Server)
+- Linear (issue tracking)
 
 You can also define [custom remote providers or providers with custom domains](/gitlens/settings/#remote-provider-integration-settings).
 
@@ -42,6 +43,7 @@ You can use the following GitLens commands to interact with files, commits, and
 ### Files
 
 - **Open File from Remote** (`gitlens.openFileFromRemote`) — Open a local file by specifying a remote file URL
+- **Open Revision from Remote** (`gitlens.openRevisionFromRemote`) — Open a specific file revision from a remote URL, resolving the exact revision rather than the working copy
 - **Open File on Remote** (`gitlens.openFileOnRemote`) — Open the current file or revision on the remote
 - **Copy Remote File URL** (`gitlens.copyRemoteFileUrlToClipboard`) — Copy the URL of the current file or revision
 - **Open File on Remote From...** (`gitlens.openFileOnRemoteFrom`) — Open a file/revision from a specific branch or tag
@@ -85,15 +87,15 @@ To connect GitHub or GitLab to GitLens, you'll use your GitKraken account via th
 2. Go to the **GitKraken Account** section in the GitLens Activity Bar and choose **Integrations**.
 
 <figure>
-  <img src="/wp-content/uploads/gl-connect-remote-integration.png" srcset="/wp-content/uploads/gl-connect-remote-integration@2x.png" class="help-center-img img-bordered">
+  <img src="/wp-content/uploads/gl-connect-remote-integration-01-v2@2x.png" srcset="/wp-content/uploads/gl-connect-remote-integration-01-v2@2x.png" class="help-center-img img-bordered">
   <figcaption style="text-align:center; color:#888">Navigate to Integrations in the GitKraken Account menu</figcaption>
 </figure>
 
 3. If you’re not already signed in, log into your GitKraken account.
 4. Click **Connect with GitHub** or **Connect with GitLab** and complete the sign-in process.
 5. Select **Complete Setup** to return to Visual Studio Code and activate the integration.
 
-You can connect multiple integrations if needed.
+You can connect multiple integrations if needed, including multiple accounts for the same provider. For example, you can connect both a personal and a work GitHub account simultaneously. Use the integration settings to set a primary account, manage connections, and scope searches to a specific account.
 
 <figure>
   <img src="/wp-content/uploads/gl-connect-remote-integration-manager.png" class="help-center-img img-bordered">
@@ -104,6 +106,14 @@ You can connect multiple integrations if needed.
   <p>Community users are limited to basic functionality only.</p>
 </div>
 
+## GitHub PR Stacks `PRO`
+
+GitLens supports stacked pull request workflows on GitHub.com. When working with stacked PRs, GitLens shows stack information including the stack size, your PR's position within the stack, and the base ref. Merge operations are stack-aware, letting you choose to merge a single layer or the entire stack.
+
+PR stack details appear in the Commit Graph pull request sheet when viewing a PR that belongs to a stack.
+
+***
+
 ## GitHub Enterprise Server and GitLab Self-Managed Integration `PRO`
 
 GitLens Pro supports advanced integration with GitHub Enterprise Server and GitLab Self-Managed.
@@ -115,7 +125,7 @@ Once authenticated, GitLens enhances autolinks for these services in hover cards
 - Pull request and issue details directly in the Sidebar views
 
 <figure>
-  <img src="/wp-content/uploads/gitlab-github-integration.png" class="help-center-img img-bordered">
+  <img src="/wp-content/uploads/gl-gitlab-github-integration-01-v3@2x.png" class="help-center-img img-bordered">
   <figcaption style="text-align:center; color:#888">Enhanced hover cards with issue and PR metadata</figcaption>
 </figure>
 
@@ -141,7 +151,7 @@ Or for GitLab:
 5. Click <i class="fa-solid fa-plug"></i> **Connect to Remote**
 
 <figure>
-  <img src="/wp-content/uploads/gl-connect-to-remote-ghe.png" class="help-center-img img-bordered">
+  <img src="/wp-content/uploads/gl-connect-to-remote-ghe-01-v2@2x.png" class="help-center-img img-bordered">
   <figcaption style="text-align:center; color:#888">Use the plug icon to connect a self-managed remote</figcaption>
 </figure>
 
@@ -175,6 +185,6 @@ GitLens Pro supports integration with Jira Cloud via your GitKraken Account. Thi
 You can also configure this via the [Integration Settings](https://gitkraken.dev/settings/integrations?source=help_center&product=gitlens) in a browser.
 
 <figure>
-  <img src="/wp-content/uploads/gl-cloud-integrations.png" class="help-center-img img-bordered">
+  <img src="/wp-content/uploads/gl-cloud-integrations-01-v3@2x.png" class="help-center-img img-bordered">
   <figcaption style="text-align:center; color:#888">Jira integration via GitLens Cloud Integrations panel</figcaption>
 </figure>
diff --git a/gitlens/GL-Parallel-dev-workflow.md b/gitlens/GL-Parallel-dev-workflow.md
@@ -27,7 +27,7 @@ See branches, worktrees, working changes, commits, HEAD, upstream, merge targets
 Multi-worktree WIP also surfaces working changes across your worktrees, so active work stays visible even when you aren’t currently working in that worktree.
 
 <figure>
-  <img src="/wp-content/uploads/GL-Worktrees-multi-wip.png" class="help-center-img img-bordered">
+  <img src="/wp-content/uploads/gl-worktrees-multi-wip-01-v2@2x.png" class="help-center-img img-bordered">
 </figure>
 
 ## 2. Monitor Agent Work
@@ -42,7 +42,7 @@ From the Commit Graph, you can:
 - Resume active or previous sessions with the surrounding Git context intact
 
 <figure>
-  <img src="/wp-content/uploads/GL-Agent-working.png" class="help-center-img img-bordered">
+  <img src="/wp-content/uploads/gl-agent-working-01-v2@2x.png" class="help-center-img img-bordered">
 </figure>
 
 <figure>

diff --git a/gitlens/GL-Visual-File-History.md b/gitlens/GL-Visual-File-History.md
@@ -8,26 +8,32 @@ taxonomy:
 
 <kbd>Last updated: August 2025</kbd>
 
-## Visual File History
+## Visual History
 
-The GitLens **Visual File History** shows how a file has evolved, including when changes were made, the size of those changes, and who made them.
+The GitLens **Visual History** (formerly Visual File History) shows how your code has evolved, including when changes were made, the size of those changes, and who made them. Visual History supports multiple scopes: view the history of a single file, a folder, an entire repository, or a specific branch.
 
 ---
 
-### Open Visual File History
+### Open Visual History
 
-You can open the Visual File History view in two ways:
+You can open the Visual History view in two ways:
 
 1. From the **GitLens Inspect** sidebar.  
-   - Open the sidebar, then select the **Visual File History** view.  
+   - Open the sidebar, then select the **Visual History** view.  
 2. From the **Command Palette**:  
    - macOS: <kbd>Cmd</kbd> + <kbd>Shift</kbd> + <kbd>P</kbd>  
    - Windows/Linux: <kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>P</kbd>  
-   - Search for **GitLens: Show Visual File History View**.
+   - Search for **GitLens: Show Visual History View**.
+
+### Scope Options
+
+- **File or Folder**: Visualize the history of a specific file or folder
+- **Repository**: See the full history of your entire repository
+- **Branch**: Slice history by branch to focus on a specific line of work
 
 <figure>
-  <img src="/wp-content/uploads/visual-file-history.png" class="help-center-img img-bordered" alt="Visual File History view in GitLens showing commits plotted by author and time" />
-  <figcaption style="text-align: center; color: #888">Visual File History view</figcaption>
+  <img src="/wp-content/uploads/gl-visual-file-history-01-v2@2x.png" class="help-center-img img-bordered" alt="Visual History view in GitLens showing commits plotted by author and time" />
+  <figcaption style="text-align: center; color: #888">Visual History view</figcaption>
 </figure>
 
 ---

diff --git a/gitlens/GL-Workflow-Cleanup-prepare-for-review.md b/gitlens/GL-Workflow-Cleanup-prepare-for-review.md
@@ -71,6 +71,8 @@ GitLens uses Git intelligence to help you ship work that is easier to review, re
 
 - [Launchpad (PR and review awareness)](https://help.gitkraken.com/gitlens/gitlens-features/#launchpad-pro)
 
+- [Start Review](/gitlens/gl-accelerate-pr-reviews/#start-review-pro) (quick-pick wizard to select a PR, check out branch or worktree, and optionally open AI review chat)
+
 - Worktrees (parallel branch workflows)
 
 - Commit Graph context menu actions

diff --git a/gitlens/GL-Workspaces.md b/gitlens/GL-Workspaces.md
@@ -108,7 +108,7 @@ Visual indicators in Workspaces help you quickly understand their status. For ex
 - A **green Workspace** with an **O** symbol indicates it is open in your current window.
 
 <figure>
-  <img src="/wp-content/uploads/gl-workspace-indicators.png" class="help-center-img img-bordered">
+  <img src="/wp-content/uploads/gl-workspace-indicators-01-v2@2x.png" class="help-center-img img-bordered">
   <figcaption style="text-align: center; color: #888">Workspace status indicators</figcaption>
 </figure>
 

diff --git a/gitlens/GL-Worktrees.md b/gitlens/GL-Worktrees.md
@@ -11,7 +11,7 @@ taxonomy:
 ## Worktrees View
 
 <figure>
-  <img src="/wp-content/uploads/worktrees-view.png" class="help-center-img img-bordered" alt="GitLens Worktrees view in VS Code showing multiple branches" />
+  <img src="/wp-content/uploads/gl-worktrees-view-01-v2@2x.png" class="help-center-img img-bordered" alt="GitLens Worktrees view in VS Code showing multiple branches" />
   <figcaption style="text-align: center; color: #888">GitLens Worktrees view</figcaption>
 </figure>
 

diff --git a/gitlens/GL-accelerate-pr-reviews.md b/gitlens/GL-accelerate-pr-reviews.md
@@ -48,6 +48,20 @@ To start reviewing:
 </figure>
 
 
+## Start Review `PRO`
+
+The **Start Review** command provides a quick-pick wizard for jumping into a pull request review. It walks you through selecting an integration, picking a PR, and choosing how to check it out (as a branch or in a new worktree). You can also optionally open an AI chat with a review prompt to assist your review.
+
+To use Start Review:
+
+1. Open the Command Palette (`Ctrl+Shift+P` or `Cmd+Shift+P`).
+2. Run: `GitLens: Start Review`.
+3. Select your integration and pull request, then choose your checkout method.
+
+<figure class='callout callout--warning'>
+  <p>This feature is available with a GitLens Pro subscription or higher.</p>
+</figure>
+
 ## Worktrees
 
 Worktrees let you check out multiple branches simultaneously in separate working directories. This means you don’t need to commit or stash in-progress changes before switching to another branch—perfect for reviewing pull requests without disrupting your workflow.