Roo Code fails to open diff editor in specific VS Code contexts

[sstublic]

App Version

3.19.1

API Provider

Not Applicable / Other

Model Used

N/A

🔁 Steps to Reproduce

Using Windows 11, VS Code 1.100.2

1. Open VSCode
2. Move Roo into editor window
3. Move Roo editor window onto another monitor (this spawns a child VSCode or something)
4. Lock that window to prevent Roo opening diff editor in this editor instance
5. Attempt to do any change that uses diff editor
6. Roo will open correct diff editor in the original VSCode editor
7. Roo will wait for a specific time and not detect that diff has been correctly opened AND fail with error message "Failed to open diff editor, please try again..."

This flow worked some time ago (a month?) without any problems.
Lately it has increasingly started to fail, to a point where it's not usable anymore. Maybe it never works now, didn't pinpoint this because diff editor is not always used.

The whole setup is logical and very convenient for multi-monitor setup. I want to be able to see and follow Roo process on one screen (including Approve prompts) and actual changes on the other.

Screenshot of both screens:

This NEVER happens if I keep Roo window on the same monitor (VSCode instance) as the diff editor.

💥 Outcome Summary

Expected diff editor to work in described setup.

📄 Relevant Logs or Errors (Optional)

More detailed error message from conversation:


[apply_diff for 'Program.cs'] Result:

The tool execution failed with the following error:
<error>
Error applying diff: {"name":"Error","message":"Failed to open diff editor, please try again...","stack":"Error: Failed to open diff editor, please try again...\n    at Timeout._onTimeout (c:\\Users\\XXX\\.vscode\\extensions\\rooveterinaryinc.roo-cline-3.19.1\\dist\\extension.js:3138:2294)\n    at listOnTimeout (node:internal/timers:581:17)\n    at processTimers (node:internal/timers:519:7)"}
</error>

[dosubot]

Hi @sstublic! I'm Dosu and I’m helping the Roo-Code team.

I could not find any documentation or discussions specifically addressing Roo Code failing to open the diff editor in multi-monitor setups or the error message "Failed to open diff editor, please try again..." in your described scenario. The documentation does mention that Roo Code introduced multi-window support in version 3.8.0, which may be related to your workflow, but there are no details about issues or troubleshooting steps for diff editor failures in multi-monitor contexts or recent changes that could have caused this regression [source].

If you haven't already, you might try updating both Roo Code and VS Code to their latest versions, as well as testing with different window arrangements or resetting Roo's settings. However, based on available documentation, there are no official fixes or workarounds published for this specific issue.

To reply, just mention my name @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[WhiteyDude]

I can replicate this on macOS 15.5 running vscode 1.100.2 and roo 3.19.2.

I also run roo on a second screen and have "locked the group" of tabs on the window with roo in it, otherwise it often will open the diff in that window. This was indeed working better in an earlier version. Annoyingly it means sending a new API request for the LLM to attempt to edit the file again, resulting in a fair bit of wasted cost over a day of work.

[daniel-lxs]

Might be related to #2360

[sstublic]

Might be related to #2360

I have found that issue and tested multiple times with editing markdown files AND non-markdown files. It made no difference.

From what I understand that issue describes malfunction when editing markdown files explicitly, so this should be something different.

[daniel-lxs]

Hey @Mnehmos, thank you for your report, would you like to work on this issue?