Integrated browser: cmds from agent do not make it through

[Rf_Tsu]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

‘CTRL +Shift + R’ and similar keyboard-type cmds if run from agent has no effect to the integrated browser (chrome): the agent can though switch to new tabs, change url, make browser action: just the keyboard cmds seem to not make it through and the agent have no message error in return (no error message in return is expected though)

it proceed after that assuming hard reload correct hence basically if it was verifying a bugfix it won’t get the new update page and the agent thinks the fix didn’t work (but if I manually reload the integrated browser the agent confirm the fix hence this confirms it’s not just something ‘visual’ but the browser actually not receiving/parsing the ctrl+shift+R cmd)

Steps to Reproduce

fire integrated browser and ask agent to hard refresh the integrated browser (chrome) page

Expected Behavior

page reloads (reload is visually observable when it works, tested: it’s an heavy magento 2 page in developer mode: will take 5 to 10 seconds: no pwa)

Operating System

Linux

Version Information

Version: 2.3.30
VSCode Version: 1.105.1
Commit: d1289018cc3fcc395487f65455e31651734308d0
Date: 2026-01-08T05:21:38.211Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Linux x64 5.15.0-139-generic

For AI issues: which model did you use?

gpt-5.2 Codex

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the report. I see the screenshot. Looks like the agent is trying to send Ctrl+Shift+R, but it never reaches the browser.

This seems like a gap in the current browser tool functionality. Keyboard shortcuts as a separate action aren’t supported yet, or they’re working incorrectly. The browser can navigate, click, type into fields, and scroll, but sending system key combos (hard refresh, etc.) is a bit different.

I’ve passed this to the team. For now, the workaround is to ask the agent to do a normal refresh by navigating to the current URL, or just reload manually after changes.

[Rf_Tsu]

thanks Dean, understood. your confirmation is a valuable info.

I’ve instructed the agent to reopen the browser when it needs hard refresh for now and it is a decent provisional workaround.

thanks for forwarding this to the team, we’ll love to have this in the future but we’ll use what available for now, no problem.

have a great day