WandEnhancer
WandEnhancer: quickstart de parche local y panel LAN confiable
Prueba por separado el parche, el Remote Web Panel, los scripts del renderer y un artefacto construido por ti, con rollback.
Qué aprenderás
- Exercise WandEnhancer features one boundary at a time
- Build and test a trusted LAN panel
- Audit renderer scripts and perform a clean rollback
Antes de empezar
- Basic Git and command-line usage
- Comfort reading a project README
You can explain the project, run its documented first step, and decide what to verify before adopting it.
Conclusiones clave
- Test patching, the LAN panel, and renderer scripts as separate trust boundaries.
- Port 3223 is unauthenticated plain HTTP; keep it on a trusted LAN or VPN.
- Build from your own fork, guard scripts against repeat execution, and keep a rollback.
Separate the feature boundaries
El parche, el panel y los scripts de WandEnhancer son límites de confianza distintos. Construye desde tu fork, prueba el panel en una LAN privada, audita un script con guardia de una sola ejecución y termina verificando la restauración del cliente.
Begin with a disposable Wand installation and a backup of the original files. Record the repository commit, local client version, Windows network profile, and the exact feature toggles. The project does not publish official prebuilt executables, so the artifact you test should come from your own fork or a source build whose workflow logs you can inspect.
Run the Remote Web Panel smoke test
The README's quick start places the PC and phone on the same Wi-Fi network, then uses the Connect button and QR code. If the page does not load, check client isolation, Windows Firewall, and TCP port 3223 before changing the patch. A trusted VPN such as Tailscale can bridge networks, but the panel remains plain HTTP and has no pairing code.
The acceptance test is intentionally narrow: load the panel, observe one harmless trainer state, issue one reversible UI action, and close it. Do not port-forward 3223 or put the panel behind a public reverse proxy; anyone who can reach it can view the panel and control the active trainer. Preserve a short test receipt without bearer tokens or installation paths.
Add custom scripts with a one-time guard
Custom `.js` files run in Wand's renderer when the Remote Web Panel patch is enabled. The README grants DOM access and Node `require`, says a script may execute more than once per launch, and provides a small `WandEnhancer` helper. Start with a script that only logs a visible event, guard installation behind a `globalThis` flag, and verify that a thrown error does not crash the client.
Review every script as privileged client code. Keep it in source control, pin its checksum, and remove it from `renderer-scripts/` before testing an unrelated patch. Never paste a script from a tutorial or mirror you cannot audit; the repository's malware warning is part of the feature contract, not a footnote.
Diagnose and roll back
If the client fails to start, restore the backed-up installation and retest without the panel or scripts. If only the panel fails, inspect the network profile and 3223 listener. If a script behaves twice, confirm the guard and lifecycle timing. If Windows Defender warns about the executable, compare the artifact hash and Actions log with your fork rather than disabling protection globally.
A successful quickstart ends with a clean rollback: remove the patch, delete injected scripts, close the listener, and verify the original client launches. This gives a reader a repeatable way to explore the project without turning an experimental local enhancement into an internet-facing control service.
Cómo elegir
| Criterio | Opción A | Opción B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Pasos de implementación
- 1
Fork/sync WandEnhancer and build the artifact through your own Actions run.
- 2
Back up the local Wand installation and test one client-side feature.
- 3
Run a harmless QR/panel action on a trusted LAN, checking firewall and port 3223.
- 4
Add one audited script with a one-time guard, then remove all changes and verify rollback.
Ejemplo para copiar
// hello.js (renderer script; runs with client privileges)
if (!globalThis.__helloInstalled) {
globalThis.__helloInstalled = true;
WandEnhancer.log('hello from a reviewed script');
}
Remote panel: TCP 3223 / trusted LAN or VPN onlyPreguntas frecuentes
Can I download a ready-made WandEnhancer.exe?
The README says there are no official prebuilt executables. Build from your own fork's Actions artifact or compile from source, and treat third-party binaries as untrusted.
Why does the QR code work on Wi-Fi but not on guest Wi-Fi?
Client or access-point isolation can block devices from reaching each other. Check the network profile and firewall, or use a private VPN without exposing port 3223 publicly.
Fuentes
- WandEnhancer README (captured 2026-08-31)Fuente verificada 2026-08-31
- WandEnhancer repositoryFuente verificada 2026-08-31