How should I keep DeepSeek Web login profiles separate between the full studio and Conversation Capture?

[rayfon99999]

I want to use both DeepSeek Translation Studio and the standalone DeepSeek Conversation Capture on the same Windows machine.

From the README and docs/DEVELOPMENT.md, I can see that the full app and the standalone capture app use different runtime data folders. I want to confirm the recommended setup before I start switching DeepSeek Web accounts:

1. Should the full app and Conversation Capture always use separate browser profiles?
2. When should I override DST_APP_DATA_DIR or DCC_APP_DATA_DIR?
3. Is it safe to use the "Switch Web Account" button while a Web capture task is running?
4. For portable packages, should I copy only the .exe, or keep the whole generated folder?

I am mainly trying to avoid mixing login state, SQLite history, and logs between the translation workflow and the daily conversation capture workflow.

[NextWeb4]

Yes, keep them separate.

The full app and the standalone capture app intentionally use different runtime data roots:

• Full studio: %LOCALAPPDATA%\DeepSeekTranslationStudio
• Conversation Capture: %LOCALAPPDATA%\DeepSeekConversationCapture

Each data root can contain its own SQLite database, logs, and Playwright browser profile. That separation prevents a normal translation/SRT workflow from sharing state with the stripped daily conversation capture workflow.

Use DST_APP_DATA_DIR only when you want to move the full studio runtime data somewhere else:

$env:DST_APP_DATA_DIR="D:\Codex\DPSK\.runtime"
python main.py

Use DCC_APP_DATA_DIR only for the standalone capture app:

$env:DCC_APP_DATA_DIR="D:\Codex\DPSK\.conversation-runtime"
python conversation_main.py

Do not switch Web accounts while a Web task is running. The account switch flow moves the current browser_profile into browser_profile_backups and creates a fresh empty profile, so it should only run when no translation or capture job is using the browser profile.

For packaged builds, keep the whole generated application folder. Do not copy only the .exe, because Web mode also needs the bundled _internal files, including Playwright driver files and Chromium. For portable packages, use the included Start Portable.bat; it points the runtime data to the package-local data folder so login state, SQLite, and logs stay with that portable copy.