Unresponsive after edit using GPT-5/Swift code/qdrant, stuck on "Save" button and need to "Reopen"

[jab-r]

App Version

3.25.10

API Provider

OpenAI

Model Used

GPT-5

Roo Code Task Links (Optional)

No response

🔁 Steps to Reproduce

1. MacOS, 3.25.10, GPT-5/small/medium, indexing w Qdrant
2. normal prompt in Code mode to cause an edit
3. when the "Save" option appears, the entire VSCode UI freezes and the "Save" button cannot be clicked
4. When the modal to "Reopen Window" appears, I can reload the window and restart the task

💥 Outcome Summary

Expect to be able to Save file edits, but the VSCode UI locks and the Window needs to be reloaded by VSCode

📄 Relevant Logs or Errors (Optional)

[roomote]

I'm here to help out the maintainers and am going to investigate this VSCode UI freezing issue when the Save button appears after edits in Code mode. I'll work on identifying the root cause and implementing a fix. 🔍

[roomote]

I've created a pull request to fix this issue: #6871

The fix wraps all VSCode save/open dialog calls in a non-blocking utility that uses setImmediate to defer the dialog to the next event loop iteration. This prevents the UI thread from being blocked and should resolve the freezing issue you're experiencing.

The changes have been tested with:

• ✅ All linting checks passed
• ✅ All type checks passed
• 🔄 CI checks are currently running

The solution affects all save dialog operations in the extension to ensure consistent behavior across the codebase.

[jab-r]

I'm back using anthropic 4, and it is working now though i notice that there can be a delay before the "Save" button becomes active ... I think this must be related to the Swift parser ... but claude does work

…

On Sat, Aug 9, 2025 at 9:40 AM roomote[bot] ***@***.***> wrote: *roomote[bot]* left a comment (RooCodeInc/Roo-Code#6870) <#6870 (comment)> I've created a pull request to fix this issue: #6871 <#6871> The fix wraps all VSCode save/open dialog calls in a non-blocking utility that uses setImmediate to defer the dialog to the next event loop iteration. This prevents the UI thread from being blocked and should resolve the freezing issue you're experiencing. The changes have been tested with: - ✅ All linting checks passed - ✅ All type checks passed - 🔄 CI checks are currently running The solution affects all save dialog operations in the extension to ensure consistent behavior across the codebase. — Reply to this email directly, view it on GitHub <#6870 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEHN3KRVWQGPM4K4IXBWPFD3MX25NAVCNFSM6AAAAACDP5OLHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNZQG4ZDMMRQHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[daniel-lxs]

Hey @jab-r I'll close this issue for now since it seems that is not related to Roo Code, Let me know if you have any questions!