Frequently Asked Questions
Does Glint work with my monitor?
▼
Most external monitors support DDC/CI. If your monitor has an OSD with brightness/volume controls, it almost certainly supports DDC. Works over HDMI, DisplayPort, and USB-C/Thunderbolt. Some USB-C hubs may block DDC signals — try connecting directly if you have issues.
Why does Glint need Accessibility access?
▼
To intercept media key events before macOS processes them, Glint uses a CGEventTap, which requires Accessibility permission. Without it, Glint can't detect brightness/volume key presses. This is a standard macOS security requirement for any app that reads keyboard input.
Is this safe? Why isn't it on the Mac App Store?
▼
Glint is open source (read every line!) and notarized by Apple (malware-scanned). DDC requires IOKit I2C access, which the App Store sandbox blocks. This is the same reason BetterDisplay, MonitorControl, and Lunar distribute outside the Store.
How do I get settings back after hiding the menu bar icon?
▼
Open Glint from your Applications folder (or Spotlight search for "Glint"). When the app detects it's being re-opened, it automatically shows the settings window.
Can I control multiple monitors?
▼
Yes! Glint detects all connected external displays and adjusts them simultaneously when you press brightness or volume keys.
What's the CPU/memory usage?
▼
Effectively zero when idle. Glint uses a CGEventTap which is interrupt-driven — no polling, no timers, no background threads. Memory footprint is under 15 MB.
Does it conflict with BetterDisplay / MonitorControl?
▼
Possibly — if two apps both intercept the same media keys, they may interfere. We recommend using one DDC controller at a time.