Yesterday, Brave was working perfectly fine with Grammarly.
Today, Brave and Grammarly don’t like each other.
Grammarly keeps telling me that I’m not logged in, even though I am and tries to redirect a new login to Chrome, which I don’t actually use.
There are other behavioral issues with Grammarly as well, which are difficult to describe.
I downloaded and installed Chrome, and Grammarly works perfectly with Chrome.
Has an update gone through lately that has “upset” Grammarly, or is this a Grammarly issue?
Are there settings I should use to work with Grammarly?
Because of the accurate timing of your observation, my guess is that the recent Chromium update to v134.0.6998.178, is the probable cause of “Brave and Grammarly” having a sudden disagreement.
Brave Browser being updated to 1.76.82 in order to include that Chromium update ← updated by Chromium because of CVE-2025-2783:
Someday, a subsequent update - taking into account some issues caused by BB v1.76.82 (Chromium v134.0.6998.178) - will come along, I expect.
I would test your issue, by:
disable anti-virus
disable ALL of extensions that you have installed
In a Brave Browser New Window, go to:
brave://settings/clearBrowserDataAdvanced tab
Time range: All time
ENABLE:
Cookies and other site data
Cached images and files
Click Clear data
Exit / Quit everything, and restart the computer.
Then install the Grammarly extension and test.
Sometimes, the order of installation of extensions, matters.
Sometimes, the installation of any anti-virus extension in last place, fixes things. And sometimes, installing an ad-block extension BEFORE that anti-virus extension, matters.
Yeah, I think that Grammarly themselves have broken it.
According to Grammarly, they do not support the Brave Browser.
So, it’s all on Grammarly and they don’t seem to care.
Grammarly (including Coda) engages certain third-party vendors (i.e., subprocessors) listed below to help us operate, provide, improve, integrate, customize, and support our services when we process Customer Personal Data (as defined in our Data Privacy Addendum) on behalf of our business customers.
The table below identifies Grammarly’s subprocessors, details the purpose of their services, and server location. The subprocessors we engage may change from time to time and we may add or remove subprocessors in the future. We will post updates to our subprocessors on this page.
In order to use Grammarly, I would ALLOW JavaScript for each of the 27 following domains / hostnames; and make sure that none are blocked by some firewall or DNS service:
Just note, shields ads&trackers doesn’t protect you at extension level. If Grammarly has lots of 3p trackers, I would personally avoid it. Probably doesn’t help with memory or battery usage either.
