Skip to content

gk mcp process floods macOS temp directory with gkinstall dirs (hundreds of GB), ignores autoEnabled: false setting #5249

Description

@egarcia74

GitLens v17.12.2 spawns multiple gk mcp --host=gemini --source=gitlens --scheme=vscode processes on every VS Code workspace open. Each process repeatedly downloads gk_core_3.1.65_darwin_arm64.zip to a fresh temp directory and extracts mcp_resources/tools/git_overview.bundle.js. macOS Gatekeeper re-verifies the extracted binary on every invocation because it lands in a new path each time, and the directories are never cleaned up.

Rate: ~4-5 new directories per 10 seconds, 44 MB each. Accumulated 386 GB overnight.

Two bugs:

  1. The gk binary extracts to a new temp dir on every invocation instead of a stable cached path, causing unbounded Gatekeeper re-verification and disk consumption.
  2. Setting gitlens.gitkraken.mcp.autoEnabled: false in user settings does not prevent gk mcp from being spawned.

Steps to reproduce:

  1. Install GitLens v17.12.2 on macOS (Apple Silicon, SIP enabled)
  2. Open any git repository workspace in VS Code
  3. Run: while true; do ls "$TMPDIR" | grep -c gkinstall; sleep 10; done
  4. Observe counter climbing continuously

Confirmed via fs_usage:

gk  open   gkinstall.../gk_core_3.1.65_darwin_arm64.zip
gk  mkdir  gkinstall.../mcp_resources/
gk  open   gkinstall.../mcp_resources/tools/git_overview.bundle.js

Workaround: Rename ~/Library/Application Support/Code/User/globalStorage/eamodio.gitlens/gk to gk.disabled

Environment:

  • GitLens: 17.12.2
  • VS Code: 1.120.0
  • macOS: Apple Silicon, SIP enabled
  • gk_core version being downloaded: 3.1.65

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions