You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the "danger" feature relies on the operator to have launched the first chrome browser with the remote debug port running on the standard port. Is there a way around this? Can we reopen the port from a session that is already launched?
The text was updated successfully, but these errors were encountered:
I'm searching for relevant snippets in your repository. If this is your first time using Sweep, I'm indexing your repository, which will take a few minutes.
Tip
To recreate the pull request, edit the issue title or description.
I'm searching for relevant snippets in your repository. If this is your first time using Sweep, I'm indexing your repository, which will take a few minutes.
Tip
To recreate the pull request, edit the issue title or description.
Right now the "danger" feature relies on the operator to have launched the first chrome browser with the remote debug port running on the standard port. Is there a way around this? Can we reopen the port from a session that is already launched?
The text was updated successfully, but these errors were encountered: