fix: move context condensing prompt to Prompts section (#4924)

[SannidhyaSah]

Description

Fixes #4924

This PR moves the "Context condensing prompt" setting from the Context Management section to the Prompts section in the settings UI. Additionally, it fixes a visibility issue where the prompt was incorrectly hidden when auto-condensing was disabled.

Changes Made

• Moved the Context Condensing section from ContextManagementSettings.tsx to PromptsSettings.tsx
• Updated props passing in SettingsView.tsx to provide the necessary settings to the Prompts component
• Fixed visibility logic - the prompt is now always visible regardless of the auto-condensing setting
• Updated unit tests in ContextManagementSettings.spec.tsx to reflect the component changes
• Added missing translations for the new "contextCondensing" section in all 17 language files

Testing

• All existing tests pass (2534 tests)
• Updated unit tests for ContextManagementSettings component
• Manual testing completed:
  • Verified the Context Condensing section appears in Prompts settings
  • Confirmed the prompt is always visible regardless of auto-condensing state
  • Tested that changes to the prompt are properly saved

Verification of Acceptance Criteria

• Context condensing prompt has been moved to the Prompts section
• The prompt is always visible (visibility issue fixed)
• All translations are complete for all 17 supported languages
• No breaking changes - settings continue to work as expected

Checklist

• Code follows project style guidelines
• Self-review completed
• Comments added for complex logic
• Documentation updated (if needed)
• No breaking changes
• Accessibility checked (for UI changes)

---

Important

Moves context condensing prompt to Prompts section and fixes visibility issue, updating tests and translations accordingly.

• Behavior:
  • Moves "Context condensing prompt" from ContextManagementSettings.tsx to PromptsSettings.tsx.
  • Fixes visibility issue: prompt is now always visible, regardless of auto-condensing setting.
• Code Changes:
  • Updates SettingsView.tsx to pass necessary props to PromptsSettings.
  • Removes context condensing logic from ContextManagementSettings.tsx.
• Testing:
  • Updates unit tests in ContextManagementSettings.spec.tsx to reflect changes.
• Translations:
  • Adds missing translations for "contextCondensing" in 17 language files.

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

[daniel-lxs]

I think a better approach would be to keep the condensing settings where they are but add the prompt to the Prompts section here:

That way you can turn it on or off in the usual place but also change it on the Prompts section and have it reflect the changes in the Context section as well.

Let me know what you think.

[SannidhyaSah]

I think a better approach would be to keep the condensing settings where they are but add the prompt to the Prompts section here:

That way you can turn it on or off in the usual place but also change it on the Prompts section and have it reflect the changes in the Context section as well.

Let me know what you think.

I see your point about centralizing the on/off switch. However, the new implementation is a crucial fix for a significant UX issue in the old design.

The main problem was that the checkbox for automatic condensing also locked the settings for manual"condensing. Many users want to fine tune the prompt or API for manual use without having the feature trigger automatically, and the old design made this impossible and you had to check the checkbox to do that.

By giving context condensing its own section in the prompt panel, we have solved that problem entirely. It creates a clear distinction from the other prompts and allows users to configure it for manual use without affecting any automatic settings. If we were to move the settings back behind the checkbox, we would reintroduce that initial frustration for users.

Let me know your thoughts.

[SannidhyaSah]

@daniel-lxs I've made a few changes . Restructured it properly. Should be good now .

The backend isn't really changed much, so old prompts shall be migrated here easily.

[daniel-lxs]

I noticed that along with moving the context condensing prompt to the Prompts section, you've also moved the API configuration selector for context condensing.

Could we keep the API configuration selector in the Context Management section and only move the prompt itself to the Prompts section? This would maintain better separation of concerns - the Context Management section would control when and how condensing happens (including which API to use), while the Prompts section would only control what the condensing prompt says.

This approach would be more consistent with how other settings are organized and would avoid duplicating configuration options across sections.

[SannidhyaSah]

Thanks for this PR! I noticed that along with moving the context condensing prompt to the Prompts section, you've also moved the API configuration selector for context condensing.

Could we keep the API configuration selector in the Context Management section and only move the prompt itself to the Prompts section? This would maintain better separation of concerns - the Context Management section would control when and how condensing happens (including which API to use), while the Prompts section would only control what the condensing prompt says.

This approach would be more consistent with how other settings are organized and would avoid duplicating configuration options across sections.

Thank you for the feedback—that's a very valid point.

My rationale for the current implementation was twofold:

Consistency: I wanted to align this feature's user experience with the existing 'Enhance Prompts' setting, which uses a similar interaction pattern. This helps create a more consistent and predictable interface for users.

Clarity & Separation of Concerns: This approach allowed for a clean separation of the settings into two distinct logical groups: one dedicated purely to 'automatic' condensing that is now present in the context tab under a checkbox and another that governs both manual and automatically combined condensing actions. This distinction isn't just beneficial from a code structure perspective; it also provides users with a clearer mental model of how the different settings operate.

While I believe this structure has its merits, I see the validity of your point as well. Let me know what you think is the best path forward. I'm happy to go with whichever approach we agree makes the most sense.

[daniel-lxs]

Thank you @SannidhyaSah!