Troubleshooting and recovery

Start with the specific failed operation. An unavailable engine or provider does not make the project’s ordinary files unusable.

The editor or renderer is unavailable

GDE’s document and visual surfaces need the Evergreen WebView2 Runtime. Open Settings → Tools → WebView2 Runtime, recheck it and use the official Microsoft download action when it is missing. An Edge preview channel alone is not the required runtime.

After installation, reopen GDE. If the renderer crashed, preserve any available draft or recovery copy first. Text already received by the application can be retained; an unacknowledged renderer edit and its JavaScript undo history cannot be guaranteed after that renderer fails.

Settings and project navigation remain the entry points for recovery. Do not delete the project or all application state to repair a renderer.

A file changed outside GDE

Keep your draft open. Inspect the newer disk version before retrying a save. Use File → Save a copy if you need to preserve both versions. Choose Reload from disk only when you intend to replace the current draft with the file on disk.

A file conflict is about source versions, not a reason to create a duplicate project.

Visual edits have not saved

Markup, map and canvas edits can remain visible while saving. After a failure, the failed operation and later queued gestures are retained together.

Use the offered retry only when the original source still matches. If it changed, use Save retained copy to preserve the edits separately, then compare the versions. Reload or discard only when you no longer need the retained work.

A changed background image also needs an explicit relink. Moving an arrow cannot resolve an image-identity conflict.

Git is unavailable or the repository changed

Check the installed Git tool and the project root. Refresh the repository view. A cached status is the last observation, not current confirmation.

If Update cannot fast-forward while preserving work, resolve that condition with the project’s normal Git workflow. GDE does not silently stash, force-push or manufacture a merge to get past it. Preserve unsent commit writing before switching tools.

GitHub is unavailable or delivery is uncertain

Check Settings → Connections → GitHub and the repository access of the existing CLI account. Cached issues may remain readable while refresh is unavailable.

If an issue or comment submission is uncertain, use its delivery check before sending again. A published issue can exist even when a later board-placement or refresh step failed. Keep the retained draft until that outcome is resolved.

When a remote issue changed during editing, review the latest version before applying your changes.

Director or a Run cannot continue

Check the Codex connection and the existing conversation or Run. Refresh its observed state. A missing working copy, changed branch or unavailable provider thread needs attention; opening the Run does not create a replacement automatically.

Do not resend an uncertain message until its delivery has been checked. Continue local writing while the provider is unavailable.

An engine requirement is Missing or Unknown

Confirm the selected binding and the exact operation. Check the installed editor path, project descriptor, target and required toolchain or modules. Unknown means the check could not establish the fact; it is not proof that a tool is absent.

Use vendor setup for licenses, accounts and installations. Recheck Requirements after addressing the named condition. Project and engines explains the scope.

A result is stale, changed or incomplete

Open the Run’s details and compare its recorded source and output with the current files. Restore the intended artifact or produce a new result from the intended inputs.

Do not substitute the ordinary project launcher for a Run’s exact output. Supporting files matter: an EXE alone may not be a complete game. Results and evidence lists the distinctions.

Report a repeatable failure

Record the operation, expected result, observed message and whether it happens in a fresh example copy. Keep any retained input. Inspect the application’s diagnostic report before sharing it, and avoid including private project content or credentials in screenshots.