Cursor browser still does not support 401 http authorization

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

For 401 response a browser should show a login form, as all browsers do.

Steps to Reproduce

  1. Open any 401-protected web page in the cursor tab browser
  2. It shows 401 error instead of auth form

Expected Behavior

A login form or, at least, an ability to set the auth data for bypassing

Operating System

MacOS

Version Information

Version: 2.6.13
VSCode Version: 1.105.1
Commit: 60faf7b51077ed1df1db718157bbfed740d2e160
Date: 2026-03-06T06:17:49.499Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.2.0

Additional Information

It’s been a month since this was found here: 401 Authorization in Cursor browser not working?

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

3

Hey, this is a known limitation of the built-in browser. It doesn’t currently handle HTTP 401 auth prompts (Basic or Digest Auth). The team is aware of it.

As a workaround, you can use the Playwright MCP server instead of the built-in browser. Playwright runs a real Chromium instance, so it handles 401 auth prompts natively. You can set it up in your MCP config. See our MCP docs for setup instructions.

There’s no timeline yet for when native 401 support will ship, but your report helps us prioritize it. I’ll update here if anything changes.

4

Was definitely confused by this one too. htaccess support is badly needed in the built-in browser.

5

htaccess is badly connected to 401 response

6

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.