TL;DR: We recommend all users download and install https://www.microsoft.com/edge and run pluck + okedge ASAP.

What happened? What is happening?

On 2025-08-01, we started to receive reports that Plucky was suddenly removed from some instances of Chrome.

The first user sent us this, from Chrome 139:

Another user reported Plucky was removed from Chrome 138.0.7204.184.

While the Chrome team had long since claimed they were removing MV2 extensions, the Chrome team had also implied they would allow programs such as Plucky to continue to exist awhile longer. Or so we thought. Apparently we were mistaken!

What are we doing in the short term?

For all devices with synchronized configurations that have the system feature enabled, we have added a new configuration named block-chrome-updates. It is intended only to give us a bit more time to address this problem. We do not intend to block Chrome or other browser updates in the long haul. This configuration may help Windows and macOS computers, but it will not help most Linux devices.

We also added the feature feature:okedge to and removed feature:noedge from these same configurations. We realize this change was invasive, but it seemed better to do this in the interests of those who might otherwise end up “cut off from the Internet” without a clue why and no interface to inform them.

We are sending out a notification to inform users, asking them to install Edge () because out of Chrome, Brave, Vivaldi, and Edge, we think Edge may be the most reliable. Once again, Microsoft shows its committment to not breaking software, and for that we’re grateful.

Here’s a link to download Edge https://www.microsoft.com/edge .

What are we planning for the long term?

We are not yet sure. We may ship our own version of Chrome. Or we may eat crow, and try to jump back to Firefox. Both courses will take some time. But the problem is quite high priority for us.

Chrome 138

Plucky should work in Chrome 138. But if it stops working, you can probably make it work again using this advice from https://www.reddit.com/r/uBlockOrigin/comments/1itw1bz/end_of_support_for_ubo_on_chrome_chromium/ :

First set:

  • chrome://flags/#temporary-unexpire-flags-m137 [Enabled]

Then restart Chrome and you can set:

  • chrome://flags/#extension-manifest-v2-deprecation-warning [Disabled]
  • chrome://flags/#extension-manifest-v2-deprecation-disabled [Disabled]
  • chrome://flags/#extension-manifest-v2-deprecation-unsupported [Disabled]
  • chrome://flags/#allow-legacy-mv2-extensions [Enabled]

What else?

We’re still collecting information as it comes. We’ll update this page and/or notify users as the situation develops.

Plucky users may also visit this forum post to see more discussion.

Questions from users

  1. How can I avoid the notification on every browser start?

    As of 2025-08-02, if you click on URL in the notification (that goes to this very page!), it should not appear again.

  2. On Ubuntu Linux with okedge and not noedge, should msedge work?

    Yes, but it may require temporarily allowing msedge. Try running this command:

    pluck + now+30m allow program msedge port:443

    If your delay is long, you can expedite the change:

    pluck expedite msedge

    Once the rule is effective (use pluck find msedge to tell), then restart edge.

  3. If Plucky is removed from Chrome, does that mean that Chrome will suddenly be unfiltered?

    No. If the system feature is enabled, Chrome 139 will be blocked when Plucky is removed.

Last updated: 2025-08-01