Repository navigation
Keybase Finder Integration refuses to load in MacOS 27.0 Beta (26A5368g) #29355
Description
Describe the bug
Enabling Keybase Finder integration in MacOS 27.0 Beta (26A5368g) generates an error, and the Keybase file system is not exposed.
To Reproduce
Steps to reproduce the behavior:
- Ensure you are running MacOS 27.0 Beta (26A5368g)
- Navigate to Settings > Files > Enable Finder Integration
- Follow the instructions to enable kernel extensions
- Restart the Mac twice to confirm the extensions are enabled.
- Restart the Keybase application
Expected behavior
Keybase Finder integration should be possible when running Keybase for Mac.
Screenshots
The exact error message is:
We were unable to load KBFS (Fuse kext). This may be due to a limitation in MacOS where there aren't any device slots available. Device slots can be taken up by apps such as VMWare, VirtualBox, anti-virus programs, VPN programs and Intel HAXM.
Please run
keybase log sendto report the error.
I have run keybase log send. my log id: b5b67a3156c6bf8c106e5e1c
Additional numbers
The number 345567
Activity
shallax commentedon Aug 18, 2026
Ahh, the annual "will Keybase actually get their act together and make this work before the new MacOS reaches release date?"
benrfairless commentedon Aug 18, 2026
I've moved our workloads away from Keybase because of this shrug
kg4zow commentedon Aug 27, 2026
Given Keybase's past history of not even looking at the macOS beta versions ahead of time, my guess is that we'll have at least a few weeks during with Keybase just plain won't work on macOS 27.
If only Keybase/Zoom would spend the time figuring out how to write a macOS File Provider instead of relying on a kernel extension, especially since Apple has already announced that kernel extensions are deprecated, and will be removed in "some future version".
FWIW, I remember I also had trouble with the same error message when I upgraded to macOS 26. I forget the specifics, but I remember having to reboot a few times, and I remember having to manually give something permission that it didn't have, under "System Settings → Privacy & Security".
kg4zow commentedon Sep 23, 2026
Not sure if anybody at Keybase is going to see this or not, but if so, I just powered on a machine that I had upgraded from macOS 26 to 27, and got a pop-up about an error installing what I assume is the kernel extension which allows KBFS to be "mounted" as part of the filesystem, and therefore visible in Finder.
Log ID: 94a8aab2cc5b0f66b01c691c
Also, after I cleared the popup, the main window just sat there with the Keybase logo in it, doing nothing. I finally had to "Quit Keybase Completely" and run it from scratch again. After I did this, the client seems to be working normally but is aware that the "Finder Ingegration" isn't there (Settings → Files shows the "Enable Finder integration" button).
Elbje commentedon Sep 25, 2026
Same here, the finder integration does not work anymore after upgrading from MacOS 26 to 27. If I click on the "Enable Finder integration" button, it starts loading and then nothing happens. No error.
Log ID: 69ba0f6c3b95d5db72d04f1c
marcofranssen commentedon Sep 28, 2026
A recompile with new fuse libraries is required.
kg4zow commentedon Sep 28, 2026
Sure. But when is, or is, that going to happen?
This has been a recurring issue with every macOS major update, going back to at least macOS 14→15. Apple makes the new macOS versions available to developers several months before they are publicly released, and almost every other company that makes Mac software uses them to make whatever updates are needed to work with the new OS, so that things work with the new OS on release day. For the macOS 15→26 upgrade they had a new client out the next day - maybe it was silly of me, but I hoped they had learned their lesson and would have new versions out more quickly.
At the very least, it would be nice if somebody from Keybase/Zoom would at least acknowledge the issue, and give us an idea when we can expect a new version.
As for moving away from Keybase ... I've been slowly doing this as well. For the services which are important to me, I'm using ...
Encrypted file storage: Proton Drive. My one complaint is that it doesn't offer a "shared drive" between users, even when those users are part of a (paid) family group.
Encrypted git repos: FOKS. It was written (and is actively being developed) by one of the two guys who started Keybase, who has described it as "Keybase done right" (paraphrasing). At the moment it has encrypted key-value storage (with a hierarchical namespace, so the keys "look like" path names) and encrypted git repos implemented using key-value storage. Unlike Keybase, the "server bits" are also open source, so you can run your own FOKS server if you like. If you don't want to, he offers accounts on his own production FOKS server.
Encrypted chat: Signal. It's free, but it requires an iOS or android PHONE in order to create an account (although they're working on a way to allow signups without a phone number). It doesn't support "teams" the same way Keybase and FOKS do, but they do allow "group chats" the same way most phones' built-in "messenger" programs do.
marcofranssen commentedon Sep 28, 2026
Ever since, the team has been doing an update, I have always postponed my MacOS upgrade waiting for them to compile with the new Fuse system. As far I know they still do the maintenance of these kind of things. For the remainder don't expect new features.