Content:
With the recent update to Chat Tabs 0.48, I’d like to propose a new feature that would significantly improve workflow efficiency: enabling different chat tabs to communicate with each other.
Use Case:
When implementing a complex feature that requires multiple components ex (business logic, repositories, frontend), I currently use Claude 3.7 Sonnet MAX thinking mode to gather comprehensive context. I reference associated files with @ references and ask it to plan & create a task list for each implementation phase.
However, this approach becomes unwieldy as Claude tries to handle everything at once. What I’m proposing is the ability to:
- Maintain a “main” chat tab that holds the overall context and plan
- Open separate chat tabs for each implementation phase
- Allow these specialized tabs to communicate with the main chat, while remaining focused solely on their specific task
This would create an “agent” approach where each chat tab can function independently yet share information with the main chat when needed.
Problem This Solves:
Claude 3.7 Sonnet, while powerful, often tries to accomplish too many tasks simultaneously without user confirmation, resulting in poor execution. Even with careful prompt engineering and rules, it’s difficult to keep it focused on a specific scope.
An inter-chat communication system would allow us to compartmentalize tasks while maintaining context across the workspace, improving both control and output quality.
Would this feature be valuable to others? I’d love to hear your thoughts or alternative approaches to managing complex, multi-part implementations in Cursor AI.