While the tool does outputs some cookies, this aren't really the cookies of the user.
Chrome dev tools opens the page in some kind of container, without the user's cookies.
The cookies it outputs are just the cookies that google sets automatically, without the user being logged in.
If you delete de --headeless parameter in the source code, run the tool and when chrome opens you go to http://localhsot:9222/json/new?https://some_page_you_are_logged_in.com you will see you are not going to be logged in this URL, that's why the tool can't retrieve the real cookies.
At least that is what I understood. Only tested in Windows 10, on the latest Chrome.
While the tool does outputs some cookies, this aren't really the cookies of the user.
Chrome dev tools opens the page in some kind of container, without the user's cookies.
The cookies it outputs are just the cookies that google sets automatically, without the user being logged in.
If you delete de --headeless parameter in the source code, run the tool and when chrome opens you go to
http://localhsot:9222/json/new?https://some_page_you_are_logged_in.comyou will see you are not going to be logged in this URL, that's why the tool can't retrieve the real cookies.At least that is what I understood. Only tested in Windows 10, on the latest Chrome.