It got confused and hard reset git

[VividLemon]

Type: Bug

It just git reset hard HEAD with a ~50 files in staging area. In addition to just getting the instructions wrong and not just adding ! in these TS files. It got too confused with ~200 instances of needing to fix, kept running, and decided it was better to just reset to head, ignoring staging. It should probably not reset without checking staging first

Extension version: 0.36.2
VS Code version: Code 1.108.2 (c9d7799, 2026-01-21T13:52:09.270Z)
OS version: Linux x64 6.17.9-76061709-generic
Modes:

System Info

Item	Value
CPUs	AMD Ryzen 7 7800X3D 8-Core Processor (16 x 4177)
GPU Status	2d_canvas: enabled 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: disabled_software vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: disabled_off webnn: disabled_off
Load (avg)	2, 2, 2
Memory (System)	30.50GB (16.02GB free)
Process Argv	--new-window /home/issayah/Documents/Apps/bootstrap-vue-next --crash-reporter-id 0e433481-fb82-40a8-aa58-b4535226fe12
Screen Reader	no
VM	0%
DESKTOP_SESSION	pop
XDG_CURRENT_DESKTOP	pop:GNOME
XDG_SESSION_DESKTOP	pop
XDG_SESSION_TYPE	x11

A/B Experiments

vsliv368:30146709
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythonrdcb7:31342333
6518g693:31436602
aj953862:31281341
6abeh943:31336334
cloudbuttont:31379625
aihoversummaries_t:31453032
3efgi100_wstrepl:31403338
use-responses-api:31390855
anonusage:31403420
je187915:31401254
ec5jj548:31422691
cmp-ext-treat:31426748
cp_cls_t_966_ss:31454198
c0683394:31419495
ge8j1254_inline_auto_hint_haiku:31427726
nes-autoexp-off:31446584
a5gib710:31434435
38bie571_auto:31426784
rename_enabled:31436409
7a04d226_do_not_restore_last_panel_session:31438103
anthropic_thinking_t:31432745
h0hdh950:31428394
cp_cls_c_1081:31443829
copilot-nes-oct-trt:31432596
ia-use-proxy-models-svc:31452481
nes-jump-on-with-edit:31444032
nes-slash-models-on:31441832
nes-set-to-on:31441941
a43f0576c:31442824
ts_provider_disabled:31446105
nes-conv-2-2:31447849

[VividLemon]

This is also somewhat my fault because it kept getting confused after receiving so many errors, that I gave it autonomy to run as many scripts as it needed.

[lszomoru]

Thanks for filing this issue. Reading through it, it is not clear to me what it would be expected.
Without the prompt, model information, as well as the Chat logs it is very difficult for us to take action.

[vs-code-engineering]

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.

For Copilot Issues, be sure to visit our Copilot-specific guidelines page for details on the necessary information.

Happy Coding!

[VividLemon]

Thanks for filing this issue. Reading through it, it is not clear to me what it would be expected. Without the prompt, model information, as well as the Chat logs it is very difficult for us to take action.

The core of it is that the agent should take into account existing changes before it started running and before it attempts to take any destructive actions like git reset --hard. The agents thought was "Oh what I did failed, let me revert my changes and try again", which caused it to destroy the git staging environment, which existed before it started running.