What problem does it solve?
DeepChat stores provider keys, MCP settings, sessions, and chat history in local SQLite databases that may be SQLCipher-encrypted, making it hard for third-party tools to safely read, migrate, or analyze that data without corrupting a live profile.
Core Features & Use Cases
- Data Location & Snapshot Guidance: Locate
agent.db, legacy chat.db, WAL sidecars, and database-security.json across macOS, Windows, and Linux, with rules for safe read-only snapshots.
- Encryption Handling: Open SQLCipher-encrypted databases via Electron safeStorage unwrapping or manual password fallback, including guidance for Tauri and native importers.
- Schema & Import Recipes: Map providers, models, sessions, structured user messages, and assistant blocks into target app formats with secret-redaction checklists.
- Use Case: Build a migration tool that copies a user's DeepChat profile, unlocks the encrypted
agent.db, and exports all sessions and messages into another chat client's format.
Quick Start
Use the deepchat-data-import skill to help me write a tool that exports my DeepChat sessions and messages from agent.db into JSON.