WandGx Connect lives on the desktop.
WandGx Agent works inside it.
Connect is the installed app that gives WandGx local files, native app connectors, local hardware access, and project-scoped execution on the user's machine. WandGx Agent is the Hermes-backed local agent inside Connect, not a separate desktop product users need to decode.
Product split
WandGx.com
Account, projects, builds, hosted previews, publish history, rollback, billing, and cloud control-plane surfaces.
WandGx Connect
The installed desktop app on the user's machine. It owns local bindings, native launches, connectors, and desktop-side continuation.
WandGx Agent
The Hermes-backed local agent inside Connect. It handles file edits, local reasoning, debugging, and project-scoped execution.
What Connect actually does
Connect is not just a launcher. It is the local desktop layer between WandGx.com, the user's hardware, and the apps they already use.
Use local hardware
Run local models, use the machine's GPUs and CPUs when needed, and keep heavy local execution off the cloud path.
Edit real project files
WandGx Agent works inside Connect so it can edit files, run commands, start local dev servers, and debug inside the actual project folder.
Connect desktop tools
Attach the right project context and connect to tools like Unreal Engine, Blender, Photoshop, Slack, and Discord from the local machine.
Publish with rollback
Connect can trigger publish, but WandGx.com remains the source of truth for hosted versions, deployment history, and one-click rollback.
How the desktop flow should feel
The product should stay simple on the surface even though the local execution model is powerful underneath.
Download Connect and sign in with the same WandGx account.
Connect prepares the local runtime and pairs this machine to your workspace.
Attach a project or tool context so Connect knows exactly what it is allowed to touch.
WandGx Agent works locally inside that scope, while WandGx.com keeps version history and rollback.
Download the canonical installer
This button pulls the current Windows installer from the WandGx control plane, not from a random local path or stale external mirror.