> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/~/revisions/CBft97pr7Q1KpU4KFthF/faqs-and-troubleshooting/why-cant-i-log-in-to-reos-chrome-extension.md). # Why can’t I log in to Reo's Chrome Extension? If you’re experiencing login issues with the Chrome extension, it may be due to **corrupted or outdated cookies** that interrupt the authentication process. To resolve this, please try clearing your cookies by following either of the below options. **Option 1: Delete all cookies** {% hint style="info" %} **Important**: Clearing cookies may sign you out of websites and remove saved preferences. Proceed only if you’re comfortable with this. {% endhint %} **Steps** 1. Open **Chrome** on your computer. 2. Click the **More (⋮)** icon in the top-right corner → select **Delete browsing data**. 3. Choose **Basic** or **Advanced** and ensure **Cookies and other site data** is selected. 4. Under **Time range**, choose: * Last hour * Last 24 hours * Last 7 days * Last 4 weeks * All time *(recommended)* 5. Select any additional items you want to delete. 6. Click **Delete data** to confirm. \ **Option 2: Delete cookies for a specific website** If you prefer to not delete all cookies, you can remove them only for the affected site. **Steps** 1. Open **Chrome**. 2. Click **More (⋮)** → **Settings**. 3. Select **Privacy and security** → **Third-party cookies**. 4. Click **See all site data and permissions**. 5. Use the search bar in the top-right to find the website name. 6. Click **Delete (🗑️)** next to the site. 7. Confirm by selecting **Delete**. \ **Next Steps:** After clearing the cookies, **restart the Reo Chrome Extension** and try logging in again. If the issue persists, please contact support. To understand Cookies, refer this article: --- # 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.reo.dev/~/revisions/CBft97pr7Q1KpU4KFthF/faqs-and-troubleshooting/why-cant-i-log-in-to-reos-chrome-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.