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

# Chrome extension

**In short:** the VoiceMoat Chrome extension brings drafting and replying into Twitter and LinkedIn where you already work. On Twitter it is a reply coach on every post; on LinkedIn it harvests the data VoiceMoat needs (your posts, analytics, home feed). It follows your active profile and never posts without you.

### Installing

Install "VoiceMoat" from the Chrome Web Store, then sign in to VoiceMoat in the same browser. The extension reads your dashboard session, so there is no separate key to enter. Once connected, it shows which profile is active and whether that profile's voice is trained.

### On Twitter

A reply coach appears on every tweet in your feed:

* press the reply-coach button, or hover a tweet and press **`r`**, to open the tone picker,
* pick from **12 tones**, use a smart auto-suggested tone, or a random one (keys **1 to 9** select tones),
* audenAI drafts **one** reply in your voice; you can rewrite, copy, or post it,
* **quick-fire** mode lets you queue replies fast, with an undo.

Replies you post from the extension go out through your logged-in Twitter session and count toward your overall daily reply limit (the same limit shown in Replies and Engage). On plans that include image analysis, the extension can factor in a tweet's image.

### On LinkedIn

LinkedIn does not offer the APIs VoiceMoat needs, so the extension gathers data from your own logged-in session (it never reads or ships your login token). It can:

* **harvest your own posts** for voice training and your own analytics,
* **add a creator by URL** to pull their recent public posts for study,
* **discover by hashtag**, and
* **harvest your home feed** (up to 40 posts) into your shared reply and Explore pool.

{% hint style="warning" %}
The extension does **not** post comments on LinkedIn. LinkedIn's rules do not allow it, so commenting stays copy-and-paste from the dashboard. On LinkedIn the extension reads; it does not write.
{% endhint %}

### What it does not do

* No posting comments on LinkedIn.
* No voice training inside the extension (training happens in the dashboard).
* No profile or account switcher: it has a Twitter / LinkedIn platform toggle and a LinkedIn-harvest toggle, and it follows your active dashboard profile. If it notices you are logged into a different Twitter handle than the one connected, it nudges you to connect that profile.
* No auto-posting without a click, and no reading of anything off Twitter or LinkedIn.

{% hint style="info" %}
Because the extension follows your **active profile**, switch profiles in the dashboard and the extension follows. There is no separate profile picker inside it.
{% endhint %}

### Common questions

**Do I need the extension?** On Twitter it is optional but handy (reply in the feed). On LinkedIn it is how voice training, home-feed discovery, and analytics get their data, so it is strongly recommended there.

**Is my LinkedIn login safe?** Yes. The extension reads data from your own logged-in session and never reads or transmits your login token.

**Which version am I on?** The popup shows the connected version. The current extension is version 1.9.0.


---

# 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.voicemoat.com/engaging/chrome-extension.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.
