WinCC Unified Debug Proxy

Debug WinCC Unified scripts in VS Code with automatic reconnection.

A lightweight, open-source CDP proxy written in Rust.

Features

Automatic Reconnection

The proxy monitors WinCC for target changes. When a screen reloads, VS Code reconnects automatically. Zero manual intervention.

Separate Proxy Ports

Dynamics and Events each get their own proxy port, so you can debug them independently or together.

Script Dump

Dump all runtime scripts to local files as they are loaded. Includes ESLint config and TypeScript definitions for IntelliSense.

Remote Debugging

Auto-generate netsh scripts for port forwarding and firewall rules when WinCC runs on a different machine.

The Problem

Debugging WinCC Unified scripts is painful. Every time a screen reloads, the debug target changes and your debugger disconnects. The default workflow uses chrome://inspect, which means opening new DevTools windows constantly — separately for Dynamics and Events.

This proxy sits between VS Code and WinCC, monitoring for target changes and automatically reconnecting. Debug from the comfort of VS Code instead of juggling DevTools windows.

Get started

Open Source

WinCC Unified Debug Proxy is free and open source. Found a bug? Have a feature idea? Contributions are welcome — open an issue or submit a pull request on GitHub.