feat: better context management #2573

Closed
opened 2025-11-11 15:09:53 -06:00 by GiteaMirror · 0 comments
Owner

Originally created by @Eureka-0 on GitHub (Nov 5, 2024).

Feature Request

Is your feature request related to a problem? Please describe.
As an OpenAI API user, I often don't need much context (usually 4 or fewer), since longer contexts increase the cost. This situation likely applies to most of OpenAI or Claude API users. Therefore, implementing built-in context management would be beneficial, with good examples like LobeChat providing inspiration.

Describe the solution you'd like
A built-in context management based on conversations, and allow me to change its value at any time.

Describe alternatives you've considered
I tried using the "context clip filter" function, but found it inconvenient. To use this function, I have to create a new model specifically incorporating it. Additionally, if I change the history message value of this function, it affects all ongoing conversations that use the model. This makes it difficult to manage multiple conversations with different history message values.

Additional context
Take LobeChat's context management capabilities as an example:

image image
Originally created by @Eureka-0 on GitHub (Nov 5, 2024). # Feature Request **Is your feature request related to a problem? Please describe.** As an OpenAI API user, I often don't need much context (usually 4 or fewer), since longer contexts increase the cost. This situation likely applies to most of OpenAI or Claude API users. Therefore, implementing built-in context management would be beneficial, with good examples like LobeChat providing inspiration. **Describe the solution you'd like** A built-in context management based on conversations, and allow me to change its value at any time. **Describe alternatives you've considered** I tried using the "context clip filter" function, but found it inconvenient. To use this function, I have to create a new model specifically incorporating it. Additionally, if I change the history message value of this function, it affects all ongoing conversations that use the model. This makes it difficult to manage multiple conversations with different history message values. **Additional context** Take LobeChat's context management capabilities as an example: <img width="322" alt="image" src="https://github.com/user-attachments/assets/404ffc25-b55a-4308-a0a1-e9c21f28e241"> <img width="296" alt="image" src="https://github.com/user-attachments/assets/c6bce917-97e9-4d13-b690-c58d2c459be0">
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#2573