Feature request for product/service
Cursor IDE
Describe the request
Feature Request: Persistent Queue Storage for AI Requests
Problem Statement
When WSL2 crashes, Docker restarts, or Cursor needs to reload the window, all queued AI requests are lost. This results in:
Lost work and context from pending queries
Wasted time re-typing or re-generating complex requests
Frustration from having to remember what was in the queue
Disruption to workflow during system issues
This is particularly painful when you’ve queued up multiple related requests (refactoring tasks, documentation generation, test creation, etc.) and a system crash wipes everything.
Use Cases
Primary: WSL2/System Crashes
User queues:
- “Refactor UserService to use dependency injection”
- “Add unit tests for authentication flow”
- “Generate API documentation for all endpoints”
- “Optimize database queries in OrderRepository”
WSL2 crashes → Cursor reloads → Queue is lost
With persistence → Queue automatically restored
Docker Restarts
Working on containerized project
Queue 5 complex refactoring tasks
Docker needs restart
Window reloads → Queue persists
Intentional Window Reload
Extension update requires reload
Or: Manual reload for performance
Queue remains intact
Additional Context: This issue becomes critical when working with WSL2, which is notorious for crashes and hangs requiring window reloads. Losing a carefully crafted queue of 5-10 related refactoring tasks can waste 10-15 minutes of work.
Would love to see this implemented to make Cursor more resilient to system instability!