github / github/vscode-github-actions
Stuck stating tools at the beginning of a new session
- Lingua principale
- TypeScript
- Stelle
- 660
- Fork
- 213
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
Type: Performance Issue
so I provide system prompt and it got stuck saying "starting tools" or soemething like that
Extension version: 0.31.0
VS Code version: Code 1.111.0 (ce099c1ed25d9eb3076c11e4a280f3eb52b4fbeb, 2026-03-06T23:06:10Z)
OS version: Windows_NT x64 10.0.19045
Modes:
System Info
|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i3-6100T CPU @ 3.20GHz (4 x 3192)|
|GPU Status|2d_canvas: enabled
GPU0: VENDOR= 0x8086, DEVICE=0x1912 [Intel(R) HD Graphics 530], DRIVER_VENDOR=Intel, DRIVER_VERSION=26.20.100.7156 *ACTIVE*
GPU1: VENDOR= 0x1414, DEVICE=0x008c [Microsoft Basic Render Driver], DRIVER_VERSION=10.0.19041.5794
Machine model name:
Machine model version:
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
trees_in_viz: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|7.88GB (1.43GB free)|
|Process Argv|--folder-uri file:///c%3A/code/ForeSight --crash-reporter-id 2c2e99a6-4d7c-471a-a430-b375d217533c|
|Screen Reader|no|
|VM|0%|
Process Info
```
CPU % Mem MB PID Process
0 107 21656 code
0 126 4832 gpu-process
0 279 7192 window [1] (foresight_system_prompt.md - ForeSight - Visual Studio Code)
0 77 11960 utility-process
0 98 12724 pty-host
0 8 10372 conpty-agent
0 52 11780 C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -noexit -command "try { . \"c:\Users\howardon\AppData\Local\Programs\Microsoft VS Code\ce099c1ed2\resources\app\out\vs\workbench\contrib\terminal\common\scripts\shellIntegration.ps1\" } catch {}"
0 85 17608 file-watcher [1]
0 28 18332 crashpad-handler
0 128 18764 shared-process
0 44 19620 utility-network-service
0 187 21920 extension-host [1]
0 115 800 electron-nodejs (bundle.js)
0 8 7860 c:\Users\howardon\.vscode\extensions\ms-python.vscode-python-envs-1.22.0-win32-x64\python-env-tools\bin\pet.exe server
0 7 14156 C:\WINDOWS\system32\conhost.exe 0x4
0 88 20320 "C:\Users\howardon\AppData\Local\Programs\Microsoft VS Code\Code.exe" "c:\Users\howardon\AppData\Local\Programs\Microsoft VS Code\ce099c1ed2\resources\app\extensions\markdown-language-features\dist\serverWorkerMain" --node-ipc --clientProcessId=21920
```
Workspace Info
```
| Window (foresight_system_prompt.md - ForeSight - Visual Studio Code)
| Folder (ForeSight): 2 files
| File types: md(2)
| Conf files:;
```
A/B Experiments
```
vsliv368cf:30146710
vswsl492cf:30256860
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythonrdcb7:31342333
6518g693:31463988
aj953862:31281341
6abeh943:31336334
envsactivate1:31464700
cloudbuttont:31379625
aihoversummaries_f:31469309
42190218_ostrepl:31403339
use-responses-api:31390855
anonusage:31403420
ddidtcf:31399634
je187915:31401254
ec5jj548:31422691
cp_cls_t_966_ss:31454198
4je02754:31466945
ge8j1254_inline_auto_hint_haiku:31427726
nes-autoexp-off:31446584
38bie571_auto:31426784
7a04d226_do_not_restore_last_panel_session:31438103
cp_cls_c_1081:31454833
ia-use-proxy-models-svc:31452481
a43f0575b:31442825
e9c30283:31461165
test_treatment2:31471001
nes-conv-2-3:31474331
control_6dc23131:31467998
idci7584:31464702
edit_mode_hidden:31461530
864ei723_large_tool_results_to_disk:31460878
showingstats:31471631
55364912:31471672
chat:31457767
8hig5102:31473806
grok_6ec3c140:31477193
nes-rcnt-ctrl:31471618
bg_compact_c:31476251
cpptoolson-v2:31475363
f0268191:31471593
noaffordance1:31474146
db0gd219:31473911
newsessionicon:31473927
nes-notsn-1:31475122
```
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Non sono indicati file, test o punti di ingresso. Inizia riproducendo il flusso di una nuova sessione con il prompt di sistema segnalato nelle versioni elencate dell’estensione e di VS Code, quindi traccia il punto in cui l’UI rimane su “starting tools”. Il lavoro è completato quando lo stato bloccato è spiegato e un test di regressione verificato o una verifica della riproduzione conferma che non si verifica più.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- typescript, vscode
- Ambito
- devtools, performance
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100