Agents can save data in instance storage or in session storage. The instance storage writes would go to directly under .typeagent\profiles\dev. This location is useful for configuration data that will persist across sessions. Agents could also save data in the session storage at .typeagent\profiles\dev\sessions\<sessionID>. This location is useful for caches and other ephemeral data that should be reset if user creates a new session e.g. via @session new.
With the new server-sessions, we now have an additional layer .typeagent\profiles\dev\server-sessions\<server-sesion-id> which has the folders that were in instance storage and .typeagent\profiles\dev\server-sessions\<server-sesion-id>\sessions\<sessionID> which has the content that was in session storage. The server-sessions are created automatically. Whenever a new server-session is created, we are resetting instance storage, resetting any user customizations etc. that we expected to keep across sessions.
Agents can save data in instance storage or in session storage. The instance storage writes would go to directly under
.typeagent\profiles\dev. This location is useful for configuration data that will persist across sessions. Agents could also save data in the session storage at.typeagent\profiles\dev\sessions\<sessionID>. This location is useful for caches and other ephemeral data that should be reset if user creates a new session e.g. via@session new.With the new server-sessions, we now have an additional layer
.typeagent\profiles\dev\server-sessions\<server-sesion-id>which has the folders that were in instance storage and.typeagent\profiles\dev\server-sessions\<server-sesion-id>\sessions\<sessionID>which has the content that was in session storage. The server-sessions are created automatically. Whenever a new server-session is created, we are resetting instance storage, resetting any user customizations etc. that we expected to keep across sessions.