# Click at 'plan' in chat - freezing screen

**URL:** <https://forum.cursor.com/t/click-at-plan-in-chat-freezing-screen/143816>\
**Category:** Bug Reports\
**Created:** [November 23, 2025, 7:08pm UTC](https://forum.cursor.com/t/click-at-plan-in-chat-freezing-screen/143816 "2025-11-23T19:08:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zsolt\_Tasnadi](https://avatars.discourse-cdn.com/v4/letter/z/b3f665/32.png) [@Zsolt\_Tasnadi](https://forum.cursor.com/u/Zsolt_Tasnadi)\
**Post date:** [November 23, 2025, 7:08pm UTC](https://forum.cursor.com/t/click-at-plan-in-chat-freezing-screen/143816/1 "2025-11-23T19:08:05Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

# Cursor Plan Window Freezing Issue

## Summary

The Cursor plan window freezes completely for 30-40 seconds when opening any plan, causing the application to become unresponsive. The operating system detects the freeze and prompts the user to wait or force quit.

## Environment

- **OS** : macOS 15.6.1 (Build 24G90)
- **Cursor Version** : (check via Help \> About)
- **Project Size** : 474MB, 575 files, 50,247 lines of code
- **Modified Files** : 166 files in git status
- **Project Type** : TypeScript/React with Supabase backend

## Steps to Reproduce

1. Open any plan in Cursor (either existing or newly created)
2. Click on the plan in the plan sidebar
3. The application freezes completely (no response to any clicks)
4. After 30-40 seconds, the plan content appears
5. During the freeze, macOS shows “Application not responding” dialog

## Expected Behavior

The plan should open instantly (within 1-2 seconds) without freezing the application.

## Actual Behavior

- Complete application freeze for 30-40 seconds
- Cursor Helper (Renderer) process uses 100%+ CPU during freeze
- Memory usage spikes to ~1GB during freeze
- Operating system detects unresponsiveness and prompts user

## Troubleshooting Attempted

We have tried multiple troubleshooting steps without success:

1. **Database cleanup** : Deleted composer and plan data from `state.vscdb` (reduced from 4.8MB to 72KB)
2. **AI Service data cleanup** : Deleted `aiService.prompts` (1.2MB) and `aiService.generations` (56KB)
3. **Large records cleanup** : Deleted all records \>100KB from database
4. **Cache cleanup** : Deleted `CachedData` (23MB) multiple times
5. **Images cleanup** : Deleted `images` folder (25MB, 79 images)
6. **Settings modification** : Modified diff editor settings:
  - `diffEditor.maxComputationTime`: 0 → 5000
  - `diffEditor.maxFileSize`: 10000
  - `diffEditor.renderSideBySide`: false
  - `composer.diffTimeout`: 5000
  - `composer.enableDiff`: false
  - `composer.maxPlanSize`: 1000
  - `composer.enablePlanCaching`: false

None of these steps resolved the issue.

## System Information

- **Total CPU Usage** : 118.7% (multiple cores)
- **Total Memory Usage** : 10.7%
- **Large Files** : 7 files with \>1000 lines
- **Project Type** : TypeScript/React project with Supabase backend

## Console Errors

(To be checked in Developer Tools - please check for any errors when opening a plan)

## Additional Notes

- The issue occurs with even the simplest plans (20 lines)
- The freeze happens regardless of plan complexity
- The issue started recently (was working before)
- The problem persists even after complete cache and database cleanup

## Request

Please investigate why the plan window freezes when opening plans. This significantly impacts productivity as users cannot use the plan feature effectively.

## Contact Information

### Steps to Reproduce

# Cursor Plan Window Freezing Issue

## Summary

The Cursor plan window freezes completely for 30-40 seconds when opening any plan, causing the application to become unresponsive. The operating system detects the freeze and prompts the user to wait or force quit.

## Environment

- **OS** : macOS 15.6.1 (Build 24G90)
- **Cursor Version** : (check via Help \> About)
- **Project Size** : 474MB, 575 files, 50,247 lines of code
- **Modified Files** : 166 files in git status
- **Project Type** : TypeScript/React with Supabase backend

## Steps to Reproduce

1. Open any plan in Cursor (either existing or newly created)
2. Click on the plan in the plan sidebar
3. The application freezes completely (no response to any clicks)
4. After 30-40 seconds, the plan content appears
5. During the freeze, macOS shows “Application not responding” dialog

## Expected Behavior

The plan should open instantly (within 1-2 seconds) without freezing the application.

## Actual Behavior

- Complete application freeze for 30-40 seconds
- Cursor Helper (Renderer) process uses 100%+ CPU during freeze
- Memory usage spikes to ~1GB during freeze
- Operating system detects unresponsiveness and prompts user

## Troubleshooting Attempted

We have tried multiple troubleshooting steps without success:

1. **Database cleanup** : Deleted composer and plan data from `state.vscdb` (reduced from 4.8MB to 72KB)
2. **AI Service data cleanup** : Deleted `aiService.prompts` (1.2MB) and `aiService.generations` (56KB)
3. **Large records cleanup** : Deleted all records \>100KB from database
4. **Cache cleanup** : Deleted `CachedData` (23MB) multiple times
5. **Images cleanup** : Deleted `images` folder (25MB, 79 images)
6. **Settings modification** : Modified diff editor settings:
  - `diffEditor.maxComputationTime`: 0 → 5000
  - `diffEditor.maxFileSize`: 10000
  - `diffEditor.renderSideBySide`: false
  - `composer.diffTimeout`: 5000
  - `composer.enableDiff`: false
  - `composer.maxPlanSize`: 1000
  - `composer.enablePlanCaching`: false

None of these steps resolved the issue.

## System Information

- **Total CPU Usage** : 118.7% (multiple cores)
- **Total Memory Usage** : 10.7%
- **Large Files** : 7 files with \>1000 lines
- **Project Type** : TypeScript/React project with Supabase backend

## Console Errors

(To be checked in Developer Tools - please check for any errors when opening a plan)

## Additional Notes

- The issue occurs with even the simplest plans (20 lines)
- The freeze happens regardless of plan complexity
- The issue started recently (was working before)
- The problem persists even after complete cache and database cleanup

## Request

Please investigate why the plan window freezes when opening plans. This significantly impacts productivity as users cannot use the plan feature effectively.

## Contact Information

### Operating System

MacOS

### Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.25 (Universal)  
VSCode Version: 1.105.1  
Commit: 7584ea888f7eb7bf76c9873a8f71b28f034a9820  
Date: 2025-11-23T04:45:23.529Z  
Electron: 37.7.0  
Chromium: 138.0.7204.251  
Node.js: 22.20.0  
V8: 13.8.258.32-electron.0  
OS: Darwin arm64 24.6.0

### Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [November 24, 2025, 6:52am UTC](https://forum.cursor.com/t/click-at-plan-in-chat-freezing-screen/143816/2 "2025-11-24T06:52:46Z")

</div>

Hey, thanks for the report. The 30-40 second freeze when opening plans looks similar to performance issues we’ve already seen in v2.0, especially with large projects and git status handling.

Could you help me gather some diagnostic info?

During the next freeze, please try:

- Console errors: Help \> Toggle Developer Tools \> Console tab \> screenshot any errors (especially when clicking a plan)
- Process info: `CMD+Shift+P` \> “Developer: Open Process Explorer” \> take a screenshot during the actual freeze
- Extensions check: run `cursor --disable-extensions` in your terminal and see if the freeze still happens

Let me know what you find.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [December 16, 2025, 6:53am UTC](https://forum.cursor.com/t/click-at-plan-in-chat-freezing-screen/143816/3 "2025-12-16T06:53:17Z")

</div>

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