> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/how-to/pinning-the-chrome-extension.md).
# Pinning the Chrome Extension
Sometimes you’ll need to access the PixieBrix Sidebar. The quickest way to trigger that is by clicking the PixieBrix extension icon from the Chrome toolbar.
If you don’t see it there, that’s easy to fix! Click the puzzle icon at the end of your URL bar. Once the menu opens, you should see all your installed Chrome extensions, including PixieBrix!
Click the pin icon next to PixieBrix, and now you’ll be able to click the PixieBrix icon from your toolbar anytime you want.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://docs.pixiebrix.com/how-to/pinning-the-chrome-extension.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.