Microsoft/vscode

Git - changes tool should avoid context blowout

Open

#276,413 建立於 2025年11月10日

在 GitHub 查看
 (5 留言) (0 反應) (1 負責人)TypeScript (74,848 star) (10,221 fork)batch import
feature-requestgithelp wanted

描述

Type: Bug

  1. Ask agent to "review #changes" in a large changeset
  2. 🐛 #changes tool calls adds 50k tokens to a conversation, causing quick summarization cycle

Expected: Make #changes smarter to NOT include ALL details when a changeset is massive, but allow the agent to progressively disclose context.

Without changes, the agent will usually list changed files first and then do smarter exploration of what changed.

VS Code version: Code - Insiders 1.106.0-insider (Universal) (48cdf17f0e856e1daca2ad2747814085a2453df0, 2025-11-07T21:38:27.361Z) OS version: Darwin arm64 24.6.0 Modes:

Item Value
CPUs Apple M4 Pro (14 x 2400)
GPU Status 2d_canvas: enableddirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: enabled_ontrees_in_viz: disabled_offvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off
Load (avg) 5, 5, 6
Memory (System) 24.00GB (0.10GB free)
Process Argv --log trace --enable-proposed-api digitarald.agent-memory --crash-reporter-id 9b206efe-c338-4f34-baff-2aab1c48a82e
Screen Reader no
VM 0%

貢獻者指南

技術棧
typescriptjavascript
領域
developer experienceperformance
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
TypeScriptVS Code extension API
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50
研究方向
Investigate the implementation of the #changes tool in the VS Code git extension (likely in extensions/git/src/). The current behavior fetches the full diff, causing large token counts. Consider adding a heuristic to limit the diff size or provide a summary of changed files first, as suggested in the issue. Look at how the tool retrieves and formats the diff, and explore options for progressive disclosure.
Git - changes tool should avoid context blowout · Microsoft/vscode#276413 | Good First Issue