Type: Bug
Sonnet 4 is still having issues with getting stuck during edits.
There seems to be two cases where it gets stuck:
- Applying edits gets stuck at 98-100% and never continues.
In these cases the edit is actually applied, it just seems the agent is not picking up a callback about this being done.
- Generating edits, never goes to apply even and just leaves it like this for inifity or until you stop it. This is usally triggered after 1. has already happened in the same session.
You can break it out of these problems by asking it to actively do something else or force an action that is not ending in the same edit. You can also tell it to use other editing "tools" or mind the syntax as it keeps breaking edits, this usually makes it work for a little bit again until the amnesia kicks in. This seems to happen more frequently when we are obviously routed to dumber/quantized models instead of getting the real thing...
Either way this is a huge waste of our request quotas as it can take hours to get a single little thing right with continious reprompting. This issue comounds on the other issues that is already completely draining our quotas without getting a anything that can actually be used out of the models.
Extension version: 0.29.2025070703
VS Code version: Code - Insiders 1.102.0-insider (96f1890, 2025-07-04T15:15:02.963Z)
OS version: Windows_NT x64 10.0.26100
Modes:
System Info
| Item |
Value |
| CPUs |
AMD Ryzen 5 5600X 6-Core Processor (12 x 3700) |
| GPU Status |
2d_canvas: enabled canvas_oop_rasterization: enabled_on 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 video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off |
| Load (avg) |
undefined |
| Memory (System) |
31.93GB (3.17GB free) |
| Process Argv |
--crash-reporter-id 6184e59b-eb56-4178-9e91-ec311e8e4aee |
| Screen Reader |
no |
| VM |
0% |
Type: Bug
Sonnet 4 is still having issues with getting stuck during edits.
There seems to be two cases where it gets stuck:
In these cases the edit is actually applied, it just seems the agent is not picking up a callback about this being done.
You can break it out of these problems by asking it to actively do something else or force an action that is not ending in the same edit. You can also tell it to use other editing "tools" or mind the syntax as it keeps breaking edits, this usually makes it work for a little bit again until the amnesia kicks in. This seems to happen more frequently when we are obviously routed to dumber/quantized models instead of getting the real thing...
Either way this is a huge waste of our request quotas as it can take hours to get a single little thing right with continious reprompting. This issue comounds on the other issues that is already completely draining our quotas without getting a anything that can actually be used out of the models.
Extension version: 0.29.2025070703
VS Code version: Code - Insiders 1.102.0-insider (96f1890, 2025-07-04T15:15:02.963Z)
OS version: Windows_NT x64 10.0.26100
Modes:
System Info
canvas_oop_rasterization: enabled_on
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
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off