The launch script scripts/launch_tv_debug.bat checks %LOCALAPPDATA%\TradingView, %PROGRAMFILES%\TradingView, and a path inside WindowsApps, but doesn't reliably find TradingView when it's installed from the Microsoft Store. On my Windows 11 machine, the script fails with Error: TradingView not found even though TradingView Desktop is installed and running.
Environment
Windows 11
TradingView Desktop installed via Microsoft Store (package: TradingView.Desktop_3.1.0.7818_x64__n534cwy3pjxzj)
Node 24.15.0, npm 11.12.1
Claude Code 2.1.126
Reproduction
Install TradingView Desktop from the Microsoft Store (which is what tradingview.com/desktop currently directs Windows users to — the standalone installer is no longer easy to find on the official download page).
Clone the repo, npm install, configure .mcp.json per the README.
Run .\scripts\launch_tv_debug.bat.
Expected: TradingView launches with --remote-debugging-port=9222.
Actual: Script prints Error: TradingView not found. Checked: %LOCALAPPDATA%\TradingView, %PROGRAMFILES%\TradingView, WindowsApps.
Suggested fix
Add a fallback that uses Get-AppxPackage to locate Store-installed TradingView:
powershellGet-AppxPackage TradingView | Select-Object -ExpandProperty InstallLocation
This returns the current install path regardless of version. The version suffix in the WindowsApps folder name (e.g. 3.1.0.7818) changes with every TradingView update, so hardcoded path matches inside WindowsApps will break on each update. Querying by package name is the durable solution.
Open question
I'm not sure whether launching the Store-installed TradingView.exe directly with --remote-debugging-port=9222 actually works — Store-packaged (AppX) apps can have their command-line flags stripped by the runtime wrapper, in which case detection alone won't be enough and the script would need to either error with a clearer message ("Microsoft Store version detected; not currently supported, please install the standalone version") or document a working approach for Store users.
If anyone has confirmed that direct-exe invocation with the debug flag works for the Store version, that would be useful to document in the README. If it doesn't work, a clearer error message would save Store-only users (which appears to be most current Windows users, given how tradingview.com directs downloads) a lot of troubleshooting time.
Workaround for now
Install the standalone (non-Store) version of TradingView Desktop. This is increasingly difficult to find — the official download page redirects to the Store. Documenting a current direct-download URL in the README, or noting that the standalone version is required, would help.
The launch script scripts/launch_tv_debug.bat checks %LOCALAPPDATA%\TradingView, %PROGRAMFILES%\TradingView, and a path inside WindowsApps, but doesn't reliably find TradingView when it's installed from the Microsoft Store. On my Windows 11 machine, the script fails with Error: TradingView not found even though TradingView Desktop is installed and running.
Environment
Windows 11
TradingView Desktop installed via Microsoft Store (package: TradingView.Desktop_3.1.0.7818_x64__n534cwy3pjxzj)
Node 24.15.0, npm 11.12.1
Claude Code 2.1.126
Reproduction
Install TradingView Desktop from the Microsoft Store (which is what tradingview.com/desktop currently directs Windows users to — the standalone installer is no longer easy to find on the official download page).
Clone the repo, npm install, configure .mcp.json per the README.
Run .\scripts\launch_tv_debug.bat.
Expected: TradingView launches with --remote-debugging-port=9222.
Actual: Script prints Error: TradingView not found. Checked: %LOCALAPPDATA%\TradingView, %PROGRAMFILES%\TradingView, WindowsApps.
Suggested fix
Add a fallback that uses Get-AppxPackage to locate Store-installed TradingView:
powershellGet-AppxPackage TradingView | Select-Object -ExpandProperty InstallLocation
This returns the current install path regardless of version. The version suffix in the WindowsApps folder name (e.g. 3.1.0.7818) changes with every TradingView update, so hardcoded path matches inside WindowsApps will break on each update. Querying by package name is the durable solution.
Open question
I'm not sure whether launching the Store-installed TradingView.exe directly with --remote-debugging-port=9222 actually works — Store-packaged (AppX) apps can have their command-line flags stripped by the runtime wrapper, in which case detection alone won't be enough and the script would need to either error with a clearer message ("Microsoft Store version detected; not currently supported, please install the standalone version") or document a working approach for Store users.
If anyone has confirmed that direct-exe invocation with the debug flag works for the Store version, that would be useful to document in the README. If it doesn't work, a clearer error message would save Store-only users (which appears to be most current Windows users, given how tradingview.com directs downloads) a lot of troubleshooting time.
Workaround for now
Install the standalone (non-Store) version of TradingView Desktop. This is increasingly difficult to find — the official download page redirects to the Store. Documenting a current direct-download URL in the README, or noting that the standalone version is required, would help.