Fix common problems
How do I troubleshoot a failed download or model run?
It depends on the failure shown by the app. Read the download status, confirm the file checksum if available, and retry only when the server says it is available. For memory errors, select a smaller exact file; for a launch error, check the runtime and file format. Keep the error message and file name for diagnosis.
RAM is working memory while a model runs; disk space stores the downloaded file. A partial download is incomplete. A checksum mismatch means the bytes differ from the recorded fingerprint; a runtime error occurs when software cannot load or run the selected file.
Service status reports site availability. Inspect the exact model file and recorded hash beside its run-readiness evidence; a receipt applies only to its named file and setup. This troubleshooting guide is not itself a test receipt.
Updated · Page-copy source revision 8871bab84e1cf80aea1686a944ec335078a6c036 · Source files: apps/web/lib/help-centre-content.mjs, apps/web/lib/help-centre-legacy.mjs, apps/web/lib/aeo-page.mjs · Full revision record
Key facts
- Desktop app
- Installed locally; each model file is a separate download with its own hash check.
- Checked label
- Means bytes matched a published SHA-256 on this computer; not a safety guarantee.
- Fit estimate
- Compares file size to memory; it is not a measured run or speed promise.
- Service status
- /status reports site probes; it does not diagnose your local runtime.
Evidence you can inspect (plain text)
- GET /api/status.json reports current service probe results (samples, not uptime guarantees).
- /verification lists steps to compare a downloaded file to its recorded hash.
- Open /artifact/hf-model-qwen-qwen3-8b/files for model exact filenames, availability and any recorded SHA-256.
- Open /evidence/artifacts/hf-model-qwen-qwen3-8b for run-readiness evidence tied to that record; absent receipts stay unmeasured.
- Open /api/artifacts/hf-model-qwen-qwen3-8b/card.md for machine-readable source facts (not a runtime test).
- A run receipt on the evidence page applies only to the file and setup named there.
Unmeasured states are stated explicitly; this page does not invent run scores or compatibility guarantees.
Which date applies to which fact
- Committed page-copy sources:
- Upstream model metadata: Dates on artifact records when shown; not implied by page-copy revision
- Run receipts: Only on /evidence pages when recorded; otherwise unmeasured
Page-copy revision (Updated line above) identifies committed text sources, not upstream model edits or test outcomes.
Not enough memory
If chat stops for memory, accept Switch to a smaller model when offered, or pick a smaller file under Fits my computer in Discover.
Download stuck or slow
- Open Downloads and read the status on the failed or paused row.
- Choose Check what's wrong when offered.
- Try another network if you can, then retry. Resume works only when the server supports it.
- If the file is marked unavailable, pick another model.
App won't open on Linux
- Confirm you downloaded Linux x86_64 from the desktop page for Ubuntu 22.04+ or Debian 12+.
- Run the SHA-256 check from the download page. Re-download if it does not match.
- For AppImage: run the make executable and run commands listed beside the file.
- If the window never appears, launch from a terminal to read the error, and check whether your distro needs libfuse for AppImage.
- For .deb: install with the listed sudo command, then open the app from your applications menu.
More
Hash mismatch: delete the partial file and download again. macOS Gatekeeper: drag to Applications and use Open Anyway for a trusted test build. Slow replies: wait for the first load, try a smaller model, or choose Stop then try again.
Common questions
A download is stuck. What first?
Open Downloads, read the status row, and use Check what's wrong when offered.
Linux AppImage does nothing.
Confirm SHA-256, run the make executable command from the download page, and check FUSE or sandbox settings for your distro.