Feature Request: Group Conversations by Backend, Container, and Workspace
#1,351 opened on Jun 14, 2026
Repository metrics
- Stars
- (43 stars)
- PR merge metrics
- (PR metrics pending)
Description
Summary
Add additional grouping options to the Conversations panel to improve navigation and organization when working with multiple containers and workspaces.
Current options
Proposed Features
Add the following optional grouping controls to the Conversations panel:
- Group by Container
- Group by Workspace
These options should be independent checkboxes that users can enable or disable according to their workflow.
Expected Behavior
When both Group by Container and Group by Workspace are enabled, the conversation list should be displayed as a hierarchical tree:
Container 1
├── Workspace A
│ ├── Conversation A
│ ├── Conversation B
│ └── Conversation C
└── Workspace B
├── Conversation D
└── Conversation E
Container 2
└── Workspace C
├── Conversation F
└── Conversation G
If only Group by Container is enabled:
Container 1
├── Conversation A
├── Conversation B
└── Conversation C
Container 2
├── Conversation D
└── Conversation E
If only Group by Workspace is enabled:
Workspace A
├── Conversation A
├── Conversation B
└── Conversation C
Workspace B
├── Conversation D
└── Conversation E
Motivation
Users working with multiple containers and workspaces can accumulate a large number of conversations, making navigation increasingly difficult. Grouping conversations by container and workspace would provide a more intuitive structure and make it easier to locate relevant conversations.
Additionally, the feature requests discussed in https://github.com/OpenHands/agent-canvas/issues/1145, https://github.com/OpenHands/agent-canvas/issues/1153 and https://github.com/OpenHands/agent-canvas/issues/914 could potentially be addressed through the introduction of a Group by Workspace option, providing a unified and flexible organizational model rather than adding separate navigation mechanisms.
Benefits
- Improved scalability for large conversation histories.
- Faster navigation between related conversations.
- Better visibility of container/workspace relationships.
- Reduced clutter in the conversation list.
- A flexible foundation for workspace-based organization and future grouping options.