Troubleshooting
Choose the problem below. If the suggested steps do not help, collect a bug report for support or our Discord.
Which page do I need?
| Symptom | See |
|---|---|
| Plugin missing, "failed to load library", blank panel | Installation & Loading |
| Background service did not start, disconnected, cannot sign in | Connection & Server |
| Chat errors, restore-point failures, rate limits, billing or API keys | AI & Provider Errors |
| Ollama or LM Studio models missing | Local Providers |
| External tools fail or need sign-in | MCP Servers |
| Another AI app cannot use Ziva's Godot tools | Ziva as an MCP Server |
Finding your logs
If Ziva is stuck loading, type !logs in our Discord server for Windows, Mac,
and Linux instructions to find your logs, zip the whole folder, and upload it
without opening Ziva's chat or settings.
Logs help support understand what went wrong.
Exporting logs in one click (easiest)
Type /export-logs in the chat. Ziva creates a zip file and shows it in your file manager, ready to attach to a bug report.
Review logs before sharing them. They can contain project paths, errors and other details about your work.
Opening the logs folder
Open Settings → About → Open Logs Folder to find individual log files.
Optional: locate log files manually
Finding the folder manually
Replace <project-name> with your Godot project's name:
| System | Logs folder |
|---|---|
| Windows | %APPDATA%\Godot\app_userdata\<project-name>\ziva\logs\ |
| macOS | ~/Library/Application Support/Godot/app_userdata/<project-name>/ziva/logs/ |
| Linux | ~/.local/share/godot/app_userdata/<project-name>/ziva/logs/ |
The *_gdext.log file covers loading the plugin, *_sidecar.log covers chats and sign-in, and zivacode-crash.log records background-service startup crashes when present.
Collecting a bug report
Include:
- What you tried, what you expected and what happened.
- Your operating system and Godot version.
- Your Ziva version from Settings → About → Version.
- Your exported logs and any visible error message. Check them for private information before sharing.
Resetting Ziva to a clean state
Resetting removes this project's Ziva chats and settings. Try the relevant troubleshooting guide first, and export logs before resetting.
If Ziva shows Clear Data & Restart on a recovery or error screen, that action makes a backup, clears the saved data and restarts Godot. It keeps your Ziva sign-in and connected AI accounts. To sign out instead, use Log out in Settings → Account.
Advanced: reset when the panel cannot open
Manually
Close Godot. Find the ziva folder beside the logs folder listed above. Make your own backup before deleting it: manual deletion does not create the automatic backup and removes this project's Ziva chats and settings.
Check the project name and full path before running a command. Replace <project-name> with the correct name.
Windows (PowerShell)
Remove-Item -Recurse -Force "$env:APPDATA\Godot\app_userdata\<project-name>\ziva"macOS (Terminal)
rm -rf "$HOME/Library/Application Support/Godot/app_userdata/<project-name>/ziva"Linux (terminal)
rm -rf "$HOME/.local/share/godot/app_userdata/<project-name>/ziva"Reopen the project. Ziva downloads what it needs on the next launch. This does not sign you out of shared accounts.
Advanced: gather extra startup detail
Running Godot in verbose mode
If support asks for more detail, open a terminal and launch Godot with the command for your system. Replace the example Godot and project paths with your own.
Windows (PowerShell)
& "C:\path\to\Godot.exe" --verbose --editor --path "C:\path\to\your\project"macOS (Terminal)
/Applications/Godot.app/Contents/MacOS/Godot --verbose --editor --path "/path/to/your/project"Linux (terminal)
./Godot_v4.x --verbose --editor --path "/path/to/your/project"Reproduce the problem and include the relevant terminal errors in your report.
Last updated on
Share Web Builds
Export your Godot game to the web and share a play.ziva.sh link so friends can play it in their browser, on every Ziva plan.
Installation & Loading
Fix Ziva plugin loading problems in Godot: blocked native libraries on Windows Defender and macOS Gatekeeper, a blank plugin panel, and missing bundled tools.