Expands connectivity with CLI to support new MCP tools

[d13]

Changes

This PR adds Model Context Protocol (MCP) support to enable communication between the GitLens extension and the GitLens CLI.

New CLI integration features

• Insiders Edition Support: Adds gitlens.gitkraken.cli.insiders.enabled setting to use experimental insiders builds
• IPC Discovery:
  • Bundled version - Passes --gitlens-url parameter in MCP server definitions
  • Non-bundled version - Creates discovery files in temp directory for IDE clone support
• New CLI IPC Commands:
  • compose - Opens commit composer
  • start-review - Starts reviewing a PR
  • start-work - Starts work on an issue
  • get-launchpad-item - Retrieves specific launchpad item
  • get-launchpad-list - Lists all launchpad items
  • ping - Health check endpoint

New GitLens core changes

• Start Review Command (gitlens.startReview):

  • Review PRs with AI assistance or from the Command Palette (GitLens: Start Review)
  • Choose reviewable PRs or search by PR URL
  • Creates and opens worktrees for reviewing PRs
  • Prompts AI chat to begin review after opening worktree
  • Supports pre-selecting PRs by URL for programmatic usage

• Enhanced Start Work Command (new optional args):

  • Pass a pre-selected issue by URL
  • Supports "use defaults" mode for non-interactive usage
  • Prompts AI chat to start work after opening worktree

• Chat Integration (gitlens.sendToChat):

  • Unified interface for sending prompts to various AI chat systems
  • Supports VS Code Copilot Chat, Cursor, Windsurf, Kiro, and Trae
  • Handles clipboard-based prompt injection for IDEs without direct API

Local Setup

In settings.json, add:

• "gitlens.gitkraken.cli.integration.enabled": true
• "gitlens.gitkraken.cli.insiders.enabled": true

Risk

New CLI integration features - low

Currently, if the gitlens.gitkraken.cli.integration.enabled setting is not applied, no new features will appear.

New GitLens core changes - medium

• gitlens.startReview is an additive command, which we could be hidden from the command palette and still expose for the CLI to call.
• Start Work Command had no changes to the existing usage of Start Work flow, but major refactoring was done to accept optional args to avoid some interactive steps when called programmatically, so there is potential for regression.

---

Resolves issues: #4797 #4907 #4908 #4909 #4910 #4912

[augmentcode]

🤖 Augment PR Summary

Summary: This PR expands GitLens���������������������� connectivity with the GitKraken CLI by adding IPC and MCP-based integrations, enabling the CLI (and MCP tools) to trigger GitLens workflows.

Changes:

• Adds a new gitlens.startReview command (Quick Wizard routing + contributed command palette entry)
• Extends GK CLI IPC commands to support compose, start-review, start-work, and Launchpad data retrieval (get-launchpad-item/get-launchpad-list) plus a ping endpoint
• Introduces a unified gitlens.sendToChat command and host-specific chat openers (VS Code/Copilot Chat, Cursor, Windsurf, Kiro, Trae) with clipboard-based injection fallbacks
• Adds Start Review + Start Work prompt templates and supporting AI prompt resolution overloads
• Adds deeplink state/context for Start Review / Start Work and persists pending deeplink payloads in secrets
• Adds CLI “insiders” support via gitlens.gitkraken.cli.insiders.enabled and telemetry fields to track insiders installs
• Implements IPC discovery-file creation in temp storage for non-bundled CLI discovery scenarios

Technical Notes: The MCP provider now injects a --gitlens-url=... argument based on the runtime IPC address, and a new event bus signal (gk:cli:ipc:started) triggers definition refresh when the IPC server is ready.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 7 suggestions posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

Review completed. 2 suggestions posted.

Comment augment review to trigger a new review at any time.