Add the option to accept or decline the proposed changes of the ai.

[taengaaa]

It should be possible for users to accept or decline the proposed changes made by the AI. Additionally, users should be able to specify which files or parts of the code should remain unchanged. Currently, the AI sometimes overwrites functional code with replacements that are not desired, leading to loss of stable functionality.

Key Requirements:

Granular Control: Users should have the ability to selectively approve or reject changes at a file or even a line level.

File-Level Locking: Users should be able to mark specific files or segments as "do not modify" to protect critical or well-functioning parts of the code.

Change Review Interface: Introduce a review mechanism where users can inspect proposed changes and provide feedback or approval.

Rationale:

The current approach can lead to unwanted modifications, especially when the AI suggests updates for stable parts of the code. By giving users more granular control, we ensure that only the necessary changes are integrated, reducing the risk of breaking existing functionality.

This feature would significantly improve developer trust and control over AI-generated changes, leading to more efficient collaboration between users and the AI system.

Possible Implementation Ideas:

A dedicated UI for reviewing and approving changes similar to Cline.

A "lock" feature that prevents specific files from being altered by the AI.

Integration with version control systems to provide an additional layer of safety before applying changes.

[mbhvl]

Yes this would be excellent. Bolt often gets over-enthusiastic on writing new code-files instead of editing existing code-files. You can end up with simiarly named files all trying to do the same thing: DialogView.ts, DialogWindow.ts, ViewDialog.ts, ViewDialog.tsx - four different versions of the same thing. You then have to go through a needless & token-expensive Merge process.
So a Git Diff would be really useful: accept the proposed changes only once you've checked them.

Also locking down Bolt to edit only certain files can fail because it might create a new file and then be locked out from editing it. If "Target All" could apply at folder-level, not file-level, this would be realy useful - maybe "Target Folder" (to allow new files to be created & edited) alongside "Traget Existing Files" (which does not).