A require rule can be added to a configuration if you want Plucky to protect a specific browser extension from being disabled or removed. If the protected browser extension is disabled or removed while the require rule is active, the browser will lose internet access until the extension is enabled or the require rule is removed from the configuration.

The rule syntax is simply require extension-id. If you know the id of an extension, you can require it.

How to find the id of an Edge (Chromium) extension

  1. Open your browser’s extension page by expanding the hamburger menu (or three dots menu on Microsoft Edge) in the top-right corner of your browser window, and click on “Extensions” or “Manage Extensions”.
  2. Locate the extension you want to require with Plucky, and click the “Details” button.
  3. The url location bar will now show something like this: edge://extensions/?id=oicejjalnbhehlnedhhjlhbabhddhidc
  4. The 32-letter string following the equal sign is the id of your extension.

How to find the id of a Firefox extension

Note that Firefox extensions are often called add-ons and the terms are used interchangeably

  1. Navigate to the add-ons page in the Mozilla store for the extension you want to require
  2. Scroll down to More information and click on Copy add-on ID
  3. The add-on id is now copied to your clipboard, so you can paste it to finish making a require rule as shown in the examples below

On Firefox, the id sometimes looks like an email address (e.g., addon@darkreader.org) and sometimes it’s a uuid in curly braces (e.g., {e4b27483-2e73-4762-b2ec-8d988a143a40}). Plucky 1.17.54+ can read both id types just fine.

Example: making dark reader required

pluck + require eimadpbcbfnmbkopoojfekhnkhdbieeh
pluck + require addon@darkreader.org

This rule makes an extension called Dark Reader required in order for your browser to allow internet access. It’s important that you install the extension before adding the require rule with Plucky, or you will lose internet access and be unable to install the extension after. If this happens, remove the require rule to regain internet access.

Adding/removing a require rule

Requiring extensions can’t be configured from the interface in the browser. It must be configured through either a console, or the raw edit tab of your configuration on the user site.

pluck + require extension-id
pluck - require extension-id

Scheduling a require rule

A require rule can be scheduled using a when modifier, so it is only required within certain timeframes. For example, you can require an extension during work hours from 9am to 5pm, or all day Saturday and Sunday, or from 11pm to 7am on Monday through Friday.

pluck + when 9-17 require extension-id
pluck + when UA0-24 require extension-id
pluck + when MTWRF0-7,23-24 require extension-id

Blocking extensions (opposite of require):

The simple way is to block the extension store by importing no-browser-extensions.

Alternatively, one can explicitly require all preferred extensions and also use nobrowserextensions to forbid the installation of any new ones.

pluck + require eimadpbcbfnmbkopoojfekhnkhdbieeh
pluck + require abcd...
pluck + require defg...
. . .
pluck + nobrowserextensions

Tip: only use one browser

If you’re using a setup that relies on requiring/blocking browser extensions using one of the methods described above, it’s a good idea to simplify by only using one browser.

For example, to only allow Edge:

pluck - noedge
pluck + okedge
pluck - okfirefox
pluck + nofirefox

If you need two browsers, such as keeping one for work and the other for personal browsing, take care to make sure you have the same extension(s) on both browsers and match it with the browser-specific require rules.

Last updated: 2026-08-06