Persistent accessibility issues on 26.4.1
- Dominant language
- C
- Stars
- 29.6k
- Forks
- 750
- PR merge metrics
- No merged PRs in 30d
Description
I've installed yabai, but executing any command gives me this error: `yabai-msg: failed to connect to socket..`
Did the exact same install on a duplicate machine yesterday and had no such trouble. Yabai is turned on for accessibility permissions in Settings. However, running `/opt/homebrew/bin/yabai` gives me this: `yabai: could not access accessibility features! abort..` which triggers a redundant accessibility request that does nothing.
Tried uninstalling and reinstalling—same thing.
I see there's a lot of conversation about this elsewhere on this repo, but all the issues appear to be slightly different from mine or using an earlier macOS. I'm on macOS 26.4.1.
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the failure on macOS 26.4.1 by running /opt/homebrew/bin/yabai and a yabai command, then inspect why the reported accessibility permission is not recognized and why the socket is unavailable. Done means yabai can access accessibility features and commands connect without triggering a redundant permission request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, macos
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100