Implement Tree/Hierarchical View for Chat History with tasks gened from Orchestrator Mode

[dbsxdbsx]

(ps: this post is somehow related to post: #2945)
Issue Description:

Currently, the chat history is displayed in a flat list format, which becomes difficult to navigate when using orchestrator mode with multiple sub-tasks and nested conversations.

Problem:
When the orchestrator creates multiple sub-task chats, the current linear chat history view becomes cluttered and hard to manage. Users need to scroll through a long list to find specific conversations or understand the relationship between main tasks and their sub-tasks.

Proposed Solution:
Implement a tree/hierarchical view for the chat history, similar to VSCode's folder explorer structure, where:

• Main orchestrator conversations act as parent nodes
• Sub-task chats appear as child nodes under their respective parent conversations
• Collapsible/Expandable functionality allows users to:
  • Collapse completed or inactive conversation branches
  • Expand only the conversations they're currently working on
  • Maintain a clean, organized workspace

Benefits:

1. Better Organization: Clear visual hierarchy showing task relationships
2. Enhanced UX: Familiar tree interface pattern that users already understand from file explorers

Implementation Suggestions:

• Add expand/collapse icons (▶️/▼) next to parent conversations
• Indent sub-task chats to show hierarchy
• Preserve conversation state (expanded/collapsed) across sessions

Use Case:
This would be particularly valuable when orchestrator mode generates 3+ sub-tasks,making the current flat view overwhelming to navigate--- it would be even more overwhelming if the gened sub task could also gen their own tasks(chat sessions)!

[starrain3]

Can't agree with you anymore! In my opinion, the view could be a flowchart view to show which state are currently running now and shown in a separate windows.