Issue Type: Bug

After updating my VS Code, my debugging experience became unpredictable and would pause unexpectedly. I've traced down the root cause in my code to an instantiation of a node Worker (from the worker_threads module).

I have created a simple reproducible scenario with instructions here.

The problem manifests when a

• I have searched through existing issues

Feature Request

https://user-images.githubusercontent.com/9758711/118620178-d5ff1000-b7f7-11eb-8a65-f3221ec5ac3b.mov

I love the extension but the icon feels a little out of place relative to other icons to me. The close lines/crowded detail actually makes the icon appear blurry on my display vs the built in icons which are sharp (screenshots don't capture it well). A more minimalistic folder icon might match better with the built in VSCode icons.

<img width="86" alt="CleanShot 2021-05-19 at 10 54 33@2x" src="

Most of the time when I'm using this extension I am using it to mark points of interest during research. A task that I've had to perform lately is looking for hard coded text in various applications that needs to be moved to our CMS. This extension works great for that with one exception:

Generally after I have performed my research I need to document it. Using this extension I need to go to ea

Setting peacock.color or peacock.remoteColor in the user settings.json can be done manually. If set, peacock will use that color as the default color to colorize VS Code.

This should be documented in the readme, along with considerations.

Considerations:

• this can only be set or unset manually.
• this will make every vs code instance that doesnt have a color in their workspace use t