Clicking learn more in the ide just takes you to a blog with no mention of “Glass” (lol).
Going to https://cursor.com/glass explains nothing. (yes I like power, sign me up!)
Is there not a single employee who can be tasked with giving us a brief summary of what we are upgrading to or installing? No screenshots, no bullets points, no changelog, no official thread I could find. It is fair for people to be hesitant of gambling with updates that entirely break workflows.
vibe update
Sigh. I read an article from earlier this month where Cursor leadership admit they don’t care about the ide or the product of making an editor for humans to code along with AI. Just making a vibe coding tool to compete with Claude Code.
looks like codex
I raised this on X with Lee.
I know its an ‘Alpha’ product but the onboarding experience was really poor. No screenshots or videos or anything. I had to rely on a comment to actually find how to launch it
The Open Cursor button doesnt actually launch Glass
This would have been enough to add to clarify it.
Agree, I think it has bad onboarding. Maybe that’s why it’s still in Alpha. I’ll forward this to the Cursor team to make the onboarding smoother.
Other than that, Cursor Glass is just like an agent orchestrator. We can compare it with Conductor and Superset, which are focused on “managing” agents.
Here’s a demo video I posted on Twitter showing how to use it to work on 2 different projects with Cursor Glass. Hope it gives you some insight!
It fcks with the color theme 
can you run agents remotely in the background or am I still going to have to use the CLI in tmux?
Is glass only available if your on the $200/m plan?
Doesn’t works with wsl2 (asks to install the wsl extension but doesn’t installs). Waiting for actual release to try it.
Yep… I really didn’t want to be forced into the dark theme. So naturally, I got Cursor Glass to fix it 
Here’s the steps to choose the theme you want in Glass:
Glass keeps its own theme preference, separate from the normal workbench color theme:
User/globalStorage/state.vscdb → table ItemTable → key glass.theme.settingsId.If that value is stuck on something like Cursor Dark, Glass will stay dark even when the rest of the UI suggests a light theme.
Open the Command Palette: ⌘⇧P (Mac) or Ctrl⇧P (Windows/Linux).
Run one of these (exact labels can vary slightly by build):
Light Theme — sets Glass (and related state) to light.
Command id: glass.lightTheme
Dark Theme — glass.darkTheme
System Theme — glass.systemTheme (follows OS light/dark)
This uses Cursor’s GlassThemeService and updates storage correctly.
If the command palette fix is not available or you need to correct a bad value:
Fully quit Cursor (so state.vscdb is not locked).
Open a terminal and run sqlite3 against your user data folder’s database, for example:
sqlite3 "/path/to/User/globalStorage/state.vscdb" \
"INSERT OR REPLACE INTO ItemTable(key, value) VALUES('glass.theme.settingsId', 'Cursor Light');"
Replace /path/to/User with your actual profile (e.g. a custom --user-data-dir).
Start Cursor again.
You can confirm the current value with:
sqlite3 "/path/to/User/globalStorage/state.vscdb" \
"SELECT value FROM ItemTable WHERE key = 'glass.theme.settingsId';"
Also, I created a second Cursor instance to run the Glass alpha in. If you or anybody wants todo the same to avoid messing up Cursor stable, do the following.
Set up a second, isolated Cursor profile on my Mac.
1. Ask me for the folder path I want for the second profile (or suggest ~/Library/Application Support/Cursor-Second-Profile).
2. Create that folder if it doesn’t exist.
3. Create an executable shell script named "Launch Cursor (second profile).command" in that folder that runs:
open -n -a "Cursor" --args --user-data-dir="<FULL_PATH_TO_THAT_FOLDER>"
(use the actual absolute path).
4. chmod +x the .command file.
5. Tell me: double-click the .command to open the second instance; first launch may require signing in again; optional: Cursor Settings ⌘⇧J → Beta → Early Access/Nightly for preview features; if a cursor:// link opens the wrong instance, quit the main Cursor first or enable features in-app.
Do not change my default Cursor data directory. Only create the new folder, the launcher script, and set permissions.
Goal: Run Cursor again with its own settings, login, extensions, and update channel (e.g. Glass preview) without touching your main install.
Examples:
Internal: ~/Library/Application Support/Cursor-Glass-Preview
External drive: /Volumes/YourDrive/Dev/cursor_glass
That folder is where all data for this instance lives (not the app binary).
mkdir -p “/path/to/your/cursor_second_profile”
open -n -a “Cursor” --args --user-data-dir=“/path/to/your/cursor_second_profile”
-n = new instance even if Cursor is already open.
Replace the path with your chosen folder.
Optional: Save that line in a .command file in that folder, chmod +x it, and double‑click to launch.
Sign in (can be a different Cursor account than your main instance).
⌘⇧J → Beta → choose Early Access or Nightly if you want preview features (update channels).
Update and enable Glass (or other preview UI) inside this window when your build offers it.
cursor://…) - Fix for opening the Glass updater urlThe OS only has one cursor:// handler. To avoid the link opening your main Cursor: quit the main instance, open only the second instance, then click the link—or use in‑app toggles instead of the browser link.
Always start “instance B” with the same --user-data-dir path (launcher script or terminal). Your main Cursor keeps using its default data under ~/Library/Application Support/Cursor when you open it normally.