[BUG] After each modification is completed, the mouse/focus jumps to the top of the code

[Maozai-Teng]

Problem (one or two sentences)

After a Roo code prompt completes the edits, it always scrolls to the top of the code and is driving me crazy as I have to scroll back down to the section of the code I'm working in.

Context (who is affected and when)

Affects anyone working in an already-open file while Roo applies a diff or saves changes during a task. Happens repeatedly within a session when edits are applied to the same file you’re viewing.

Reproduction steps

Open VSCode to use Roo-Code to edit and complete a modification, you can refer to the screen recording below

bandicam.2026-04-09.03-53-00-492.mp4

Expected result

The viewport stays where it was so you can continue reading or editing

Actual result

The editor jumps to the top, losing your place

Variations tried (optional)

1. Disable all other extensions
2. Set "editor.formatOnSaveMode" to "modifications" in the settings

This is the export file of my Roo-Code management settings

roo-code-settings.json

App Version

The latest version is v3.51.1

API Provider (optional)

None

Model Used (optional)

All of them, I've tried GPT, Gemini, Mimo, and all of them have this problem

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote-v0]

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

Root cause: In src/integrations/editor/DiffViewProvider.ts, when Roo finishes editing a file (save or revert), it calls vscode.window.showTextDocument() to re-open the file after closing the diff view. This call opens the document without restoring the viewport position, so the editor defaults to showing the top of the file.

There are three code paths that exhibit this behavior:

1. saveChanges() (line 216) - called when the user approves edits
2. revertChanges() (line 404) - called when the user rejects edits
3. saveDirectly() (line 666) - called when the preventFocusDisruption experiment is enabled

Proposed fix:

1. Capture the viewport position before closing the diff editor. In both saveChanges() and revertChanges(), read the visibleRanges from the active diff editor before closing it. This tells us which lines the user was looking at.

2. Capture the original viewport position when opening the diff. In open(), before closing the original file tab and opening the diff editor, save the visibleRanges of the original editor (if the file was already open). Store this as an instance property (e.g., originalVisibleRange).

3. Restore the viewport position after re-opening the file. After showTextDocument() returns the new TextEditor, call editor.revealRange(savedRange, vscode.TextEditorRevealType.InCenter) to scroll back to where the user was. For saveChanges and revertChanges, use the captured visible range. For saveDirectly(), find any existing editor for the file and capture its visible range before writing, then restore after.

4. Add tests to verify that revealRange is called with the captured visible range after showTextDocument in each code path.

This approach preserves the user's scroll position across all three edit flows without changing any other behavior.

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

[Maozai-Teng]

I don't know how to do it, but I still hope that a real programmer will come to reply and operate it.(:3」 ∠）
@hannesrudolph @brunobergher

Below are some related questions I found online, and without exception, none of them have been fixed. It seems many people are encountering similar problems:
#8112
#9282
https://www.reddit.com/r/RooCode/comments/1mk91nj/prevent_scroll_to_top_after_edit_save/?utm_source=chatgpt.com
https://www.reddit.com/r/RooCode/comments/1kc79po/issues_with_roo_code_extensions_file_navigation/?utm_source=chatgpt.com

[mini2s]

I don't know how to do it, but I still hope that a real programmer will come to reply and operate it.(:3」 ∠） @hannesrudolph @brunobergher

Below are some related questions I found online, and without exception, none of them have been fixed. It seems many people are encountering similar problems: #8112 #9282 https://www.reddit.com/r/RooCode/comments/1mk91nj/prevent_scroll_to_top_after_edit_save/?utm_source=chatgpt.com https://www.reddit.com/r/RooCode/comments/1kc79po/issues_with_roo_code_extensions_file_navigation/?utm_source=chatgpt.com

you can try https://github.com/zgsm-ai/costrict