[Condense Context] Track metrics around context condensing and show in UI #3736

canrobins13 · 2025-05-20T00:38:50Z

Related GitHub Issue

Closes: #3673

Description

This PR has a few visible changes:

Adds a new UI element in the task when a condense operation is run, showing how much the context was condensed
Users can expand this UI element to view the summary message
Changes how cost and context tokens are computed, so that they are in sync with the condense operations

Point #2 above will be necessary for unlocking #3671. Without the changes in this PR, the context progress bar would not update after a manual condense operation until the next API request is made, which would be confusing to the user. After this PR, the context progress bar is correct after a condense operation even without an additional API request.

Test Procedure

Reduced the threshold for running condense operations and used the extension
Ensured the UI in the left looked correct and was consistent with the progress bar
Logged the API messages and Cline Messages to sanity check

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

Screenshots / Videos

Collapsed view

Expanded view

Important

This PR adds UI and backend support for tracking and displaying context condensing metrics, ensuring synchronization with context operations.

UI Changes:
- Adds a UI element in ChatRow.tsx to display context condensing metrics.
- Users can expand this element to view a summary message.
Functionality:
- Updates summarizeConversation() in index.ts to return a SummarizeResponse with context metrics.
- Modifies truncateConversationIfNeeded() in sliding-window/index.ts to handle context condensing.
- Implements contextCondenseSchema in schemas/index.ts for context condensing data.
Testing:
- Adds tests in index.test.ts and sliding-window.test.ts to verify context condensing behavior.
Miscellaneous:
- Updates getApiMetrics() in getApiMetrics.ts to include context condensing metrics.
- Adds translations for context condensing in various language files.

^{This description was created by}^{for 7df703f. You can customize this summary. It will automatically update as commits are pushed.}

…n UI

changeset-bot · 2025-05-20T00:38:53Z

🦋 Changeset detected

Latest commit: 7df703f

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
roo-cline	Patch

Not sure what this means? Click here to learn what changesets are.

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

daniel-lxs · 2025-05-20T03:05:04Z

src/core/condense/index.ts

+	// Check if there's a recent summary in the messages we're keeping
+	const recentSummaryExists = keepMessages.some((message) => message.isSummary)
+	if (recentSummaryExists) {
+		return response // We recently summarized these messages; it's too soon to summarize again.


Hey @canrobins13,

Just a question about the truncateConversationIfNeeded function in sliding-window:

When autoCondenseContext is true and the token limit is hit, it tries to summarize. But if summarizeConversation decides not to create a summary (maybe because there aren't many new messages or there was a recent summary), it looks like truncateConversationIfNeeded still goes ahead and does the simple truncation.

I am aware this behavior was present before your changes, but would it make more sense to use the previous summary considering it might still be fresh rather than using the simple truncation?

When making an API request we only send messages starting from the latest summary if one exists, so the recent summary message would be "used" in the case you highlighted (when making API requests and when calculating the context window usage).
This case should be pretty hard to hit through the existing implementation, but will be more relevant because we're about to add a button for manually triggering context summarization through the UI.

Makes sense, if the condense feature becomes manual and the user clicks summarize multiple times, would this trigger the simple truncation? Or is it only triggered when the context is already bigger than the window?

It's not implemented yet, but we wouldn't trigger simple truncation or dropping of messages from the user button, that would only hit the new condense code

daniel-lxs · 2025-05-20T03:14:52Z

webview-ui/src/components/chat/ContextCondenseRow.tsx

+				<div className="mt-2 ml-6 p-3 bg-vscode-editor-background rounded text-vscode-foreground text-sm">
+					<h3 className="font-bold mb-2">{t("chat:contextCondense.conversationSummary")}</h3>
+					{summary}
+				</div>


Hey again,

Would rendering the summary with webview-ui/src/components/chat/Markdown.tsx create too much visual clutter?

It might make the summary easier to read specially since the models love to output markdown.

Let me try it that out!

I like it, updated the code :)
The only downside it that things like tags are omitted... it's a better UI but maybe slightly worse for analysis/debugging.

Ah, are you talking about the tags? Does the summary prompt encourage the model to use other XML tags?

If that's the case it would be interesting to see if we can improve the Markdown.tsx component to show the tags, of course in a different PR.

No, it doesn't encourage it to use any other tags

daniel-lxs · 2025-05-20T03:18:13Z

Great work! Now we won't have so many people asking about when this feature is triggered and what it does.

I'm honestly really excited to be able to trigger this behavior manually as well.

src/core/sliding-window/index.ts

webview-ui/src/components/chat/ContextCondenseRow.tsx

cte · 2025-05-20T03:50:24Z

src/core/task/Task.ts

-		// If the previous API request's total token usage is close to the
-		// context window, truncate the conversation history to free up space
-		// for the new request.
-		if (previousApiReqIndex >= 0) {


Is there anything different about this previousApiReqIndex version and the new code (which seems simpler)? It seems like they are different but it's hard for me to tell if the new version is also correct.

I had the same question but I couldn't find any reason that it wasn't using getApiMetrics before... agree it feels weird

cte

Looks great to me; left a few nits (feel free to ignore) and one question.

webview-ui/src/components/chat/ContextCondenseRow.tsx

* add protos files (RooCodeInc#3736) Co-authored-by: Elephant Lumps <[email protected]> * change package script --------- Co-authored-by: Elephant Lumps <[email protected]>

* add protos files (RooCodeInc#3736) Co-authored-by: Elephant Lumps <[email protected]> * change package script * rest of updates for vertex / bedrock --------- Co-authored-by: Elephant Lumps <[email protected]>

[Condense Context] Track metrics around context condensing and show i…

603d2ef

…n UI

github-project-automation bot added this to Roo Code Roadmap May 20, 2025

github-project-automation bot moved this to New in Roo Code Roadmap May 20, 2025

canrobins13 changed the title ~~[Condense Context] Track metrics around context condensing and show i…~~ [Condense Context] Track metrics around context condensing and show in UI May 20, 2025

canrobins13 added 14 commits May 19, 2025 18:20

Add UI component

95bd6cb

account for system prompt when estimating new context size

65f7f35

add header

585023a

bug fix

2bdd7d1

nit

f4a263d

nit

0fb8075

refactor

7053547

fix

7c3f799

add unit tests for condense

9765612

update sliding-window tests

01bdc53

add getApiMetrics.test.ts

a028f72

fix failing tests

599e1c3

use chat.json

fe883e3

add translations

5318a2f

daniel-lxs reviewed May 20, 2025

View reviewed changes

add tests for ContextCondenseRow

bc94dba

add changeset

ff56aba

canrobins13 marked this pull request as ready for review May 20, 2025 03:22

canrobins13 requested review from mrubens and cte as code owners May 20, 2025 03:22

dosubot bot added size:XXL This PR changes 1000+ lines, ignoring generated files. enhancement New feature or request labels May 20, 2025

ellipsis-dev bot reviewed May 20, 2025

View reviewed changes

src/core/sliding-window/index.ts Outdated Show resolved Hide resolved

camelCase

29e055c

cte reviewed May 20, 2025

View reviewed changes

webview-ui/src/components/chat/ContextCondenseRow.tsx Outdated Show resolved Hide resolved

cte reviewed May 20, 2025

View reviewed changes

webview-ui/src/components/chat/ContextCondenseRow.tsx Outdated Show resolved Hide resolved

cte reviewed May 20, 2025

View reviewed changes

cte approved these changes May 20, 2025

View reviewed changes

dosubot bot added the lgtm This PR has been approved by a maintainer label May 20, 2025

use Markdown for summary

1f30149

ellipsis-dev bot reviewed May 20, 2025

View reviewed changes

webview-ui/src/components/chat/ContextCondenseRow.tsx Show resolved Hide resolved

canrobins13 added 2 commits May 19, 2025 20:57

use tailwind

671c3b7

non default export

a1a8654

canrobins13 force-pushed the canyon/condense-metrics branch from d2bdd98 to a1a8654 Compare May 20, 2025 04:32

rm test :/

7df703f

canrobins13 merged commit aff94e1 into main May 20, 2025
12 checks passed

github-project-automation bot moved this from New to Done in Roo Code Roadmap May 20, 2025

canrobins13 deleted the canyon/condense-metrics branch May 20, 2025 04:45

mrubens added this to Roo Code Roadmap May 20, 2025

github-project-automation bot moved this to New in Roo Code Roadmap May 20, 2025

hannesrudolph moved this from New to Done in Roo Code Roadmap May 20, 2025

[Condense Context] Track metrics around context condensing and show in UI #3736

[Condense Context] Track metrics around context condensing and show in UI #3736

Uh oh!

Conversation

canrobins13 commented May 20, 2025 • edited by ellipsis-dev bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Related GitHub Issue

Description

Test Procedure

Type of Change

Pre-Submission Checklist

Screenshots / Videos

Collapsed view

Expanded view

Uh oh!

changeset-bot bot commented May 20, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🦋 Changeset detected

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

daniel-lxs May 20, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

canrobins13 May 20, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

daniel-lxs commented May 20, 2025

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

cte left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

canrobins13 commented May 20, 2025 •

edited by ellipsis-dev bot

Loading

changeset-bot bot commented May 20, 2025 •

edited

Loading

daniel-lxs May 20, 2025 •

edited

Loading

canrobins13 May 20, 2025 •

edited

Loading