Chrome Debug Mode
To record interactions, Reshot needs to control Chrome through its debugging protocol.
Launching Chrome
Use the built-in command to launch Chrome with the correct flags:
Terminal
reshot chrome
This opens a new Chrome window with remote debugging enabled on port 9222.
Options
| Option | Description |
|---|---|
--port | Debug port (default: 9222) |
--user-data-dir | Chrome profile directory |
Example with custom port:
Terminal
reshot chrome --port 9333
Important Notes
Quit All Chrome Instances First
Before running reshot chrome, you must fully quit all existing Chrome windows. Chrome can only run with remote debugging if it starts fresh.
On macOS: Cmd + Q to fully quit Chrome.
Using an Existing Chrome Instance
If you prefer to manage Chrome yourself, launch it manually with these flags:
Terminal
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
--remote-debugging-port=9222 \
--user-data-dir=/tmp/reshot-chrome
Reshot will automatically connect to any Chrome instance running on the configured debug port.
Multiple Browser Profiles
For testing with different user states, you can run multiple Chrome instances with separate user data directories:
Terminal
# Admin user
reshot chrome --user-data-dir=/tmp/chrome-admin
# Regular user (in another terminal)
reshot chrome --port 9223 --user-data-dir=/tmp/chrome-user