Issue Description
After the agent creates and updates files, and I click accept each file change or wait for multiple changes and accept them, the changes are accepted on the first initiation or when I click the accept button on the first agent run. However, if I let the agent run and all the files are modified, the accept button doesn’t work as expected. It remains persistent even after multiple clicks.
Steps to Reproduce
Assign the agent a task and observe it modifying one or two files before hitting “Accept.” Allow the agent to continue with all the tasks until they’re completed. Try to accept all file changes. You may notice that the “Accept” button remains persistent and doesn’t disappear.
Expected Behavior
Regardless of whether a single file is modified and you hit Accept, it will accept the changes. If multiple files are modified, you can accept the changes for multiple files. Alternatively, if you decide to wait until all tasks are completed and then hit Accept, all file changes will be accepted.
Actual Behavior
The actual behavior of the button seems inconsistent, possibly due to a UI state bug. When the button is clicked for files that are modified, it does not function as intended for multiple files that are modified within a single subsequent request or task from the agents.
Screenshots / Screen Recordings
Operating System
Apple M4 Pro
15.6.1 (24G90)
Current Qoder Version (Menu → About Qoder → Copy)
Version: 0.1.15
VSCode Version: 1.100.0
Commit: dfb66331a59270f1c56eae9e5d252fc321af0cbc
Date: 2025-08-21T04:50:37.178Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0