[BUG] Roo code won't edit any files - Error apply patch

[tobico]

Problem (one or two sentences)

When roo code tries to edit a file, I get this error message:

Date/time: 2026-02-10T01:08:32.512Z
Extension version: 3.47.3
Provider: openai-native
Model: gpt-5-mini

Error apply patch:
Tab close: Invalid tab not found!

Context (who is affected and when)

I'm running roo code in code mode and asking it to modify a specific file which is attached to the context. The result from the AI provider includes a call to edit a file.

Reproduction steps

1. Environment is VS Code on Windows 11, connected to WSL with NixOS.
2. Run a code request with a file attached to the context, and ask for changes to the file.

Expected result

Roo code should edit the file, or ask me to approve an edit

Actual result

Error message is shown, the edit is not done.

Variations tried (optional)

No response

App Version

3.47.3

API Provider (optional)

OpenAI

Model Used (optional)

N/A

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote]

I've analyzed this issue and here's my proposed implementation plan:

Root Cause

The error Error apply patch: Tab close: Invalid tab not found! originates from DiffViewProvider.open() in src/integrations/editor/DiffViewProvider.ts (line 101). When preparing to show a diff view, the code tries to close any existing editor tab for the file being edited:

for (const tab of tabs) {
    if (!tab.isDirty) {
        await vscode.window.tabGroups.close(tab)  // <-- unhandled error
    }
    this.documentWasOpen = true
}

The VS Code API tabGroups.close(tab) throws "Invalid tab not found!" when the tab has already been closed or become invalid between the time it was found in the filter and when close() is called. This is a race condition that is more likely in remote environments like WSL.

The unhandled error propagates up through ApplyPatchTool.execute() to the outer catch block, which formats it as "Error apply patch: Tab close: Invalid tab not found!" and blocks the entire edit operation.

Notably, the same file already has proper error handling for tab closing in its closeAllDiffViews() method, which swallows close failures gracefully. The open() method just missed the same treatment.

Proposed Fix

1. src/integrations/editor/DiffViewProvider.ts - Wrap the tabGroups.close(tab) call in open() with a try-catch block that logs the error but allows execution to continue (matching the pattern already used in closeAllDiffViews()).

2. src/integrations/misc/open-file.ts - Apply the same defensive fix to the tabGroups.close(existingTab) call on line 130, which has the same vulnerability.

3. Add/update tests to verify the error handling behavior.

This approach will fix the blocking error while preserving the intended behavior (closing existing tabs before opening the diff view). If a tab close fails, the diff view will still open and function correctly.

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[hannesrudolph]

Does this error happen intermittently or every time?

[hannesrudolph]

That model is pretty hit and miss when calling tools in Roo but I am unable to repro that exact error.