> For the complete documentation index, see [llms.txt](https://docs.tailent.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tailent.com/knowledge-base-1/tap-chrome-extension-manifest-issue.md).

# TAP Chrome Extension Manifest Issue

Due to changes to the Google Chrome extensions platform, all extensions running under **Manifest V2** have been automatically disabled (sometimes even removed from the profile extensions altogether). While we are working on fully resolving this issue, customers can use the following workaround.

This only affects customers running version 138+ of Google Chrome. Previous versions still allow enabling or installing the extension manually. If your TAP Chrome Extension shows as "enabled" no further actions are currently required.

In case your extension has been removed or cannot be turned on (enabled button is grayed out), please follow these steps:

1. Open a new Chrome tab and navigate to **chrome://extensions**
2. Remove the Tailent Automation Extension by clicking the remove button from the Tailent Extension. If you cannot find the extension it has probably been removed automatically by Chrome and you can skip this step\
   \
   ![](/files/ja8Qgog6DpdKkuUo8leM)<br>
3. Ensure that **Developer Mode** is turned on by clicking the switch in the upper right portion of the window\
   \
   ![](/files/UqnOrg0IZH5BW6qIxWMk)<br>
4. Open a new Chrome tab and navigate to **chrome://flags** and type "manifest" in the search bar of the newly opened tab
5. Find "**Allow legacy extension manifest version"** and select **Enabled**\
   \
   ![](/files/YKwW8dQv6bG4e1olUOY2)<br>
6. Restart Google Chrome
7. Download the unpacked version of the extension at <https://tailent-share.s3.eu-central-1.amazonaws.com/TAP_Chrome_1.21.4.2_0.zip>
8. Unzip the archive to a convenient location (such as the desktop)
9. In the extensions tab opened at step #1, click the **Load Unpacked** (top left portion of the chrome extensions tab)\
   \
   ![](/files/Mu8ilVgRKTvJ1z2B3gwr)<br>
10. In the select folder dialog, navigate to the directory where you unziped the archive above (the one containing the manifest.json file) and click **Select Folder**\
    \
    ![](/files/mYLIEY8VVO5OUCDH0CQY)<br>
11. The extension should now be installed and enabled as shows:\
    \
    ![](/files/OAZ5wVVdmG6EuMSaNTHg)<br>
12. Test the extension is running correctly by checking running processes and looking for **TAP.Chrome.Extension.exe**\
    \
    ![](/files/kBAtTkE0gn77JxItIHBr)

The extension is now fully operational and can be used again. Please check regurarly as we will update the extension to manifest V3 to provide a permanent solution.


---

# 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.tailent.com/knowledge-base-1/tap-chrome-extension-manifest-issue.md?ask=<question>&goal=<endgoal>
```

`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.
