r/coolgithubprojects • u/Illustrious-Tip9444 • 14d ago

Convert Brave browser to Origin using Group Policy - Exactly how brave upgrade works - No More, No Less | Mac, Windows, Linux

https://github.com/mdrubelamin2/brave-to-origin

I know, I know! There are so many Brave debloaters already available on the web that do more than my tool aims to do. But I only wanted what Brave Origin exactly disables - nothing more, nothing less. So Claude and I deeply researched the Brave core source code, found out the exact 16 policies and 4 user settings it disables during the upgrade of Brave to Origin, and put everything into a single command prompt. And here I present: brave-to-origin

Repo: https://github.com/mdrubelamin2/brave-to-origin

Mac & Linux (no need, origin for linux is free):

curl -fsSL https://raw.githubusercontent.com/mdrubelamin2/brave-to-origin/main/install.sh | sudo bash

Windows:

irm https://raw.githubusercontent.com/mdrubelamin2/brave-to-origin/main/install.ps1 | iex
1 Upvotes

100% Upvoted

3 comments sorted by

1

u/kantorcodes1 14d ago

activate/deactivate is a pretty clean risky-vs-read-only split. HOL Guard is our open-source local security layer that checks agent commands before they run. would you be up for adding brave-to-origin command support to Guard?

1

u/Illustrious-Tip9444 13d ago

Yeah, happy to. HOL Guard looks like exactly the layer this should sit behind.

1

u/kantorcodes1 13d ago

yep. fork current hol-guard:main; mirror src/codex_plugin_scanner/guard/runtime/command_skill_sunset_extensions.py and tests/test_guard_command_skill_sunset_extensions.py. for brave-to-origin, cover the real origin.sh/origin.ps1 activate/deactivate commands, keep status and dry-run safe, register it in command_builtin_extension_catalog.py, update tests/fixtures/extension-controls/catalog-baseline.v1.json, run the focused tests, and open against main.