You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi - I have a big issue trying to manage context during long runs where the gframework internally manages all tool iterations.
Hoping someone can point me in the right direction
Is there an intended hook point between tool iterations? e.g., an IToolCallInterceptor, a middleware delegate, or
an event on ChatClientAgent?
Can ChatClientAgentOptions expose a per-iteration callback (before/after each tool-call round)?
Is IChatReducer intended to fire more than once per RunAsync? The current behavior (once only, before the first LLM
call) makes it useless for long tool runs.
Is there a DelegatingChatClient hook point that fires between iterations inside the native loop?
I added post-stream compression, but it's not enough, and I cannot see a way to implement a hook that will help prevent a single 15-tool run from killing the conversation.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi - I have a big issue trying to manage context during long runs where the gframework internally manages all tool iterations.
Hoping someone can point me in the right direction
an event on ChatClientAgent?
call) makes it useless for long tool runs.
I added post-stream compression, but it's not enough, and I cannot see a way to implement a hook that will help prevent a single 15-tool run from killing the conversation.
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions