[ENHANCEMENT] Auto Clean Task History

[NaccOll]

Problem (one or two sentences)

RooCode creates a new Task Id for each new conversation. If the user turns on the checkpoint function, this will cause the disk space to expand rapidly.

Context (who is affected and when)

People who enable checkpointing and work in large repositories

Desired behavior (conceptual, not technical)

Automatically clean up task history (mainly checkpoints)

When the number of task histories reaches the default upper limit, or the disk space reaches the default upper limit, or old tasks (more than 7 days ago) are automatically cleaned up

Constraints / preferences (optional)

It is best to clean up during idle time to avoid affecting the user's current work tasks.
Regarding the auto clean setting of thresholds, it is best to allow users to configure them.
In order not to affect old behavior, this feature should be turned off by default.

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]

I'm exploring a potential implementation for the auto-cleanup feature for task history and checkpoints. I'll work on adding configurable thresholds for disk space, task count, and age-based cleanup while ensuring it runs during idle time to avoid disrupting active work.

[roomote]

I have successfully implemented the auto-cleanup feature for task history as requested.

Summary

PR #8173 has been created with the following implementation:

Features Added:

• ✅ Configurable auto-cleanup settings with sensible defaults (disabled by default for backward compatibility)
• ✅ Three cleanup criteria: task count limit (100), disk space limit (1GB), and age limit (7 days)
• ✅ Workspace protection: Tasks from the current active workspace are protected from deletion
• ✅ Idle-time execution: Cleanup runs asynchronously after a 5-second delay to avoid blocking operations
• ✅ Comprehensive test coverage: All cleanup scenarios are tested

Configuration Options:

• taskHistoryAutoCleanupEnabled: Enable/disable auto-cleanup (default: false)
• taskHistoryMaxCount: Maximum number of tasks to keep (default: 100)
• taskHistoryMaxDiskSpaceMB: Maximum disk space in MB (default: 1024)
• taskHistoryMaxAgeDays: Maximum age in days (default: 7)

Testing:

All CI checks are passing, including unit tests for the new cleanup service and existing tests confirming no regression.

The implementation addresses the disk space expansion issue while maintaining backward compatibility by keeping the feature disabled by default.

PR Link: #8173

Feedback and review are welcome!