Brave Removal?!

[Max Stern]

Now I can't access this extension on Brave. I switched from Chrome to Brave so I could use this extension. 

[Mac Singh]

I guess it's time for me to move to mountains :(

lemme know if you find any solution or similar alternative. 

Thank you 

[Carlos Rodrigues]

I managed to use the extension again download the crx file from an alternative source and dropping it on the brave extensions pages with the developer enabled

Alternative source: crx4chrome through the "Download Crx From Crx4Chrome" option

[H Rosenmayer]

How did you download it? I've paid for this on a monthly basis and really hope you could maybe help me get it back. It has taken my business to the next level in efficiency!

[Michael Lepori]

@Max Stern. I did the same. From Chrome to Brave for this extension and also for Brave Shield.

Is there a solution?

[Daniel Christoffer]

I'm running Brave 1.92.134 and found a very simple way to reactivate AutoControl even though it has been disabled as a Manifest V2 extension.

1. Open Manage Extensions (brave://extensions/).
2. Click Details on the AutoControl extension.
3. Open the Developer Tools by right-clicking the enable/disable toggle and selecting Inspect.
4. In the DevTools, locate the <leo-toggle> element. It has a disabled attribute which prevents the toggle from being used.
5. Remove the disabled attribute, and the toggle immediately becomes clickable again.
6. Turn the extension back on.

I can't remember whether the disabled attribute was on the <leo-toggle> element itself or on one of its child elements, as it disappeared after I enabled the extension.

After re-enabling it, I restarted both Brave and my PC. The extension remained enabled and continues to work normally.

This is now the second time I've had to work around Manifest V2 restrictions, first Chrome, and now Brave.
Because of this, I'm starting to migrate my automations to Tampermonkey.I'd rather not rely on browser-specific loopholes that could disappear with the next browser update if Manifest V2 enforcement becomes even stricter.

Hopefully this information helps identify what's preventing the extension from being enabled, as it appears the extension itself still functions correctly once the UI restriction is removed.

[T K]

Awesome, Daniel, that worked for me as well.

I'm also glad the website is back up and running - Does anyone know why it went down and started redirecting to random malware pages? (At least that's what my antivirus warned me about.)

Lastly, it would be great if we could get a Manifest V3 compatible version, just in case.

[H Rosenmayer]

Could someone help me figure this out? I've been trying for an hour and can't figure it out. I'm in the inspect page, but can't figure out where I need to go after that.

Thanks for any help

[Dylan Bay]

Not the original poster, and it's different now that I changed it, but the inspect will bring up an inner piece, I think I went up a level or two (currently labeled 'cr-toggle' for me at least and the toggle switch highlights) and there's a spot where it says near the end on the line "disabled". I just right clicked that line in the inspector, Edit Element, select the "disabled" text and type "enabled" instead. Then you can toggle it back on as normal. Dunno if it persists across restarts or updates, however.

[Gray]

I think I accidentally removed the extension after the brave fallout.

Is there a way to reinstall it and get it working again?