I would like to request an optional feature to encrypt LM Studio chat history at rest and protect access to it with a user-defined password or passphrase.
Use case
I sometimes work with sensitive prompts and responses on a local machine. While LM Studio is primarily a local/offline application, local chat history may still be readable by someone who gains access to the device, user profile, backup files, or the underlying chat storage.
This feature would help protect sensitive conversations against offline access to local chat files. I understand that it would not be intended to protect against malware, an already-unlocked user session, or a fully compromised operating system.
Suggested behavior
- Users should be able to enable encrypted chat history in settings.
- When enabled, LM Studio should require a password/passphrase on app launch or before opening chat history.
- Local chat history should be encrypted at rest and only decrypted after successful authentication.
- Existing chat history should be encrypted when the feature is enabled.
- Users should be able to change the password later, with existing chats re-encrypted accordingly.
- Disabling the feature should require authentication and explicit confirmation.
- If the password is forgotten, LM Studio should make it clear that encrypted chat history cannot be recovered unless a recovery mechanism is explicitly provided.
- Optionally, LM Studio could support secure export/import of encrypted chat archives.
Why this would help
- Better protection for sensitive conversations on shared, lost, or stolen devices.
- Improved privacy for users working with confidential prompts, responses, source code, business data, or personal information.
- A stronger local security model without affecting users who do not need this feature.
- More confidence for professional users who rely on LM Studio for private or offline workflows.
I would appreciate consideration of this feature for a future release.
I would like to request an optional feature to encrypt LM Studio chat history at rest and protect access to it with a user-defined password or passphrase.
Use case
I sometimes work with sensitive prompts and responses on a local machine. While LM Studio is primarily a local/offline application, local chat history may still be readable by someone who gains access to the device, user profile, backup files, or the underlying chat storage.
This feature would help protect sensitive conversations against offline access to local chat files. I understand that it would not be intended to protect against malware, an already-unlocked user session, or a fully compromised operating system.
Suggested behavior
Why this would help
I would appreciate consideration of this feature for a future release.