Troubleshooting
Common issues and their fixes. If something here doesn’t help, check the FAQ or open an issue on GitHub.
The AppImage won’t launch
Section titled “The AppImage won’t launch”The AppImage needs FUSE. If it isn’t installed, extract and run instead:
./Nexis-*.AppImage --appimage-extract-and-runRendering glitches on Wayland
Section titled “Rendering glitches on Wayland”Try disabling the DMABUF renderer:
WEBKIT_DISABLE_DMABUF_RENDERER=1 ./Nexis-*.AppImageOn desktop Linux the .deb / .rpm builds are generally smoother than the
AppImage.
“Nexis can’t be opened” (Gatekeeper)
Section titled ““Nexis can’t be opened” (Gatekeeper)”Nexis isn’t notarized yet. Right-click Nexis in Applications → Open, then confirm. You only need to do this once. See macOS install.
Windows
Section titled “Windows”SmartScreen blocks the installer
Section titled “SmartScreen blocks the installer”Nexis isn’t code-signed yet, so SmartScreen may warn on first run. Click More info → Run anyway. See Windows install.
Wrong shell opens
Section titled “Wrong shell opens”Nexis detects shells in the order pwsh.exe → powershell.exe → cmd.exe.
Install PowerShell 7+ if you want pwsh to be picked first.
The AI panel can’t reach my model
Section titled “The AI panel can’t reach my model”- Cloud provider — confirm the key is set under Settings → AI and the provider is selected. Keys live in the OS keychain.
- Local model — check that LM Studio / MLX / Ollama is running and that the endpoint URL in settings matches. See AI providers.
Crashes
Section titled “Crashes”Nexis wraps each pane in a React error boundary — if one pane’s render crashes, the rest of the UI stays live and the failed pane shows a Try again reset. If crashes persist, please file an issue with the details.