This looks cool enough, but it’s starting to drive me crazy how people are in such a rush to put out their macOS apps they can’t be bothered to get a developer account and run a one line command. It’s not hard.
I used to be sympathetic to complaints about not wanting to pay the developer account fee. But when you’re vibe coding, you’re probably paying a good chunk of change to your LLM supplier of choice every month, and the yearly developer account fee seems minor in comparison
Also, it’s just such a bad security precedent. This page describes the error you get as “the typical macOS Gatekeeper warning”, as though it were just another piece of corporate silliness, like clicking through a EULA.
Nice, but, and this is not personal, I would not trust this app with my computer internals. Probably also asks for sudo from time to time.. but I might ask Claude to make something similar for myself.. (sorry but just being honest)
I might consider adding this in a future release, although at this point I'm focusing on keeping the app's footprint minimal, so every feature addition has to be carefully considered :)
The pricing debate is interesting. I'm running a similar service and found that giving away as much as possible for free helps build initial trust — getting people to actually try it once is the hardest part.
Pre-release feedback from the community is definitely valuable though.
I didn't know this part is the most diffcult.
in your "demo" image the menu bar is completely missing.. this seems like a very confusing choice. I can barely make out the menu bar icon against the background image.
I get that there's a market to put command line preferences in a GUI wrapper, but wasn't HN going to limit posts from new accounts? Oh, it's not in Show HN. They found a loophole.
Meanwhile, I'm running Claude Code and asking it to make me stupid bespoke things that only I want and I'm not spamming the internet with those tools because they aren't novel or useful for most people and you can have Claude Code build a version for the way that you work.
Go away, green accounts. Everyone is pretty tired of your presence.
Cool! Disappointing there's so much focus on the non-sandboxing, I think it's a reasonable trade-off to release early, and follow up with signing later.
- Website looks great overall, but the fixed and overlaid header title is awkward and hurts readability for not much benefit.
- Battery Health on my M3 Max MBP reads as "1%", when System Report shows Condition: Normal, Maximum Capacity: 100%. What is this reading from?
- Handy password generator is great; any chance of an option for "correct horse" [0] style passwords? I find these are preferable for reasonably secure passwords which can still be remembered or hand-typed as needed.
Yes, the pre-release is intended for testing purposes, so thanks for bringing the battery health issue to my attention. It is calculated from the the battery's reported design capacity and current capacity, but the reported values seem to be unreliable across different systems.
The password generator suggestion is interesting, but I intentionally gave the user only one password generator option in the base version of the app - the most secure one :)
I was skeptical that I’d find it useful since I can do all of these shell commands and such, but one feature I like is being able to effectively pare the feature set down to just what you need, making for a small but very useful menu.
27 comments
[ 3.1 ms ] story [ 50.5 ms ] threadAn example is I have my airpods bound to ctrl+alt+b to connect via Bluetooth. This is to have it yank back control from my android phone.
I used to be sympathetic to complaints about not wanting to pay the developer account fee. But when you’re vibe coding, you’re probably paying a good chunk of change to your LLM supplier of choice every month, and the yearly developer account fee seems minor in comparison
Also, it’s just such a bad security precedent. This page describes the error you get as “the typical macOS Gatekeeper warning”, as though it were just another piece of corporate silliness, like clicking through a EULA.
I might consider adding this in a future release, although at this point I'm focusing on keeping the app's footprint minimal, so every feature addition has to be carefully considered :)
Pre-release feedback from the community is definitely valuable though. I didn't know this part is the most diffcult.
Meanwhile, I'm running Claude Code and asking it to make me stupid bespoke things that only I want and I'm not spamming the internet with those tools because they aren't novel or useful for most people and you can have Claude Code build a version for the way that you work.
Go away, green accounts. Everyone is pretty tired of your presence.
- Website looks great overall, but the fixed and overlaid header title is awkward and hurts readability for not much benefit.
- Battery Health on my M3 Max MBP reads as "1%", when System Report shows Condition: Normal, Maximum Capacity: 100%. What is this reading from?
- Handy password generator is great; any chance of an option for "correct horse" [0] style passwords? I find these are preferable for reasonably secure passwords which can still be remembered or hand-typed as needed.
Looking forward to seeing how the app evolves!
[0] https://www.correcthorsebatterystaple.net
Yes, the pre-release is intended for testing purposes, so thanks for bringing the battery health issue to my attention. It is calculated from the the battery's reported design capacity and current capacity, but the reported values seem to be unreliable across different systems.
The password generator suggestion is interesting, but I intentionally gave the user only one password generator option in the base version of the app - the most secure one :)
https://sindresorhus.com/supercharge
I was skeptical that I’d find it useful since I can do all of these shell commands and such, but one feature I like is being able to effectively pare the feature set down to just what you need, making for a small but very useful menu.