Feature request for product/service
Chat
Describe the request
I’m currently managing a global scoped data structure in my repository to ensure all chats can access essential workspace information. This workaround has been invaluable for debugging sessions with agents, which often flood the conversation with irrelevant context, making interactions inefficient.
To streamline this, I propose introducing sub-chats that automatically generate a concise summary from the parent chat’s history. This would create a lightweight, targeted “pseudo-context” for the new sub-chat, allowing users to dive into focused discussions without reloading the full history.
Key benefits:
One-click creation: Add a simple button to spawn a sub-chat with an agent that’s pre-loaded with relevant context, drastically reducing token usage and wait times.
Bidirectional syncing: Make syncing updates back to the parent chat optional or enabled by default. For example, if a sub-chat resolves a bug, the main context could automatically reflect the fix, keeping everything cohesive.
TL;DR: Let’s gamify and polish the chat UX with hierarchical sub-chats for smarter, token-efficient agent workflows - turning debugging into a seamless experience.
This would make Cursor even more powerful for iterative development. Thanks for considering!
Operating System (if it applies)
MacOS