> For the complete documentation index, see [llms.txt](https://docs.codewords.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codewords.ai/features/chrome-extension.md).
# Chrome extension
Automate actions on logged-in websites with the CodeWords Chrome Extension.
### Introduction
The CodeWords Chrome extension automates tasks on websites where you're already logged in. It runs directly in your browser, using your existing sessions to access private content like LinkedIn feeds, dashboards, and member-only pages.
### Key limitations
* Runs have a 5-minute timeout limit.
* The Chrome Extension works on desktop or laptop only, and it is not supported on mobile.
* There are no visual indicators of run status.
* Outputs return in Markdown by default, not HTML.
### When to use the Chrome extension
Perfect for:
* Getting content from private pages (LinkedIn feeds, dashboards)
* Simple website tasks like clicking buttons or filling forms
* When reliability is more important than speed
Not ideal for:
* Scheduled automations when you're away
* When you need to use your browser simultaneously
* When speed is critical
### Getting started
1. Open [Settings → Browser Control](https://codewords.agemo.ai/#settings/browser-control) and click **Install & Connect**, or install from the [Chrome Web Store](https://chromewebstore.google.com/detail/codewords/fgcbeegcaikofigbnfmmlgcimdkmfnce).
2. Wait until Browser Control shows **Connected**.
3. Sign in to the websites you want to automate in that browser.
### See the Chrome extension in action
### What it can do
| Function | Best for | Speed |
| ------------------- | ------------------------------------- | -------------- |
| Page scraping | Get content from private pages | 30-60 seconds |
| Interactive actions | Click buttons, fill forms | 60-120 seconds |
| Cookie extraction | Share login sessions with other tools | 10-30 seconds |
### Performance expectations
* Reliable: Very consistent results using your real browser
* Status visibility: No visual run status indicators are shown during execution
* Slower: Takes longer than other tools, but is more dependable
* Browser control: Uses one tab while running
### Best practices
* Test your automation manually first
* Stay logged in to target websites
* Be patient — good results take time
### Common use cases
* Monitor LinkedIn feeds and collect posts
* Extract data from company dashboards
* Gather content from member-only sites
* Automate repetitive form filling
---
# 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.codewords.ai/features/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.