Terminal Cmd+click localhost links open in Safari despite “Show Localhost Links in Browser”

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Summary
With Browser Tab + localhost-in-browser settings enabled (and confirmed in settings.json)
Cmd+clicking a localhost:* URL in the integrated terminal still opens macOS Safari instead of Cursor’s Browser Tab.
Fully quitting and restarting Cursor does not change this.

Steps to Reproduce

Enable the settings above; quit Cursor fully and reopen.
Run a local server so the terminal shows a clickable localhost URL (e.g. Next.js Local: localhost:3001).
Cmd+click the http://localhost:3001 link in the integrated terminal.

Expected Behavior

URL opens in Cursor’s Browser Tab (per “Show Localhost Links in Browser” / workbench.browser.openLocalhostLinks).

Actual
URL opens in Safari (system default browser).

Notes
Setting is correctly written and persists across restart; this does not look like a user-config mistake.
Agent/search UI (⇧⌘P sometimes opens All/Agents/Files/Actions) is easy to confuse with the Command Palette, but the link-open path is independent of that.
Workaround: Command Palette → Browser: Open Integrated Browser, or ask the Agent to open the URL.

Operating System

MacOS

Version Information

Environment
OS: macOS (darwin 25.5.0)
Cursor: 3.13.25
App: Next.js 16.2.11 (pnpm run dev) printing Local: localhost:3001
Settings
Cursor Settings → Tools & MCP / Browser & Network:
Browser Automation: Browser Tab
Browser Protection: OFF
Show Localhost Links in Browser: ON
Open Web Links in Browser: ON
User settings.json (~/Library/Application Support/Cursor/User/settings.json):
“workbench.browser.openLocalhostLinks”: true

No workspace override of this setting.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hi @andres_Vervaecke, Thanks very much for bringing this to our attention! We are tracking this and we have prepared a fix for this. I don’t have an exact ETA to share with you, but I’ll try to reply here when the fix is shipped!

In the meantime, the two workarounds that you mentioned are a great option. Nothing is wrong with your setup, you can leave as-is. The issue is on our side.