> 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/updating-the-browser-extension.md).
# Updating the Browser Extension
### Updating the extension from the Chrome Web Store
Chrome automatically checks the Chrome Web Store for updates to the PixieBrix extension each day. However, in some cases you may want to get the update before Chrome has pushed it to your account.
#### Option 1. Restart Chrome
When you restart Chrome, it will apply any available updates to the installed extensions
#### Option 2. Apply Detected Update
* Open the PixieBrix browser extension. From [https://app.pixiebrix.com](https://app.pixiebrix.com/) click “Open Browser Extension"
* If Chrome has already detected that there is an update available, a golden banner will be displayed. Click the "Update Extension" button
* Refresh any tabs where you were using PixieBrix
#### Option 3. Manually Check for updates
* Open the PixieBrix browser extension. From [https://app.pixiebrix.com](https://app.pixiebrix.com/) click “Open Browser Extension"
* Click the Settings item in the sidebar\\
* Scroll to the bottom of the page and click "Check Updates"
* Refresh any tabs where you were using PixieBrix
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.pixiebrix.com/how-to/updating-the-browser-extension.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
