System Self-Check & Feedback
When something goes wrong with software, the hardest part is often "explaining exactly what's off." The self-check lays out the state of your runtime environment for you to see; feedback lets you send the problem (along with that state) straight to me. Both entry points live on the About page.
System Self-Check
Open About → System Self-Check, and Nephele runs a full health check, giving each item one of three states: Ready / Attention / Missing. There's also a one-line summary at the top (for example, "All ready" or "2 items missing").
The check covers these areas:
- Device: operating system, CPU, memory (you'll get a warning below 8 GB), graphics acceleration (whether the GPU, VRAM, and inference acceleration are available), display resolution and scaling, free disk space
- Runtime environment: build type and version, Python runtime, language, integrity of bundled resources
- Local AI: whether the local image models are in place, how much space they take, whether the dependency components are complete, whether the browser engine is available
- Network: cloud node latency and reachability, your network location and entry node, direct internet connectivity, whether you're going through a proxy / VPN
- Extensions & connectivity: Wisp extension bridge status, Aura phone connection status
- Account: login status, license tier and validity period, device fingerprint
One-Click Fix
For a few common problems, a "Fix" button appears next to the self-check result—one click and it's handled:
| Problem | What the one-click fix does |
|---|---|
| Wisp bridge not registered | Re-registers the browser extension bridge (restart your browser once afterward) |
| Phone connection dropped | Reconnects to the Aura relay |
| Missing component / file | Triggers an update check and automatically fills in what's missing |
提示
One-click fixes are all conservative operations—they won't wipe your data or force a reinstall. For large downloads like models or the browser engine, the self-check won't quietly fetch them for you—those need a progress bar and are your call to make.
Feedback
Open About → Feedback and write down the problem or suggestion you've run into:
- Pick a category: Problem / Suggestion / Other
- Write the body (up to 4,000 characters)
- You can check "Include system self-check info and runtime logs"—attaching that runtime state from above (already redacted) helps me troubleshoot much faster
Once you submit, it reaches me (with your account, version, and system info attached so I can pinpoint things). The fix gets pushed to you in a later update.
技巧
Feedback requires you to log in first (so I can get back to you once it's fixed). The self-check itself doesn't require a login.
Next Steps
- Getting Started — requirements and first launch
- How I Handle Your Data — how feedback and diagnostic info are handled