Zeroboot's support for persistent sandbox/workspace data.

Hi,

First of all, thank you for open-sourcing Zeroboot. The copy-on-write VM forking approach is very interesting, especially for AI-agent workloads.

I had a question about the roadmap: are there any plans to support persistent sandbox or workspace data in the future?

From my reading of the repository, Zeroboot currently seems optimized for extremely fast ephemeral execution from a prebuilt snapshot, which makes a lot of sense for short-lived isolated tasks. I was wondering whether you are also considering a model where users could preserve state across executions, for example:

- persistent workspace directories
- writable volumes mounted into sandboxes
- snapshot/restore of user workspace state
- resumable sessions instead of fully ephemeral forks

I’m asking because this would make Zeroboot much more compelling for longer-running agent workflows, coding environments, and iterative development tasks.

If this is already being considered, I’d be very interested to know:
- whether persistence is part of the planned roadmap
- what form you think it might take
- whether the current architecture is intended to support that eventually

Thanks again for the project.