# Built-in browser automation

**URL:** <https://forum.cursor.com/t/built-in-browser-automation/149085>\
**Category:** Help\
**Tags:** browser\
**Created:** [January 16, 2026, 1:06pm UTC](https://forum.cursor.com/t/built-in-browser-automation/149085 "2026-01-16T13:06:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ingvar](https://avatars.discourse-cdn.com/v4/letter/i/9dc877/32.png) [@Ingvar](https://forum.cursor.com/u/Ingvar)\
**Post date:** [January 16, 2026, 1:06pm UTC](https://forum.cursor.com/t/built-in-browser-automation/149085/1 "2026-01-16T13:06:50Z")

</div>

Last few weeks it seems that Cursor unable to perform any meaningful actions in my app UI using browser tab. It can’t click buttons, can’t find elements, can’t scroll etc.

Is anyone else having similar experience? Should I use some other tool for testing in the browser? I would prefer not to - having app right inside Cursor is very convenient.

Maybe I can change something in my app to make it easier for Cursor to browse it?

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [January 16, 2026, 4:22pm UTC](https://forum.cursor.com/t/built-in-browser-automation/149085/3 "2026-01-16T16:22:12Z")

</div>

Hey, this is a known issue. It’s a regression starting in version 2.3.18+. The team is working on a fix.

Related reports: [Agent can’t access Browser Automation tools (navigate/click/screenshot) even though Browser capabilities page lists them and Browser Automation is connected](https://forum.cursor.com/t/agent-can-t-access-browser-automation-tools-navigate-click-screenshot-even-though-browser-capabilities-page-lists-them-and-browser-automation-is-connected/148651)

Try this workaround:

1. Settings \> Tools & MCP \> Browser Automation: switch the mode from “Browser Tab” to “Google Chrome”
2. Turn Browser Automation off, then back on
3. Fully quit Cursor (`Cmd+Q` / `Ctrl+Q`, make sure the process is killed)
4. Run this in Terminal: `rm -rf ~/.npm/_npx`
5. Start Cursor again

This has helped some users.

Can you share your Cursor version (Menu \> About Cursor \> Copy)? It’ll help confirm you’re hitting this regression.

---

<div class="post-metadata">

**Author:** ![Ingvar](https://avatars.discourse-cdn.com/v4/letter/i/9dc877/32.png) [@Ingvar](https://forum.cursor.com/u/Ingvar)\
**Post date:** [January 16, 2026, 4:36pm UTC](https://forum.cursor.com/t/built-in-browser-automation/149085/4 "2026-01-16T16:36:13Z")

</div>

Version: 2.3.37  
VSCode Version: 1.105.1  
Commit: 6e2aa94f015240b4d1c7e5410b89593f9f53fef0  
Date: 2026-01-15T06:56:06.990Z  
Electron: 37.7.0  
Chromium: 138.0.7204.251  
Node.js: 22.20.0  
V8: 13.8.258.32-electron.0  
OS: Darwin arm64 25.1.0

---

<div class="post-metadata">

**Author:** ![omniscept](https://avatars.discourse-cdn.com/v4/letter/o/4bbf92/32.png) [@omniscept](https://forum.cursor.com/u/omniscept)\
**Post date:** [January 17, 2026, 8:38am UTC](https://forum.cursor.com/t/built-in-browser-automation/149085/5 "2026-01-17T08:38:15Z")

</div>

Version: 2.3.34  
VSCode Version: 1.105.1  
Commit: 643ba67cd252e2888e296dd0cf34a0c5d7625b90  
Electron: 37.7.0  
Chromium: 138.0.7204.251  
Node.js: 22.20.0  
V8: 13.8.258.32-electron.0  
OS: Darwin arm64 25.1.0