I know I can launch chrome the following way to open a remote debugging port at 9222 port -
chrome.exe --remote-debugging-port=9222
But I
For mac, I made a simple application that launches chrome with the --remote-debugging-port
for me. Mathias Bynens has a wonderful post on how to do this (which is where I got the idea). He even includes a (forked) script that can do most of it for you, but the basics are really simple.
Make a directory in your applications folder with the following structure <new app name>/Contents/MacOS
:
mkdir -p /Applications/Chrome\ Debugger.app/Contents/MacOS
Create your script file and make it executable (its name need to match the top folder name):
cd /Applications/Chrome\ Debugger.app/Contents/MacOS
touch Chrome\ Debugger
sudo chmod +x Chrome\ Debugger
Edit the new file with your editor of choice (your path to chrome may be different):
#!/usr/bin/env bash
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222&
And that's about it. You can add a custom icon if you want to make it easier to find (copy your new icon > right click the new app > Get Info > click the current icon in the top left > paste the new icon over current icon), but the app will work fine without it.
I have figured out a way to solve my problem statement. I am posting it as an answer as it may help someone else with similar problem statements.
If you are on Windows, go to registry editor and search this command
Computer\HKEY_CLASSES_ROOT\ChromeHTML\shell\open\command
Modify the key with the following -
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222 -- "%1"
If you want to play with Chrome, put --incognito if you always want to launch Chrome in incognito mode.
Caution: Please backup your registry before playing with it.
I can't add comments yet, But David Mann's answer is out of date for MacOS.
Thankfully only one slight change is needed; Add the bash shebang to the Chrome Debugger script.
#!/bin/bash
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222&
this update for mac users was found here: Enable remote debugging on Chrome by default on mac?
Nat Khun also went to the trouble of crafting a .dmg to allow for a "normal" installation procedure for mac users. His repo can be found here: https://github.com/natkuhn/Chrome-debug/
be sure to give him a star. I did!
Rather than editing the registry, you can simply append the flag directly within the program properties by right clicking on the Chrome icon and adding...
--remote-debugging-port=9222 -- "%1"
...onto the end of the target field.