Version 1.71.121 Chromium: 130.0.6723.91 (Official Build) (64-bit)
The above release for Linux ignores the --proxy-server flag. Merely 23 days ago, I could proxy an earlier Brave version through a system tor daemon via SOCKS5. I checked IP address in Brave to verify. With the latest release, Brave seemingly ignores --proxy-server entirely. My IP address is naked. I am not using “tor tabs” here but the system tor daemon. Tor tabs do work.
There’s a related issue with the GUI proxy panel nested deeply inside settings menus. I do not use a standard Linux desktop, just Wayland Sway, a window manager. The GUI panel tells me it can’t handle that, but only knows system settings for GNOME or KDE, and instructs me to study the Brave man pages for custom invocation switches. Well I know the switches, and even tried several variations, but the generic Linux release has no man pages in the first place. Perhaps the .deb and .rpm bundles do have man pages, but the generic Linux .zip file does not.
I do not understand why proxy settings should need a particular desktop. Such generic Linux infrastructure does not need gobject or KDE calls. Firefox has no problem using the proxy on my system.