MacOS TCC silently messes up things that depend on brew installed libraries

[mnorrsken]

Output of brew config

HOMEBREW_VERSION: 6.0.17
ORIGIN: https://github.com/Homebrew/brew
HEAD: 4dacfe77a24dead72de749c0876028b77b99cd04
Last commit: 10 days ago
Branch: stable
Core tap JSON: 16 Aug 21:03 UTC
Core cask tap JSON: 16 Aug 21:03 UTC
HOMEBREW_PREFIX: /opt/homebrew
Homebrew Ruby: 4.0.6 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/4.0.6/bin/ruby
CPU: deca-core 64-bit arm_hidra
Clang: 21.0.0 build 2100
Git: 2.50.1 => /Library/Developer/CommandLineTools/usr/bin/git
Curl: 8.7.1 => /usr/bin/curl
macOS: 26.5.2-arm64
CLT: 26.6.0.0.1781586589
Xcode: 26.6
Metal Toolchain: N/A
Rosetta 2: false

Output of brew doctor

Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: Unbrewed header files were found in /usr/local/include.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae and may need to be deleted.

Unexpected header files:
  /usr/local/include/node/*

Description of issue

So, I'm not sure how to explain my issue but it started when I was running SupaCode (terminal client) and then using claude code, lazygit, opencode and other applications that I had installed with homebrew. The issue was that I could not access local network when runnin inside supacode (sometimes not even the DNS because I run a local forwarding one), but I never got a question from macos if I wanted to allow this. However if I ran the applications in iTerm everything worked fine! Eventually I reinstalled claude code from official package and that started working again inside of supacode terminal. However I could not get opencode to work however I did! Then I realized that opencode was using my brew installed nodejs, so I reinstalled this with the official package and opencode also started working!

I have no idea whats at fault here, is it macOS TCC thats just impossible to work around? Is it some issue with how brew applies security settings to its packages? Is it some issue with supacode (but it seems that they handle everything correctly, local network is allowed for supacode itself)... it all makes my head hurt.

The solution for the moment is that I have to not use brew install for any applications I want to run from Supacode which are also accessing the local network... I have no idea why not more people have this issue but maybe they are not using a lot of services (AI MCPs etc) running on local network.