Add virtual IO layer with content-addressed storage for parallel sessions #85
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In-memory virtual file system enabling isolated, parallel session file operations without disk interaction. Uses SHA-256 content addressing for automatic deduplication across sessions.
Architecture
New types in
paws_domain::virtual_fsObjectId— SHA-256 content hash, analogous to git blob IDsObjectStore— Thread-safe deduplicated blob store (DashMap<ObjectId, Bytes>)SessionFS— Per-session overlay mapping paths →ObjectId, with snapshot stack for undoVirtualFileSystem— Multi-session orchestrator;DashMapfor cross-session concurrency,tokio::sync::Mutexper sessionSessionId— UUID-based session identifierUsage
Sessions are fully isolated — writes in one session are invisible to others. Identical content across sessions is stored once via content addressing.
Dependencies added to
paws_domainsha2(workspace),dashmap(workspace),bytes(workspace)Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.