Wand Enhancer: A Build-From-Source Patcher for the Wand Desktop App

What Wand Enhancer Patches and Who It Is For

Wand Enhancer targets the local file installation of the Wand desktop application. The README describes five categories of improvements: local environment configuration management, automated compatibility adjustments for new Wand client versions, advanced layout and theme customization (client-side only), AI features, and a Remote Web Panel for controlling the app from a phone over a local network.

The project's primary audience is developers and power users who want to extend the Wand client beyond its defaults. The README makes one commitment clear from the start: there are no official prebuilt downloads. Every user compiles their own executable from their own fork, which means anyone who downloads a .exe from a YouTube link, a random website, or a third-party mirror is not running this project. The README devotes its opening notice to warning about malware distributed under the Wand Enhancer name.

How the Patcher Applies Changes

The tool is a .NET patcher. When run, it reads the selected local Wand installation directory and applies modifications to files in that directory. The default build path includes no telemetry and no network-access code: the patcher runs entirely offline.

One optional compile-time flag changes that behaviour. When the Include GitHub release checks flag is enabled during the Actions workflow, the resulting executable sends a GitHub API request with the user's IP address and a User-Agent string each time Wand starts. The README is specific: this variant sends no Wand account data and never downloads updates automatically. Users who want a fully offline patcher should leave this flag off.

Because the patcher modifies application files and is unsigned, antivirus software may trigger on it via generic heuristics. The README names this directly and recommends reviewing the source code before building. The patcher does not change Wand's status as an online service; it only modifies local client-side files.

Building Your Executable via GitHub Actions

The supported build path for most users requires no local development environment. The steps documented in the README are: sign in to GitHub, fork the repository, click Sync fork before each build to pull upstream fixes, go to the Actions tab in the fork, enable workflows if prompted, select the Build executable workflow, click Run workflow, wait for the run to finish, then download the artifact.

Extracting the artifact zip and running WandEnhancer.exe applies the patches to the selected Wand installation.

For local builds, the README lists these requirements:

# Local build requirements (Windows only):
# Node.js and pnpm
# Visual Studio 2022 or Build Tools for Visual Studio 2022 with MSBuild
# .NET Framework 4.8 desktop development workload

When testing a release candidate, the maintainer asks testers to select the feature/rc_* branch in the workflow's branch selector. Syncing master does not update an RC branch. Record the workflow's source commit SHA, not just the version tag, because the same tag label can map to different commits across the RC branch and a local build.

The Remote Web Panel: LAN Control With No Pairing Code

Wand Enhancer includes a built-in HTTP and WebSocket server that starts on TCP port 3223. After patching, hovering over the Connect button in the top bar displays a QR code. Scanning that code from a phone on the same Wi-Fi network opens the web panel in the phone's browser.

The security model here is minimal. The README states that the panel uses plain HTTP with no pairing code, and that anyone who can reach port 3223 can view the panel and control the active application. The only recommended protections are keeping the host machine on a trusted LAN or routing the connection through a VPN such as Tailscale. Exposing port 3223 to the internet is called out as unsafe.

Two common connectivity problems have specific causes. Routers with AP isolation or guest-network SSID isolation block device-to-device traffic even when both devices share the same network name. Windows Firewall may also block inbound TCP traffic on port 3223. Marking the Windows network connection as Private rather than Public changes its firewall profile and can resolve the problem.

The panel protocol does not transmit the user's Wand bearer token or installation-path fields.

Injecting Custom JavaScript into Wand's Renderer

Wand Enhancer allows adding custom .js files that are bundled into the Wand client at patch time. Scripts run inside Wand's renderer, with full DOM access and access to Node's require. This feature requires the Remote Web Panel patch to be enabled because it reuses the same renderer injection mechanism.

Scripts can be added in two ways: through the patch dialog by selecting .js files, or by placing .js files in a renderer-scripts/ folder next to the patcher executable before running it. Only existing .js files are accepted.

The README includes a working minimal example:

if (!globalThis.__helloScriptInstalled) {
  globalThis.__helloScriptInstalled = true;
  WandEnhancer.log("Hello from my custom script!", WandEnhancer.remoteUrl);
  new MutationObserver(() => {
    const dialog = document.querySelector("ux-dialog:not([data-seen])");
    if (dialog) {
      dialog.setAttribute("data-seen", "1");
      WandEnhancer.log("A dialog opened.");
    }
  }).observe(document.documentElement, { childList: true, subtree: true });
}

The guard on globalThis.__helloScriptInstalled is necessary because scripts may execute more than once per Wand launch. A helper object named WandEnhancer exposes three properties: WandEnhancer.log() for logging, WandEnhancer.remoteUrl for the panel URL, and WandEnhancer.apiVersion. Scripts run with the same privileges as the Wand client itself.

Real Limitations of This Approach

The build-from-source requirement is a hard barrier. Users unfamiliar with GitHub forks, GitHub Actions, or C# source review cannot safely use this tool. The absence of binaries is not a gap in the project; it is the project's explicit security stance.

Testing prerelease builds adds complexity. The master branch holds stable code. Release candidate branches (feature/rc_*) are separate branches, and syncing the fork's master does not update a separate RC branch. A user running a test build must track the workflow's source commit SHA, not just the version tag, because different builds with the same tag label can contain different fixes.

The Remote Web Panel's lack of authentication is a concrete limit for shared or public networks. Anyone who can reach port 3223, whether through misconfigured firewall rules or an untrusted LAN, can control the application. There is no option to add a password to the panel within the current design.

Bug reports must not include account tokens, storage dumps, or compiled executables. The README asks for launcher.log and launcher.prev.log from the Wand installation root, the exact Wand version, stable or beta channel, selected patches, and whether the failure happened on a fresh install, an update, or a Restore operation.

Alternative Approach and Maintenance Status

The most common alternative for modifying a desktop application's local files without a dedicated patcher is direct archive editing. For applications that store their source in an .asar bundle (a format used by Electron applications), the npm package named asar unpacks and repacks that archive directly. Unlike Wand Enhancer, raw archive editing is version-blind: it does not detect Wand client updates and does not apply compatibility adjustments automatically. Every Wand update requires repeating the edit manually.

Wand Enhancer's automated compatibility adjustments and the Remote Web Panel are features that raw archive editing does not provide.

The most recent release, version 2.1.0.0, was pushed on 2026-09-09. The repository's default branch is master. The project is hosted at https://gitlab.com/kitbyte/wand-enhancer but mirrored on GitHub for Actions-based builds. The license is Apache-2.0, which permits use, modification, and redistribution with attribution. The Apache-2.0 license imposes no restrictions on the type of Wand installation being patched, but users are responsible for complying with Wand's own terms of service.

Editorial conclusion

Wand Enhancer is for technically inclined users who want more control over their local Wand client and are comfortable forking a repository, reviewing C# source, and running GitHub Actions. Anyone expecting a ready-to-run installer will not find one here: the project deliberately withholds binaries to reduce the attack surface from fake-tutorial scams. Before building, review the source, decide whether to enable the GitHub release-check flag, and read the CHANGELOG to know which patches on master are stable. The Remote Web Panel is only safe on a trusted LAN or a VPN such as Tailscale.

Frequently asked questions

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes