> For the complete documentation index, see [llms.txt](https://docs.bugbug.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugbug.io/troubleshooting/updating-chrome-extension.md).

# Updating Chrome extension

How the BugBug Chrome extension updates, how to check its version, and how to update it manually when the web app or recording doesn't work as expected.

Chrome updates the BugBug extension automatically. When a new version is available, the extension waits until no test is being recorded or run, then reloads itself and the open BugBug tabs.

If an update happens while a test window is open, the window shows **Extension has been updated**. Close the window, because it's no longer connected to BugBug, and start again from the BugBug web app.

## Check the version

Click the BugBug icon in the Chrome toolbar. The popup shows the extension **Version**, your **Browser** and the connection **Status**.

## Update the extension manually

Update manually if the web app or test recording doesn't work as expected, or if BugBug asks you to update the extension, for example **Update your browser extension to change this option** in a step.

1. Go to Chrome extensions: open `chrome://extensions` in the address bar.

![](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FstXJhQGtO7KWtFWL3iFQ%2Fimage.png?alt=media\&token=959dee81-9e8f-420a-bc75-bcd4eea06a14)

2. Turn on **Developer mode**.

![](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FsJQxSIrLFJeNxHLwoPEL%2Fimage.png?alt=media\&token=429389b2-bad1-4c96-9866-232cfc221e17)

3. Click **Update**.

![](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FH7k6VpxqxKuRBcMOHcoB%2Fimage.png?alt=media\&token=b17d4a5d-4530-41f1-855b-10ff708a5a13)

4. After the update is finished, refresh the BugBug web app page.

![](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2Fat1YbWLiczJsbPy7eRbX%2Fimage.png?alt=media\&token=93b73d47-72b4-4f47-aea6-ab00909eeefe)

If the extension isn't installed at all, see [Install Test Recorder](/quick-start/install-test-recorder.md). For errors such as **EXTENSION\_DISCONNECTED**, see [Error codes](/debugging-tests/error-codes.md#browser-and-extension-errors).


---

# 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.bugbug.io/troubleshooting/updating-chrome-extension.md?ask=<question>&goal=<user_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.