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:
- 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.
- Setting
gitlens.gitkraken.mcp.autoEnabled: false in user settings does not prevent gk mcp from being spawned.
Steps to reproduce:
- Install GitLens v17.12.2 on macOS (Apple Silicon, SIP enabled)
- Open any git repository workspace in VS Code
- Run:
while true; do ls "$TMPDIR" | grep -c gkinstall; sleep 10; done
- 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
GitLens v17.12.2 spawns multiple
gk mcp --host=gemini --source=gitlens --scheme=vscodeprocesses on every VS Code workspace open. Each process repeatedly downloadsgk_core_3.1.65_darwin_arm64.zipto a fresh temp directory and extractsmcp_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:
gkbinary extracts to a new temp dir on every invocation instead of a stable cached path, causing unbounded Gatekeeper re-verification and disk consumption.gitlens.gitkraken.mcp.autoEnabled: falsein user settings does not preventgk mcpfrom being spawned.Steps to reproduce:
while true; do ls "$TMPDIR" | grep -c gkinstall; sleep 10; doneConfirmed via
fs_usage:Workaround: Rename
~/Library/Application Support/Code/User/globalStorage/eamodio.gitlens/gktogk.disabledEnvironment:
gk_coreversion being downloaded: 3.1.65