feat: restoring project from snapshot on reload

[thecodacus]

Add Chat History Snapshot System

Overview

This PR introduces a snapshot system for chat history, allowing the restoration of previous chat states along with their associated file system state. This feature improves the user experience by enabling users to resume work from specific points in their conversation history while maintaining context and workspace consistency.

Key Changes

1. Chat History Management

• Added snapshot storage and restoration functionality
• Implemented message filtering for hidden and no-store annotations
• Added support for archived messages
• Introduced chat index tracking for partial history restoration

2. File System Integration

• Added snapshot system for file system state
• Implemented file and folder restoration logic
• Added support for binary and text file handling
• Integrated with WebContainer for file system operations

3. UI Updates

• Added snapshot restoration messages
• Implemented hidden message filtering in the Messages component
• Added visual indicators for restored snapshots

4. Storage System

• Added new Snapshot type definition
• Implemented localStorage-based snapshot storage
• Added file system state serialization
• Introduced FileMap type for tracking file states

Technical Details

Snapshot System

• Stores chat index and complete file system state
• Handles both binary and text files
• Manages folder structure preservation
• Implements proper cleanup and restoration logic

Message Handling

• Added support for message annotations (hidden, no-store)
• Implemented archived message management
• Added snapshot restoration messages
• Improved message filtering logic

Testing

• Tested snapshot creation and restoration
• Verified file system state preservation
• Tested binary and text file handling
• Verified folder structure restoration
• Tested partial history restoration

Migration Impact

• No breaking changes for existing chat functionality
• Snapshots are stored separately from existing chat history
• Backwards compatible with existing chats
• No changes required for existing message handling

Future Improvements

• Add support for multiple snapshots per chat
• Implement snapshot cleanup mechanism
• Add snapshot management UI
• Improve restoration performance for large file systems

Preview

Snapshot.demo.mp4

[coleam00]

@thecodacus Nice work!! Honestly I already thought that this functionality existed mostly already where you could go back to previous conversations and it would already have everything loaded in. Is that not the case? When you went back to a previous chat it wouldn't actually load in the context from the file system?

Also, I would suggest changing the messaging from "Restoring chat from snapshot" to "Restored chat from snapshot", otherwise it seems like it is processing infinitely since the message never goes away. Maybe you could also have the code window open automatically as well?

Thank you for the work you're putting into this man!

[thecodacus]

hi @coleam00 , the purpose of this pr is to add snapshots.

the currently when you reload a chat all the actions are run again from scratch, and executes all the action in sequence to reconstruct the file system. and that includes all the writes and rewrites of the files. But with this the file system is restored and from a snapshot in one message at the start.

but when you restore from snapshot naturally llm looses all the actions from the pasts and looses the files context. this change also considers that it retains the project content as context after restoring

[thecodacus]

@wonderwhy-er , please test this you will love it. it retains the chat context even after snapshot.

but i might have to refactor some of the stuff i wrote here, what to get review before that

[wonderwhy-er]

Will try, holidays not letting me to computer
Will see

[flikites]

@wonderwhy-er , please test this you will love it. it retains the chat context even after snapshot.

but i might have to refactor some of the stuff i wrote here, what to get review before that

I can ttest this out if it hasn't been tested yet?

[siba2893]

When will this PR be tested and added to the core implementation?

[thecodacus]

I will be adapting this to the latest codebase.
I believe you will be able to see this as experimental optional feature in next few days

[leex279]

Works for me as described. Dont see any errors so far.