The built-in Browser Tab DevTools Console shows no output at all

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The built-in Browser Tab DevTools Console shows no output at all — no logs, warnings, errors, or network-related console messages. The JavaScript execution context dropdown ([ ▼]) next to the filter bar is greyed out / disabled, so DevTools appears disconnected from the page’s JavaScript runtime.

This happens on every website tested (e.g. https://www.apple.com, localhost apps, staging UIs) — not tied to any single project or codebase.

Impact: Web debugging inside Cursor is effectively broken. Console inspection, live expression evaluation, and console-based troubleshooting are unavailable in the embedded browser.

Steps to Reproduce

Open Cursor v3.19.13 (confirmed identical on both machines below).
Open a Browser Tab (Cmd+Shift+B / Ctrl+Shift+B, or via the browser icon in Agent/Chat).
Navigate to any URL — e.g. https://www.apple.com or a local dev server.
Open DevTools on that tab (right-click → Inspect, toolbar Show Console, or F12).
Switch to the Console tab.
Optionally: run console.log(‘test’) from the page (if you can inject via another path) or trigger known page logging — nothing appears.
Observe the execution context selector [ ▼] — it is greyed out and cannot be changed.

Expected Behavior

Console displays page logs, warnings, and errors.
Execution context dropdown is active and lists the page’s JavaScript context.
DevTools behaves like Chrome/Edge DevTools for the same URL.

Operating System

Windows 10/11
MacOS

Version Information

Environment (two independent repros)
Machine A — macOS

Cursor: 3.19.13
OS: macOS (Apple Silicon)
Projects: Multiple workspaces / unrelated applications
Repro: Yes — all Browser Tab pages, all sites
Machine B — Windows

Cursor: 3.19.13 (same version as Mac)
OS: Windows 11
Developer: Different user, different machine, different applications entirely
Repro: Yes — identical symptoms

For AI issues: which model did you use?

Composer 2.5 / Gemini Flash 3.8

Additional Information

Filter settings (Custom levels, sidebar filters, clear console) do not fix it.
Issue affects both Mac Studio and a separate Windows PC used by a different developer — strongly suggests a Cursor embedded-browser / DevTools regression, not application code.
Makes in-IDE web debugging unusable until fixed.

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

Hey @PartnerInAI thanks for the detailed report.

This isn’t on your end. It’s an issue we’re tracking that came in with 3.19’s newer Chromium runtime, and it affects the built-in Browser tab’s DevTools (Console, Network, Elements) on both macOS and Windows.

Workaround for now: open the same URL in an external browser (Chrome/Edge) and use its DevTools. If you just need the page’s console, you can also ask the in-IDE agent to check the browser console - that still works.

I’ll post here when there’s an update.

9

Hey @PartnerInAI,

Quick update on this: the Browser tab DevTools showing no output (empty Console, greyed-out context selector) has been fixed, and the fix is in Cursor 3.20!

Please give it another try once you’re on that version.