Deepchat Data Import
Developmentdeepchat-data-importDeepchat Data Import is an Agent Skill for development published in the ThinkInAIXYZ/deepchat repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Help developers build third-party tools that import, inspect, migrate, or analyze DeepChat data. Use when Codex needs to work with DeepChat provider configuration, model configuration, MCP/app settings, sessions, messages, legacy chat data, `agent.db`, `chat.db`, SQLCipher encrypted SQLite, Electron safeStorage wrapped passwords, Tauri importers, or native macOS/Windows/Linux data access.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/ThinkInAIXYZ/deepchat/blob/HEAD/.agents/skills/deepchat-data-import/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/deepchat-data-import, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
DeepChat Data Import
Overview
Use this skill to design or implement importers for DeepChat local data. Treat DeepChat's SQLite schema as an internal but documentable contract: inspect the current schema when precision matters, prefer read-only snapshots, and avoid writing to a live profile.
Workflow
- Identify the source: live DeepChat profile, copied profile, sync backup, exported
agent.db, or legacychat.db. - Read references/data-locations.md to locate
agent.db, sidecar files, encryption metadata, and backup paths. - Read references/sqlite-access.md before opening SQLite. Decide whether the database is unencrypted, can be unlocked through Electron safeStorage, or must ask the user for the SQLite password.
- Read references/schema-reference.md for provider config, settings, session, message, and legacy table relationships.
- Read references/import-recipes.md when writing extractor code, mapping DeepChat data to another app, or creating a compatibility import.
Safety Rules
- Get explicit user consent before reading local DeepChat data. Provider keys, OAuth tokens, MCP env vars, prompt text, message traces, and chat content may be sensitive.
- Never open the active
agent.dbread-write from a third-party tool. Copyagent.db,agent.db-wal, andagent.db-shm, or use SQLite backup APIs through DeepChat itself. - If DeepChat is running, either ask the user to quit it or make a WAL-aware snapshot before import.
- Prefer parameterized key APIs for SQLCipher passwords. Do not interpolate passwords into SQL.
- Redact secrets by default in logs, telemetry, previews, and generated sample output.
- When the schema has changed, inspect
schema_versions,sqlite_master, and the table classes undersrc/main/presenter/sqlitePresenter/tables/before assuming column availability.
Source Files
Use these repository files as the current source of truth when updating the skill or answering version-sensitive questions:
src/main/presenter/sqlitePresenter/index.tssrc/main/presenter/sqlitePresenter/connectionConfig.tssrc/main/presenter/databaseSecurityPresenter/index.tssrc/main/presenter/sqlitePresenter/tables/*.tssrc/main/presenter/agentRuntimePresenter/messageStore.tssrc/main/presenter/agentRuntimePresenter/sessionStore.tssrc/main/presenter/configPresenter/**