QQ / NapCat / QQ Chat Exporter Handoff

Date: 2026-06-29

Goal

Run the user's normal QQ account and a separate bot QQ account without mixing sessions. Use the bot QQ account to export all accessible QQ group chat records, and optionally connect AI-assisted group replies with strict manual approval or safeguards.

Local Findings On Source PC

Main tool directory: D:\TH1_本地目录\Q群每日\聊天记录\Tools\NapCat-QCE-Windows-x64-v5.5.64\NapCat-QCE-Windows-x64
Full mode launcher: launcher-user.bat
Standalone browser-only mode: start-standalone.bat
Saved QQNT executable path: D:\Program Files\Tencent\QQNT\QQ.exe
QQ Chat Exporter Web UI: http://localhost:40653/qce-v4-tool
NapCat Web UI config file: config\webui.json
QCE plugin is enabled in: config\plugins.json
Current OneBot config files have no HTTP/WebSocket endpoints enabled: config\onebot11.json config\onebot11_3885485626.json
Previously exported records: D:\TH1_本地目录\Q群每日\聊天记录\072
Backup found: D:\TH1_本地目录\Q群每日\聊天记录\消息记录备份\3885485626的1个聊天记录.bak
User-level QCE data directory: C:\Users\daixiawu\.qq-chat-exporter

Recommended Execution On New PC

Do not run the user's main QQ and bot QQ in the same QQNT user data context if stability matters. Prefer one of:

Run main QQ normally on the desktop, and run bot QQ + NapCat under a second Windows user.
Run bot QQ + NapCat inside a virtual machine.
Only use same-session multi-open if the user accepts login-state conflicts and possible forced switching.

Install QQNT on the new PC.
Copy or re-download the NapCat-QCE package.
If the QQ path differs, run reset-qq-path.bat or pass the QQ.exe path to launcher-user.bat.

Start full mode:

cd /d "D:\TH1_本地目录\Q群每日\聊天记录\Tools\NapCat-QCE-Windows-x64-v5.5.64\NapCat-QCE-Windows-x64"
.\launcher-user.bat

Log in with the bot QQ account by QR/client login.
Open: http://localhost:40653/qce-v4-tool
Enter the access token printed in the console.
Select target groups, time range, and export format. JSON is best for later AI analysis; HTML is best for manual browsing.

AI Auto-Speaking Feasibility

Technically possible via NapCat OneBot, but currently not enabled in the found config. To implement later:

Enable OneBot HTTP or WebSocket endpoint in onebot11.json for the bot account.
Run a separate AI relay process that:
- receives group messages;
- filters by group whitelist and trigger rules;
- calls the AI model;
- either writes a draft for manual confirmation or sends with strict rate limits.
Prefer manual-confirm mode first. Full automatic group speaking can misfire, spam, violate group expectations, and risk account restrictions.

Prompt To Paste Into Codex On The New PC

I am continuing a handoff for QQ / NapCat / QQ Chat Exporter setup.

Context:

Need to run my normal QQ account separately from a bot QQ account.
Prefer bot QQ in another Windows user or VM to avoid QQNT session conflicts.
The source PC found a NapCat + QQ Chat Exporter package at: D:\TH1_本地目录\Q群每日\聊天记录\Tools\NapCat-QCE-Windows-x64-v5.5.64\NapCat-QCE-Windows-x64
Main launcher: launcher-user.bat
Web UI after startup: http://localhost:40653/qce-v4-tool
The launcher's first argument is a path to QQ.exe, not a QQ number.
Existing source PC saved QQ path was D:\Program Files\Tencent\QQNT\QQ.exe.
QCE plugin is enabled, but OneBot HTTP/WebSocket endpoints were empty, so AI auto-speaking is not active yet.

Please help me on this new PC:

Locate QQNT and the NapCat-QCE package.
Verify the launcher/config paths.
Start or tell me exactly how to start bot QQ login safely.
Help export all accessible group chat records.
If I ask for AI group replies, set up a conservative manual-confirm workflow first, not unrestricted auto-send.

3.9 KiB Raw Blame History