Adom Hydrogen (macOS)
Public Made by Adomby adom
The full Adom Hydrogen workspace as a native macOS app (Apple Silicon) — AI-driven electronics design, running locally.
Screen Recording dialog asks to toggle Adom Hydrogen ON, but Hydrogen is not in the macOS Screen Recording list (dialog waits forever)
What happens
A panel screenshot request makes Hydrogen show its "Allow Screen Recording" dialog, which says to toggle Adom Hydrogen ON under System Settings → Privacy & Security → Screen Recording. But Adom Hydrogen is not in that list. Only Adom Bridge is there (already enabled). There is nothing to toggle, so the dialog sits on "Waiting for you to enable it… this closes automatically once it's on" indefinitely. It dims the whole Hydrogen window until the user clicks "Not now".
Screenshots: the Hydrogen dialog, then the macOS Screen & System Audio Recording list opened from its button (no Adom Hydrogen entry).
Environment
- Adom Hydrogen (macOS) 0.1.418, bundle
inc.adom.hydrogen, Team IDB22GYTS2NN, hardened runtime - macOS 26.3.1, Apple Silicon
- Adom Bridge installed on the same Mac with Screen Recording granted
Steps to reproduce
- From an AI session in the Hydrogen container, request a panel capture of any open Web View tab:
(defaultadom-cli hydrogen screenshot panel --name "<any webview tab>" --reason "test"--method element-capture) - The CLI returns
Error: Failed to capture panel. - Hydrogen shows the "Allow Screen Recording" dialog: To capture "shell", Adom Hydrogen needs macOS Screen Recording permission.
- Click Open Screen Recording settings. System Settings opens Screen & System Audio Recording, and Adom Hydrogen is not listed.
- The dialog never closes on its own. Each new capture attempt brings it back; it appeared twice in one session.
Expected
- Hydrogen appears in the Screen Recording list so the user can toggle it, ideally via the system consent prompt.
- The dialog has a way forward when the app is missing from the list, instead of waiting forever.
- The CLI gets a specific permission error (e.g.
screen_recording_not_grantedwith a hint), not a generic "Failed to capture panel".
Leads
Info.plisthas noNSScreenCaptureUsageDescription(PlistBuddy -c "Print :NSScreenCaptureUsageDescription"→ Does Not Exist).- The app never shows up in the TCC list. That suggests the custom dialog is shown without first triggering the system request (
CGRequestScreenCaptureAccess()or a ScreenCaptureKitSCShareableContentcall), which is what adds an app to the list. - The dialog names the capture target "shell", which looks like an internal name leaking into user-facing text.
- The request came from an AI in the container, but the human got an unexpected, blocking system-permission modal. Consider surfacing it as a notification, or failing fast to the caller with the hint, instead of a full-window modal.
Not yet tried: adding Hydrogen by hand with the list's "+" button.


2 Replies
Log in to reply.

