feat: warning component to reduce bug when it has large context or token

[samhvw8]

Context

Some user has black screen or gray screen due to has very large chat conversation (input token: 30 mil, 70 mil, 200 mil)

Implementation

Create new element that warning user when excess threshold, show it to user

Screenshots

before	after

Screen cast

Warning Long Chat Conversation - Watch Video

How to Test

Get in Touch

---

Important

Introduces a warning component to alert users when chat context or token usage exceeds thresholds, with updates to UI components, settings, and localization files.

• Behavior:
  • Adds TokenUsageWarning component in ChatView.tsx to alert users when context or token usage exceeds thresholds.
  • Introduces warningThreshold settings in ClineProvider.ts and webviewMessageHandler.ts to manage warning thresholds.
• UI Components:
  • New TokenUsageWarning.tsx component for displaying warnings and allowing users to start a new task.
  • Updates ContextManagementSettings.tsx to include WarningThresholdSettings.
• Localization:
  • Updates localization files for multiple languages to include new warning messages and settings descriptions.
• Misc:
  • Adds warningThresholdSchema in schemas/index.ts for validation.
  • Updates ExtensionMessage.ts and WebviewMessage.ts to handle new warning threshold messages.

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: b981a33

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

[ellipsis-dev]

This pull request includes a large number of changes across different areas of the codebase. To improve reviewability and maintain focus, it would be beneficial to split the localization changes into a separate pull request. This way, the core functionality changes related to the warning component can be reviewed independently from the localization updates. Please consider creating a separate pull request for the localization changes, which include updates to the i18n files for various languages.

[cte]

Very cool! Will take a look today.

[sachasayan]

Would suggest playing around with a TaskHeader placement... :)

[samhvw8]

@sachasayan i get inspired from claude chat, i think they put near chat area to make UX better when your drag mouse into it, should we can add dismiss / close button like them ?

[sachasayan]

Okay, I'm fine with it where it is. Yes, I'd say let's add a dismiss/close button and let's ship. We can do a styling refinement pass later. :)

[mrubens]

I think we should probably discuss a little more before shipping. On my phone, but some questions that come to mind:

What are the defaults? Should this setting be model specific? When it starts a new task, does that boomerang back when it’s done?

[samhvw8]

@mrubens

• for default value i think context window: 75%, total token (input tokens + output token): 5_500_000, cost: 3$
• for Should this setting be model specific: for total token may be we need model specific
• When it starts a new task, does that boomerang back when it’s done?: i think we don't need to boomerang back

@sachasayan after dismiss should we make it show up again when user meet 1-2 consecutive error ?

[mrubens]

@mrubens

• for default value i think context window: 75%, total token (input tokens + output token): 5_500_000, cost: 3$
• for Should this setting be model specific: for total token may be we need model specific

Yeah, total tokens does seem like it would need to be model specific. Same thing with cost, I think.

• When it starts a new task, does that boomerang back when it’s done?: i think we don't need to boomerang back

Right now every new_task will boomerang back right?

[samhvw8]

Yeah, total tokens does seem like it would need to be model specific. Same thing with cost, I think.

should we move all into provider config or just total + cost ?

Right now every new_task will boomerang back right?

yeah, let make an follow up pr that can allow new_task had option to not return parent task ? and default will be return to parent ?

[samhvw8]

@mrubens update my pr, move config to per profile setting, can disable with switch or manual set to -1

[sachasayan]

Hey @samhvw8 I think we've chatted about this one and we're not quite sure about where the thresholds should be + it needs some UI polish. Those are the two big outstanding issues right now.

[mrubens]

I think there’s also the issue that all new tasks are subtasks currently. Seems like we also need to figure out what to do about that.

[mrubens]

Restated - what’s the action that we want the user to take when we warn them about the context? I think this could make a lot of sense if paired with a smol/compact action for instance, but would love to have a clear opinion on that.

[samhvw8]

Hey @samhvw8 I think we've chatted about this one and we're not quite sure about where the thresholds should be + it needs some UI polish. Those are the two big outstanding issues right now.

From @mrubens i move it to api profile

For Ui polish, can you help me and push commit direct to this pr ?

I will try to make it can dismis

[samhvw8]

Restated - what’s the action that we want the user to take when we warn them about the context? I think this could make a lot of sense if paired with a smol/compact action for instance, but would love to have a clear opinion on that.

Later we can show for them both compact and start new chat option ?

[samhvw8]

@sachasayan@cte@mrubens what do you think about this ?

https://www.loom.com/share/cbbeb3d93bfb4e918140da2663bf5601?sid=bbb221e6-a52b-4927-beea-cdea0d0b49b2

[mrubens]

I'm curious to see how #3582 plays out. If it works well, we may not need this from a cost/context management perspective. Though the PR description focuses more on client-side performance...

[samhvw8]

@mrubens ok so i just close this pr for now

[canrobins13]

Thanks for the inspo here! We added some version of this in #3582, which you can enable with the autoCondenseContext experimental feature.
Some follow up features are tracked in these issues:

• Add manual trigger button for context condensing #3671
• Allow users to configure the autoCondenseContext threshold #3672
• Add a UI element for context condense operations #3673