Repository navigation
.Net - Agents: Consolidated User History in Group Chat #7316
Description
History management is required in order to keep maintaining chat conversations as eventually potentially irrelevant context is still sent, but more importantly context size will run out.
There needs to be an option to make the history mutable while still maintaining a single source of truth that is synced between the owning group chat and the participating agents.
It would make the most sense, for the source of truth to be the chat owner - which is the group chat object.
Specifically, this would fit for handling the required functionality needed to reduce / truncate the existing history at that level and then having that history propagate down to the agents.
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
madsbolaris commentedon Jul 17, 2024
Today, we have a group chat which is connected to an agent via a "channel". In the Assisatnts API implementation, the channel connects to a "thread" object in the Assistants API service. OpenAI is then able to use that "thread" to do truncation and other summarization logic.
If the "channel" for chat completion agents did something similar (e.g., a local thread), the developer could theoretically use that to do their own truncation and summarization that is separate from the "source of truth" in the group chat. Would that work for your needs?
[-]New Feature: Consolidated User History in Group Chat[/-][+].Net: New Feature: Consolidated User History in Group Chat[/+][-].Net: New Feature: Consolidated User History in Group Chat[/-][+].Net - Agents: Consolidated User History in Group Chat[/+]crickman commentedon Jul 17, 2024
Yes. As the history for a
ChatCompletionAgentgrows, the ability to truncate according to various strategies becomes increasingly useful.