dsh-godot-play

Iterating on Godot Web exports inside the DeepSeek Harness Web GUI used to mean running godot --headless --export-release by hand, spinning up a static server, and wrangling port conflicts and cross-origin isolation headers. dsh-godot-play collapses all of that into a single floating panel: pick a project, hit build, watch the log scroll, and the iframe reloads with a cache-busting stamp ready to play. No standalone port, no resident sidecar, zero framework dependencies.

The host half injects webServer, subprocess, webRuntime, and workspaceRegistry on demand. It auto-discovers directories containing project.godot in the workspace, follows the Web export preset's export_path to locate the output, and serves it under a same-origin prefix route with Cross-Origin-Embedder-Policy and Cross-Origin-Opener-Policy headers so Godot 4's SharedArrayBuffer threading works out of the box. A four-level target priority chain covers config pin, last selection persisted to disk, newest workspace, and directory ancestry. Write operations are guarded by a loopback trust fence and path-traversal protection, and the argv is assembled in a fixed order with no user-facing command surface.

It is built for indie developers and small teams who use Harness to assist Godot game development and want to go from code change to browser playtest for the Web export in one click. The only prerequisite is that Godot and the Web export templates are installed locally; the plugin handles everything else.