Automations page doesn't load

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hey team,

Every time I open the automations page on the IDE, it doesn’t load, and the following message shows up: “Unable to load automations” and a try again button.

I don’t have any automations, so that might be the issue? But at the same time, I can’t see the suggested automations at the bottom of the page because it throws an error.

then when it fails:

Steps to Reproduce

Click on Automations on the left side panel

Expected Behavior

I expect it not to throw an error and to keep the suggested automations at the bottom of the page.

Operating System

MacOS

Version Information

Version: 3.5.38
VSCode Version: 1.105.1
Commit: 009bb5a3600dd98fe1c1f25798f767f686e14750
Date: 2026-05-26T21:32:06.537Z
Layout: glass
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
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report and the screenshots. Automations in Glass IDE is a brand-new feature, so some early rough edges are possible. The error itself could be temporary too, like auth or network, or it could be a bug.

Let’s clarify a couple things so we can find the cause:

  1. Does clicking Retry help, or does a full Cursor restart help? Is the error always there, or does it load sometimes?
  2. Open the Developer Console: Help > Toggle Developer Tools, go to the Console tab, then open Automations again and share the error text, especially lines mentioning listAutomations or any network or auth errors.
  3. Are you on a VPN or a corporate proxy like Zscaler? If yes, try turning it off temporarily and test again.
  4. Is Privacy Mode enabled?

With this info, it’ll be clearer if this is local on your side like network or config, or a bug on our side. Let me know how it goes.

Hey thanks for reaching back!

I was, in fact, in legacy privacy mode. When I changed to the regular privacy mode it worked.

The error shown in the developer tools helped point me in the right direction. :smiley:

Thanks!