Session Time Travel and Forking #343
Description
I'm working on a custom coding agent and this is a feature I want to have. It is unclear where this support should live. Some thoughts and questions
- Having this feature in ADK generally seems really useful across every downstream application
- It could facilitate making better testing data for evals, synth or hand crafted
- It would have implications for how this is supported in the other services (like Artifacts), namespacing, but also linking?
- Sessions should ideally remain accurate when loading later on. This would mean having a snapshot of the app & user state at the time they were created would be needed, if they use or modify, for their inputs and deltas to remain stable long term
- Is this possible today without changes to ADK? I think so, but requires some forethought for said namespacing to avoid collision with users and/or sessions. I'll let you know what I learn!
At some point it starts to sound like git, container layers, crdt, deltadb on a per-session basis, OCI intrigues me in this regard