# Easily identify editor instances

There is a popular extension called "Peacock". It is useful for identifying editor instances when you have multiples of them open. This extension is included in the VS Code Can Do That extension pack.

* Open the Command Palette (**Cmd/Ctrl + Shift + P**)
* Select "Peacock: Enter a color"
* Enter in any color

![](/files/-LlwctpBYXMFAcdoGgwq)

I find that it's most useful to set just the titlebar color with Peacock. This is enough to let me know at a quick glance which editor instance I'm looking at. For that reason, I disable the "Status Bar" and "Action Bar" theming in Peacock.

* Open Settings (**Cmd/Ctrl + ,**)
* Add in the following two lines...
  * "peacock.affectActivityBar": false
  * "peacock.affectStatusBar": false

![](/files/-LlwdGHoBwpXJyPA0SzU)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://burkeholland.gitbook.io/vs-code-can-do-that/master/exercise-1-1/easily-identify-editor-instances.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.