Grayed-out text issue - Approval Dialog Not Rendering

[BuildPlusDev (Kash)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The actual problem is:

The approval popup/dialog is not rendering/appearing on screen, but the approval process is still triggering in the background. This causes:

The approval process starts (AI asks for permission to run a command or add to allowlist)
The approval popup/dialog does NOT appear visually on screen
The background text gets grayed out (waiting for approval)
I have no way to approve or reject because there’s no visible dialog
Everything remains stuck in this grayed-out state
What I can see:

Bottom status: “Waiting for approval”
Options: “Stop”, “Reject, suggest, follow up?”
But no popup window showing what needs approval
What I cannot see:

The actual approval dialog box
What command needs approval
What needs to be added to allowlist
Any buttons to approve/reject
This appears to be a rendering bug where the modal/popup component is not displaying, even though the approval workflow is executing.

Steps to Reproduce

I needed an support

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.34 (user setup)
VSCode Version: 1.105.1
Commit: 643ba67cd252e2888e296dd0cf34a0c5d7625b90
Date: 2026-01-10T21:17:10.428Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.19045

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[deanrie]

Hey, thanks for the report. This is a known issue: the approval dialog doesn’t render in 2.3.x versions. The team is already working on a fix (it regressed after a temporary workaround in December).

Try this:

• Run Cursor without extensions: cursor --disable-extensions in your terminal
• Turn on auto-apply: Settings → search for “Auto-apply Edits” or “Auto-run”, this will skip manual confirmation

For debugging, we need:

• Console errors: Ctrl+Shift+P → Developer: Toggle Developer Tools → Console tab (screenshot or copy the errors)
• The Request ID from the stuck chat: chat menu (top right) → Copy Request ID

Can you share that info? It’ll help the engineers troubleshoot faster.

[BuildPlusDev (Kash)]

Thank you for your prompt rely, I’ve checked this morning everything is working fine now, but I’ve now got another issues which makes cursor ide completely closed and crashed.

Version: 2.3.35 (user setup)
VSCode Version: 1.105.1
Commit: cf8353edc265f5e46b798bfb276861d0bf3bf120
Date: 2026-01-13T07:39:18.564Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.19045

I’ve attached console log

console_cursor_at_15012026_0748.txt (14.6 KB)

[deanrie]

Thanks for the info. From the logs that you’re working over Remote/SSH. The path shows /home/buildco/.cursor-server/, which explains the issues.

Key errors in the logs:

• The Extension Host becomes UNRESPONSIVE (multiple times)
• AI tokens don’t arrive (“No first token received within 14s”)
• Diff computation times out on large files (226 → 525 lines)

This is a known issue with Remote connections, and the team is working on it.

Please try:

• On the remote server, start Cursor with extensions disabled. Check which extensions are installed on the remote host and disable any you don’t need.
• Start a new chat. A long session history can make the memory issue worse.

Also, how much RAM does the remote server have, and which extensions are installed there?

[BuildPlusDev (Kash)]

Thanks for the valuable reply, please find the attached screenshot of extension installed
I am using WSL Ubuntu

[deanrie]

Thanks for the screenshot with the extensions you have installed.

Try this:

1. Start a new chat. The old one might be using a lot of memory and making Extension Host issues worse.
2. Try it without Dev Containers. Disable it for now and keep only WSL. Dev Containers might not be needed if you’re just working in WSL without Docker containers.
3. Open an empty folder in WSL. If it doesn’t crash there, the issue is probably related to your project size.

Also, a few questions to help diagnose:

• How much RAM does your computer have, and how busy is the system? (Task Manager)
• How big is the current project? How many files? Do you have large node_modules or .git folders?

If a new chat plus disabled extensions helps, it’s likely the combo of “long history + extensions + big project”. If it still crashes even then, it’s a known Extension Host bug on WSL and the team is working on a fix.