Browser Automation shows "disabled by admin" on an individual account

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’m currently using a personal/individual Cursor account with an Ultra subscription plan. My account is not part of any team, organization, or enterprise workspace.

However, when I open Settings → Tools & MCPs → Browser Automations, the feature is unavailable and displays the message:

Browser automation disabled by admin

This is confusing because there should be no administrator managing or restricting features on my account.

I’m trying to understand whether:

This is expected behavior for Ultra users,
Browser Automation is currently behind a feature flag or gradual rollout,
Or if my account is incorrectly being treated as organization-managed.

Steps to Reproduce

Settings → Tools & MCPs → Browser Automations

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.6.31 (user setup)
VS Code Extension API: 1.105.1
Commit: 81fcf2931d7687b4ff3f3017858d0c6dee7e2a60
Date: 2026-05-31T17:46:29.630Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.220
OS: Windows_NT x64 10.0.19045

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hi Rangga,

Thanks for reporting this, and I’m sorry for the confusion here. I’ve filed a bug report and hopefully we can get this sorted out for you soon. One thing we’re checking is whether your account may still have a previous team association on our side, which could be causing Cursor to show the admin-managed Browser Automation setting even though you’re using an individual subscription now.

We’ll follow up once we have a clearer answer or a fix. Thanks again for flagging this and for including the version details and screenshot.

Thanks for the update.

One thing I’d like to clarify is that I have never been part of a team, organization, or enterprise workspace at any point since creating this account.

Please let me know if there’s any additional information I can provide to help with troubleshooting.
Thanks.

@Rangga Thank you that is very helpful context.

Hi,
I’m not even on a team plan, though I see “browser automation disabled by admin” and there’s no option to change the toggle.

I have the exact same issue (MacOS).

Hey all!

This should be fixed now. Let us know if you still have issues accessing browser automation.

Deer, I’m still encountering this problem, “I’m not even on a team plan, though I see “browser automation disabled by admin” and there’s no option to change the toggle.”

Hi @Cooper_James Thanks for the post. Your 2nd screenshot shots the Run Mode allowlist rather than the Browser Automation feature. The browser automation feature is available under Tools & MCP. Can you please let us know what you see there if that is the issue?

@kevinn Oh, sorry, I made a mistake. The problem is “auto-review is disabled for your admin.” This issue occurred when I switched proxies. Is it because this feature is currently disabled in some countries and regions?

Got it! I took a closer look and I have good news: this isn’t disabled by country or region, and there’s no admin restricting your individual account.

Auto-review is a Run Mode that relies on one of Cursor’s managed background classifier models. It shows as greyed out (with that “disabled by admin” label) whenever your active model set doesn’t include a model that supports the classifier. That’s usually the case when a custom API key or a custom base URL override is enabled, which is likely what changed when you switched proxies, since those custom/BYOK models don’t support the classifier.

To get Auto-review back:

  • Open Settings > Models
  • Turn off any custom API key and custom base URL override (Custom OpenAI / Anthropic)
  • Make sure the built-in Cursor models are enabled (Auto, or any frontier model running on Cursor inference)

After that, Auto-review should become selectable again. Allowlist mode keeps working either way. Let me know if it’s still greyed after switching off the override.

@kevinn got it,thank you for your explanation~