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
I'm currently looking for workarounds in order to retain chat session memory with Runner and Agents. I read through #248 and at the moment my two primary options are: manually saving messages in a database, reverting to Assistants. For the purposes of the web app I'm engineering, we've already begun efforts to move away from Assistants and towards the newer, more responsive Agents + Runner implementation.
I would like to know if there would potentially be features implemented dedicated towards session memory in the Runner objects, much like Assistants have threads for conversations.
The text was updated successfully, but these errors were encountered:
Hi,
I'm currently looking for workarounds in order to retain chat session memory with Runner and Agents. I read through #248 and at the moment my two primary options are: manually saving messages in a database, reverting to Assistants. For the purposes of the web app I'm engineering, we've already begun efforts to move away from Assistants and towards the newer, more responsive Agents + Runner implementation.
I would like to know if there would potentially be features implemented dedicated towards session memory in the Runner objects, much like Assistants have threads for conversations.
The text was updated successfully, but these errors were encountered: