Install the Chrome extension

The extension is installed from the Chrome Web Store in one click and connected by signing in to the webapp once — it then exchanges that web session for its own token automatically. There are no API keys to copy at any point, because the extension never talks to an AI provider directly. Chrome delivers every later version by itself.

Prefer the long version? The 15-minute getting-started guide walks through it in depth.

Before you start

You need two things:

  • A Chromium-based browser — Chrome, Edge, Brave, Arc or Opera.
  • A Reply Pilots account. The extension cannot work signed out, because it holds no AI key of its own and every generation is made by the server on your account.

Firefox and Safari are not supported. There is no iOS app.

Install it

Reply Pilots is published on the Chrome Web Store, so installing takes one click:

  1. Open the Reply Pilots listing on the Chrome Web Store.
  2. Click Add to Chrome, then Add extension when Chrome asks you to confirm.
  3. Pin Reply Pilots to your toolbar so you can see its connection state at a glance.

That is the whole install. Nothing to unzip, no Developer mode, and no folder you have to keep somewhere safe. Chrome delivers new versions automatically — you never repeat this step.

The same listing works in Edge, Brave, Arc and Opera: open it in that browser and the button reads Add to Chrome there too.

Connect it to your account

Open app.reply-pilots.com and sign in — that is the whole step.

The extension calls the webapp, and if a valid web session exists it is issued a long-lived token scoped to your account. It stores that token locally and sends it with every request afterwards.

Open the extension's popup. It should read Connected. If it does not, see Troubleshooting.

No AI provider key is ever stored in the extension. Requests are made by the server, which is why there is nothing for you to paste in and nothing sensitive sitting in your browser.

Check that it is working

Go to any supported platform, click into a comment box or message composer, and look for the Reply Pilots button next to it. If the button appears, the content script is running and you are connected.

If the button does not appear, the two most common causes are that the site is muted or that the platform is switched off in your settings — both are covered in Troubleshooting.

Updating

There is nothing to do. Chrome checks the Web Store for new versions and installs them in the background, usually within a few hours of a release. To pull one immediately, open chrome://extensions, turn on Developer mode and click Update.

Your settings and your sign-in survive every update — they live in your account, not in the extension.

If you installed before the Web Store listing

Early users loaded an unpacked build downloaded from Settings → Extension. That copy still works, but it will never update itself, and if it predates the move to app.reply-pilots.com it is pinned to the old address by its manifest and cannot reach the new one — an extension cannot rewrite its own permitted addresses.

Move over once and you are done:

  1. Open chrome://extensions and Remove the manually loaded Reply Pilots.
  2. Install it from the Chrome Web Store.
  3. Sign in at app.reply-pilots.com if the popup asks you to.

Nothing is lost — your business context, voice settings and history are in your account, not in the browser.

Related

  • Accounts, sign-in and the dashboardHow the extension authorises itself, and what lives in the dashboard rather than in your browser.
  • Your first replyOpen the panel on a real post, generate, edit one sentence, insert. The whole sequence, once.
  • TroubleshootingThe button is missing, it says signed out, the draft looks wrong — causes in the order they occur.

More on this on the blog: Setup articles