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
{{ message }}
Repository navigation
recommendations for bashkit snapshot deltas / patches #2221
We are currently building out session (conversation) persistence in our product. Our agents have access to bashkit, and for each session, we store a bashkit snapshot containing the most recently saved state of bash and the file system. We support features such as truncation of existing sessions for rewinding conversations and branching of existing sessions from particular points in the conversation. Ideally, we would like to have a snapshot of the state of bash and the file system every time bash is run and the bashkit snapshot state changes to ensure that truncated and branched sessions have accurate and up-to-date snapshots. Currently, however, we have traded off correctness for space by only storing the most recent bashkit snapshot to the database.
Is there a way to store a smaller deltas or incremental patches of a snapshot that would allow us to accumulate deltas and patches on top of one another to get the final snapshot? This would enable us to store a full history of bash and the file system as it changes over the course of the conversation, which would facilitate truncation and branching of sessions without compromising on correctness.
There is no patching or delta for snapshots yet. However this came up already couple of times. I think it is good time to attempt to fill the gap. Let me look into this tomorrow, my best guess most challenging might be file system, we have users working with quite large image files.
Incremental snapshots are released in last version. Closing this issue for now. Ping me if something missing or feel free to reopen, I am committed to support this feature.
Also just in case, depending on how you plan to deploy this, there is version 14.5 with forward compatibility.
Activity
chaliy commentedon Jul 30, 2026
There is no patching or delta for snapshots yet. However this came up already couple of times. I think it is good time to attempt to fill the gap. Let me look into this tomorrow, my best guess most challenging might be file system, we have users working with quite large image files.
axiomofjoy commentedon Jul 30, 2026
Thanks @chaliy
feat(snapshot): content-addressed history with forks and binary deltas
chore(knowledge): propose snapshot history, forks, and content deltas
feat(snapshot): content-addressed history with forks and binary deltas
chaliy commentedon Jul 31, 2026
@axiomofjoy can you pls validate that imlementation in #2223 cover your needs?
Here is Calude generated example for your original work - #2223 (comment)
axiomofjoy commentedon Jul 31, 2026
Thanks @chaliy I'll have Claude put something together
feat(snapshot): read the v2 container without writing it (#2226)
chaliy commentedon Aug 4, 2026
Incremental snapshots are released in last version. Closing this issue for now. Ping me if something missing or feel free to reopen, I am committed to support this feature.
Also just in case, depending on how you plan to deploy this, there is version 14.5 with forward compatibility.