[ENHANCEMENT] Task history optimization

[huaxianhu]

Problem (one or two sentences)

1. I hope that the task history of channel usage can be displayed as an icon permanently on the top-level page, alongside the new task/settings, instead of being hidden in a secondary list... This will make it easier for users to quickly view

2. In the multi-choice mode of task history records, besides handling the deletion of selected items, it is also desired to add the ability to export selected items

3. The export task for "task history" is set to md format by default. I hope to add more formats, such as:
   txt format - only exports the text of the chat window, which is equivalent to the user clicking the copy button of the conversation. It copies the text of all conversations into a single file in batch. Compared to other modes, its advantage is that it is easy to read and can be directly opened for reading, with the same effect as viewing directly in an IDE window
   mhtml format - can export all data completely, such as images added in the conversation, thoughts (supporting click-to-expand), tools, etc...
   The currently mechanically recognizable session format of Roo code: This format does not consider user readability and requires the perfect export of complete session information for easy sharing with friends or re-importing to restore the session on a different computer device

Context (who is affected and when)

Task history

Desired behavior (conceptual, not technical)

Task history optimization

Constraints / preferences (optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[roomote-v0]

I have reviewed this issue and explored the relevant codebase. This is a multi-part enhancement request covering three distinct features. Before proposing a plan, I have some clarifying questions:

1. Task History Icon on Top-Level Page

• Currently, the history button is registered as a VS Code title bar button (via registerCommands.ts -> historyButtonClicked) and there is a HistoryPreview component shown on the chat view when tasks exist. Could you clarify what you mean by "hidden in a secondary list"? The history button should already be visible in the extension title bar. Are you referring to something else, or is this about making the HistoryPreview section more prominent?

2. Batch Export in Selection Mode

• The selection mode in HistoryView currently only supports batch delete. Adding a "batch export" button alongside the delete button seems straightforward. Should the batch export produce a single file containing all selected tasks, or one file per selected task?

3. Additional Export Formats

• Currently, export only supports Markdown format (via export-markdown.ts). You are requesting:
  • TXT format: Plain text of chat conversation only (no tool use details, no metadata). Is that correct?
  • MHTML format: This is a complex format that would require rendering the full webview UI and capturing it. This is a significant engineering effort and may not be feasible within a single PR. Would an HTML export (standalone HTML file with embedded styles) be an acceptable alternative?
  • Session format (JSON): A machine-readable export of the complete session data (API conversation history, UI messages, task metadata) for import/restore on another machine. This would require designing both an export and import flow. Should the import functionality be part of this same feature, or would export-only be a good first step?

Priority / Scope

• Given these are three distinct features with varying complexity, would you prefer I focus on one or two of them first? My suggested priority order would be:
  1. Batch export in selection mode (smallest scope, most immediately useful)
  2. TXT export format
  3. Session/JSON export format
  4. Task history icon visibility improvements
  5. MHTML/HTML export format

Please mention @roomote in a comment with your answers, and I will proceed with a concrete implementation plan.

[huaxianhu]

4. Referencing Trae's desired task history list, each task displayed includes a short title automatically summarized by AI and a partial display of the text. Currently, Roo only shows the text, making it inconvenient for users to distinguish between historical conversations

[huaxianhu]

5. It is hoped that the task history record can enhance the convenience of folder creation, moving, and deletion for users, allowing for classification of individual tasks or multiple selections. If a folder is deleted, a confirmation box will pop up to ask whether to also delete the tasks within the folder