Extensions

Install extensions once. Choose accounts later.

Find and update extensions in one place, then choose which accounts need them. MaskPilot warns you when a version does not fit.

MaskPilot
MaskPilot extension list showing versions, categories, account usage, and update status
Real client interface · extension versions and account scope

Find the right extension quickly

Search by category or keyword, then choose which accounts should use it.

Check the version before use

MaskPilot checks whether an extension fits the current browser, reducing failed launches.

Choose when to update

When a new version is available, MaskPilot lets you know and leaves the timing to you.

01

Accounts using it

See which accounts use an extension

Check which accounts will be affected before you update or remove it.

02

Install problems

See what to do next

MaskPilot suggests reinstalling, changing versions, or contacting support instead of showing only an error code.

From install to launch

Installing an extension does not load it into every account.

MaskPilot keeps the extension identity, available versions, local installation state, and account assignment separate so one update does not silently change every environment.

Choose a compatible version before upgrading.

An extension version can declare its supported browser range. The detail view shows the available version, installed version, and whether an upgrade exists. Incompatible combinations are not forced into an account at launch.

  • Tasks are grouped into All, Installed, and Updates
  • Compatibility is described in plain language
  • Store-only removal and forced disable remain separate policies

Each account loads only the extensions you select.

After installation, choose the environments that need the extension. Before an update or removal, check which accounts are affected and validate critical work in a test account first.

  • Install does not automatically affect every account
  • Extension runtime data remains separate per account
  • Close accounts normally before changing an extension they use
Read the install and update guide

Your Manifest V3 extension stays on the current device.

Import a local extension from a folder or ZIP. Before confirmation, review its name, version, website access, and browser capabilities. The imported copy becomes an independent snapshot instead of continuing to reference the source folder.

  • The first version does not accept CRX or Manifest V2
  • Local extensions and assignments do not upload or sync
  • The client rechecks the local copy and compatibility before launch
  • Import never enables the extension for every account
Read the local-extension boundaries

Normal states and troubleshooting stay separate.

An empty store, no search results, not installed, already current, and load failure each receive a different explanation. Removal and repair actions do not dominate a healthy extension view.

  • Review release notes before upgrading
  • Choose another extension or browser version when incompatible
  • Failure states provide a next step instead of only an error code

Validate in a test account

Check compatibility before using an extension in production.

Download MaskPilot and complete one install, launch, and upgrade check in a test account before relying on the extension in daily work.