The onboarding workflow is getting pretty old, so I gave it a facelift.
It's now paginated, includes a disclaimer that Cork is not affiliated with Homebrew, and has a cool screen-switching animation.
Check it out: https://drive.tomoserver.eu/f/125eb02b155849f8aa07/
Since some operations (well, probably most of them) require Cork to manipulate data of other apps, it needs Full Disk Access permissions.
Until now, if Cork didn't have these permissions, it would fail the operaiton and the system would sometimes, and sometimes not, prompt you to grant Cork these permissions.
Coming in the next version is a built-in way to grant Cork these permissions.
Check it out: https://drive.tomoserver.eu/f/a59536d1911c4913b07e/
Marketing people would definitely tell me to not write what I'm about to write. But I believe I should.
Before we go further, today has once again confirmed that Cork remains the only GUI for Homebrew that is not AI-made slop.
What am I even talking about? @ghall notified me yesterday that Homebrew released their first-party GUI. It would be cowardly to not address that situation head-on.
It will definitely make the future of Cork ever so grimmer. Unfortunately, we will never be listed on Homebrew's homepage.
I originally made Cork, as I have said many times, to make it easier for everyone to use Homebrew. Once I started noticing that Homebrew is lacking in many aspects, I started rewriting Homebrew itself.
Homebrew has always had one glaring weakness: their rude community. This is a problem I can thank only you for fixing. I like to think that we're a much friendlier bunch than the Homebrew that told me to fuck off when I seeked friendly cooperation all those years ago.
So it is only fitting that they have now once again shown their true colors, releasing software that is completely AI made. I won't link it here, you can look it up yourself. The vast majority of commits are made by Claude. Still, it is a direct competitor to Cork.
What makes this one different is that it has official Homebrew backing. And many on the wider web genuinely don't care that it's made by a group backed by corporate donors that use AI like it's the greatest invention in history; a complete antithesis of what Cork stands for.
I am not making this post to try to get anything from you. I merely believe in transparency. And to be transparent, this will be a very tough situation to handle.
We don't use AI, nor do we have corporates pouring hundreds of thousands into the development of Cork. Hell, Cork has been deep in the red for the last couple months.
Yet I believe we can prevail. I will certainly not give up and let them win.
Release 2.0.3 brings support for Goldern Gate, or macOS 27.
It is otherwise identical to version 2.0.1 that came out a few days ago, with one exception:
None in this release.
None in this release.
You may ask, what happened to version 2.0.2?
That came out yesterday and was release 2.0.1 recompiled for Golden Gate. But a merge conflict overwrote double-click handling, so I fixed that quickly.
Happy Corking!
As always: there was absolutely NO AI used in the development of Cork, and we strongly reject AI in any capacity: https://corkmac.app/our-ai-stance/
I just compiled version 2.0.1 on Golden Gate, with a few adjustments needed to resolve build errors. Hopefully just quirks of Xcode 27 still being a beta:
It will be ready on day one of Golden Gate's release, CEST (UTC+2)
If you'd like to try it now, it's on the branch main.golden-gate
Here's a solution to that build error: https://github.com/buresdv/Cork/issues/678
In short, it's because of the order of targets for compiling being incorrect. There's an image in the module CorkTerminalFunctions, and if that module is not compiled before the other modules, the compilation will fail (because it thinks there's that picture missing).
Not even a month after I released Cork 2.0.0, which was the most significant release in the history of Cork (and undoubtedly in the history of Homebrew GUIs that aren’t made by AI... 
), a new version is already out.
As always, no AI is used at any point in the development of Cork, and we stand by that with Cork’s strict no AI policy, which remains among one of the strictest in the space.
The grind never stops, so I'll be showing off the things coming to version 2.0.1 in this thread
I'm currently working on implementing the new tap trust system, and making it actually bearable to use:
Video of the current state of drag-and-dropping
As a bonus, I have accidentally created a drag-and-drop way to back up individual taps, which I may expand to packages as well, and eventually, an entire independent backup system...
I'd like to hear your opinions on the new version - did it make Cork more useful? What do you think about the way it was developed, etc?
Everything is described in this article on the wiki:
Getting a Rikidar Authenticator account
TL;DR
This forum uses SSO (Single Sign-on) through Rikidar Authenticator (which is a self-hosted and encrypted PocketID server). You can then use that account to log in anywhere in the network.
If you'd like to read more about Rikidar Authenticator, read this page: Rikidar Authenticator
The whole wiki is useful: Rikidar Wki
