Use Logs, Diagnostics, and Reset

Open the app log

Goal

Collect recent technical details after reproducing a failure.

Before you start

Logs may include filenames, device information, model names, error text, and other context. Do not post them publicly without review.

Steps

1. Reproduce the problem once.
2. Open Settings → Advanced → Developer Options.
3. Under App Logs, select Open Logs.
4. Note the approximate time of the failure and copy only the relevant section when possible.

Expected result

The detailed application log opens in the system’s default text viewer.

If something goes wrong

If the log is empty or does not open, use Diagnostics report → Save report instead. The app log and audit log serve different purposes; the app log is normally more useful for chat, voice, and startup failures.

Save a diagnostics report

Goal

Create one text file describing the build, configuration, hardware, runtime state, and recent log activity for support.

Before you start

Privacy warning: Review the report before sending it. Local Waifu redacts license values, API keys, and Telegram tokens, but the report includes audio-device names and an app-log tail that is not fully content-filtered. Do not assume the UI phrase “No keys, no chat text” makes every line safe to publish.

Steps

1. Reproduce the issue.
2. Open Settings → Advanced → Developer Options.
3. Under Diagnostics report, select Save report.
4. Locate the revealed file named like diagnostics-YYYYMMDD-HHMMSS.txt.
5. Open it in a text editor.
6. Review every section, especially the recent app-log tail.
7. Remove or redact private text, usernames, paths, device names, prompts, or other details you do not want to share.
8. Attach the reviewed file to a private support message.

Expected result

A reviewed diagnostic text file is ready to send without exposing information you chose to remove.

If something goes wrong

If report creation fails, send the app version, platform, edition, exact error message, reproduction steps, and a reviewed excerpt from App Logs instead.

Reset all application data

Goal

Return the main application database and local content to a fresh state when repair is impossible or when intentionally starting over.

Before you start

Destructive action: Reset All is irreversible from within Local Waifu. Create a backup and export any characters you want to keep.

The reset deletes the database, characters, conversations, memories, soul files, portraits, generated images, voice references/clones, and local settings. It does not automatically remove the Direct license/trial record, cloud provider keys, connected-account credentials, or Telegram token from the secret store.

Steps

1. Create a full backup and verify its folder, file count, and size.
2. Export important characters separately.
3. If you also want credentials removed, delete provider keys and use Settings → Telegram → Forget token + pin first.
4. Open Settings → Advanced → Developer Options.
5. Find Reset Database and select Reset All.
6. At Sure?, select Yes, delete.
7. Wait for All data deleted.
8. Quit and restart Local Waifu as instructed.

Expected result

The main app data is cleared, and the application starts in a fresh state after restart. License, trial, provider, or Telegram credentials may remain unless removed separately.

If something goes wrong

• Do not repeat the reset if the app appears partially initialized; quit and reopen it first.
• Do not attempt to copy a backup into the live data directory while Local Waifu is running.
• There is no complete Restore UI in version 1.7.3. Preserve the backup and contact support for a full restore procedure.

---