This build is for community members. Enter the access password to continue - it is remembered on this computer.
This build includes your community's GEX feed. The bridge launches TradingView in debug mode and streams gamma exposure to your live chart automatically.
No key needed - this build is pre-configured.
The bridge talks to TradingView through its local debug port (127.0.0.1:9222), so the desktop app must run in debug mode to establish the connection. Opening the bridge starts TradingView that way automatically - or, if it is already running in debug mode from a previous session, we connect to it straight away.
If the button doesn't work, you can start TradingView yourself with a single command. It is shown in full below so you can read exactly what it does before running it - nothing is installed or changed on your computer.
Press the Windows key, type powershell, press Enter. Then paste this one line and press Enter:
Stop-Process -Name TradingView -Force -ErrorAction SilentlyContinue; Start-Process -FilePath "$env:LOCALAPPDATA\Programs\TradingView\TradingView.exe" -ArgumentList '--remote-debugging-port=9222'
It does two things: closes any running TradingView (the debug option only takes effect on a fresh start), then starts TradingView with its built-in debug option so this bridge can talk to it on 127.0.0.1:9222.
Once TradingView is up, click Reconnect above.
If the bridge keeps starting the wrong TradingView - typically after uninstalling and reinstalling it - this clears the bridge's memory of where TradingView lives: it closes TradingView, deletes the bridge's local copies and leftovers of uninstalled TradingView packages, then re-detects from scratch on the next start. The login and layouts of your current TradingView are not touched.