Agents unable to navigate in @Browser

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I tried Opus, Composer, Haiku and Grok Code and none of them seem to be able to scroll or use arrow keys. They seem to be able to click on things already in view, but that is it. It is unclear if they have any way of seeing the DOM. I only get snapshots and they seem to read a console log that is not what I see in the browser dev tools (I can clear it and see a few lines, but the agent claims it sees a large amount of logging, which likily wastes a lot of tokens.

Steps to Reproduce

Load a page that is taller than the current scroll area and ask it to read the bottom. It will try many ways to scroll but can’t do it

Expected Behavior

It should be able to use the browser.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.46 (Universal)
VSCode Version: 1.105.1
Commit: ab326d0767c02fb9847b342c43ea58275c4b1680
Date: 2025-12-02T03:59:29.283Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

Opus, Haiku, Composer, Grok Code

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

2

Hey, thanks for the report. According to the docs, @Browser should be able to scroll and read the console: https://cursor.com/docs/agent/browser

Help reproduce and gather debug info:

  • Public URL or minimal page example where scrolling fails
  • Short video/screencast
  • Any errors in DevTools/console on the page

Let me know the results—if it’s a confirmed bug, I’ll escalate to engineers.