[Condense] Add button for basic condensing of task message history

[canrobins13]

Related GitHub Issue

Closes: #

Description

Adds a button to the expanded TaskActions component which allows the user to manually condense the message history. Currently this button just calls the existing code to truncate messages if the context window is full, but its implementation will be replaced with an LLM call to summarize the message history a la cline/cline#3086.

Test Procedure

Type of Change

• 🐛 Bug Fix: Non-breaking change that fixes an issue.
• ✨ New Feature: Non-breaking change that adds functionality.
• 💥 Breaking Change: Fix or feature that would cause existing functionality to not work as expected.
• ♻️ Refactor: Code change that neither fixes a bug nor adds a feature.
• 💅 Style: Changes that do not affect the meaning of the code (white-space, formatting, etc.).
• 📚 Documentation: Updates to documentation files.
• ⚙️ Build/CI: Changes to the build process or CI configuration.
• 🧹 Chore: Other changes that don't modify src or test files.

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Code Quality:
  • My code adheres to the project's style guidelines.
  • There are no new linting errors or warnings (npm run lint).
  • All debug code (e.g., console.log) has been removed.
• Testing:
  • New and/or updated tests have been added to cover my changes.
  • All tests pass locally (npm test).
  • The application builds successfully with my changes.
• Branch Hygiene: My branch is up-to-date (rebased) with the main branch.
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Changeset: A changeset has been created using npm run changeset if this PR includes user-facing changes or dependency updates.
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

Documentation Updates

Does this PR necessitate updates to user-facing documentation?

• No documentation updates are required.
• Yes, documentation updates are required.

No obvious spot for this in the docs right now but ideally all UI features should be documented.

Additional Notes

The current implementation of task.condenseHistory is pretty useless since maybeTruncateConversationHistory is called in task.attemptApiRequest anyway, but the goal is to replace the condenseHistory implementation with an LLM summarization.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c2d7d41

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[canrobins13]

Reviewers: Is it okay to look for a task in the stack like this?

[daniel-lxs]

Hey @canrobins13,
This seems to be already implemented, feel free to reopen it if you want to revisit this.