regression: 'Export task history' is disabled while API is active

[KJ7LNW]

Version: 3.22.5
API Provider: Anthropic
Model: sonnet-3.5

What happened?

The 'Export task history' feature shows a 🚫 symbol while the API is active. This prevents users from exporting task history while developing and letting the model continue to operate, which is a common workflow for debugging and understanding interactions between the model and Roo.

Expected behavior

'Export task history' should work at all times, even if it downloads a partial file with only whatever is available at the moment. Users should be able to export task history while the API is running to help debug and understand the interactions.

Steps to reproduce

1. Start a task with the API
2. While the API is still running, attempt to use the 'Export task history' feature
3. Observe that the option shows a 🚫 symbol and cannot be used

Additional context

This functionality worked in version 3.16.5 and broke somewhere before 3.22.5. It's a regression that impacts the development workflow, as users often need to inspect API responses while the model is still running to understand what's happening between the model and Roo.

[daniel-lxs]

The "Export task history" feature is disabled during API operations because the export button's disabled state is tied to the buttonsDisabled prop, which receives its value from sendingDisabled in ChatView (https://github.com/RooCodeInc/Roo-Code/blob/main/webview-ui/src/components/chat/TaskActions.tsx#L28).

The sendingDisabled state is set to true in multiple scenarios including when messages are sent, during API requests, when handling various tool operations, and during context condensing. It only gets set back to false in specific cases like command output responses or when there are no messages. This means that while the API is actively processing requests or executing tools, all action buttons including export remain disabled.

This behavior was introduced in PR #3623 (commit c3716f1) which added the "Condense task context" feature. The PR modified the TaskActions component to accept a buttonsDisabled prop that controls all buttons uniformly, including the export button.

The fix would involve decoupling the export functionality from the general buttonsDisabled state, allowing users to export partial task history even while the API is running. This could be achieved by either passing a separate prop specifically for the export button state or by modifying the TaskActions component to selectively enable the export button regardless of the overall disabled state.

[KJ7LNW]

That was a great summary! Did you write that or do you have an AI mode to generate the response?