-
Notifications
You must be signed in to change notification settings - Fork 1.3k
History Cleaning #545
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Couldn't you truncate the |
yeah but what i want is that when i call an agent as tool i can select whats the input that sends the "orchestrator" agent to the following agent |
You can do that already. For example:
Would that work? |
but can i select a subset of the general history? with the Runcontextwrapper or something like that? |
Oh hmm, no. That's only available for handoffs. We could/should add this to the context, as you requested. PR welcome, otherwise I can get to it at some point. |
@rm-openai It would be helpful if there was a built-in feature to compress the history after it reaches a certain size threshold. A la |
We need a way to manage context more precisely. In the current implementation, every call, tool invocation, and handoff is appended to the history, but we can’t control how many—or which—items are sent to the LLM each turn (e.g., only tool calls, only messages, only handoffs, or any combination).
It would also be helpful to add a sliding‑window history selector that retains only the last ten turns of conversation. That way, tools could leverage both short‑term (fast) and long‑term (slow) memories as needed.
What dou you think? How are you currently handling history needs?
The text was updated successfully, but these errors were encountered: