Settings option to add custom arguments to the Chrome invocation (Retain Chrome's state across sessions) #2060
ZeroMax-dev
started this conversation in
Feature Requests
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
As a developer I don't want the Chrome browser to be completely reset every time Cline launches a new browser session.
For example, if I am testing a web-app Cline needs to go to the log-in page and enter login credentials every time before it can test the actual feature, which is time and cost-consuming.
I want to be able to retain the state of the Chrome browser across sessions as it is the case when I personally use my Chrome browser.
This can be achieved by adding the argument
--user-data-dir=./my_profile_directory/when starting the Chrome executable.The simplest solution would be to add another settings option "Chrome Custom Arguments" in Cline's advanced settings, right after the "Chrome Executable Path" option, where I can enter these custom arguments.
Beta Was this translation helpful? Give feedback.
All reactions