Should I vibe code
Five everyday Mac tools tucked into the MacBook notch
A clipboard manager is a plaintext log of every password you copied. Build it — keep it off iCloud.
?
Their verdict, the Monthly price and the build-time estimate come from their entry, MIT-licensed. Checked 2026-08-04.
?
Our verdict, the regret score and everything below it. Editorial and unsponsored — nobody can pay to be moved.
The honest answer
why the verdict is what it is
Five small utilities in a panel pinned under the notch — media controls, clipboard history, window switching, a file shelf, screen warmth. All local, none of them touching anything you cannot restart, and the worst realistic outcome is a Swift process leaking memory until you kill it. One part deserves an adult conversation: clipboard history is a plaintext log of every password and one-time code you copied this month, and it is the single file in this app you would not want synced. Everything else is a genuinely enjoyable weekend of AppKit.
What actually breaks
not "if". the specific failures.
- Clipboard history written to disk in plaintext, in a folder iCloud Drive or Dropbox is cheerfully syncing off the machine
- The Accessibility permission window management needs — the same grant that lets a process observe everything you type
- Notch geometry, which is not the same on a 14-inch, a 16-inch, an external display, or after the next macOS release
- A panel that insists on floating above everything, including the system prompt you needed to read
- The background process quietly leaking memory for six days, noticed only when the fans come on
Is that you?
the verdict is a default, not a law
- It runs on your own machine and never phones anywhere
- Clipboard history is capped, encrypted and excluded from anything that syncs — ideally all three
- You are on a current macOS and can accept re-fixing the geometry every autumn
- You are distributing it, at which point notarisation, sandbox entitlements and explaining the Accessibility prompt become a support job you did not price in
- The clipboard store is plaintext inside a synced folder
- You need it to keep working on a Mac you cannot update
If you build it anyway
the checklist, then the prompt that enforces it
- Clipboard first, and carefully: cap the history, skip pasteboard items flagged as concealed, ignore anything copied from a password manager, and exclude the store from backups and sync.
- Keep history inside the app container, encrypted, with entries expiring on a timer. A month of copied one-time codes is not a feature.
- Request Accessibility only when the window feature is first used, and explain in the same sentence what it grants.
- Do not hardcode notch dimensions. Read safe-area insets from the active NSScreen and handle the no-notch case, because external monitors exist.
- Never take a window level above modal alerts and system prompts. Covering a permission dialog is how a utility becomes a hazard.
- Ship it unsigned, to yourself, and stop — unless you are ready to run a notarisation pipeline for as long as the app exists.
I am building a macOS menu-bar utility that lives under the notch: media
controls, clipboard history, window switching, a file shelf and a display
warmth toggle. It is for me, on my machine. Apply these and push back if I ask
you to break them.
1. Start with the clipboard, because it is the only genuinely sensitive part.
Store history inside the app container, encrypted with a key from the
Keychain, never in Documents, Desktop or anything iCloud Drive syncs.
2. Honour the concealed-type pasteboard flag that password managers set, and
skip capture entirely when the frontmost app is on a configurable ignore
list. Default that list to the common password managers.
3. Cap history by count and by age, expire entries on a timer, and give me a
one-keystroke "forget everything" that actually deletes the file rather than
clearing a table.
4. Never write clipboard contents to a log line, a crash report or an analytics
event. There is no analytics in this app.
5. Only ask for Accessibility when I first use window switching, and show the
reason in the same dialog. Everything else must work without it.
6. Do not hardcode notch dimensions. Read safeAreaInsets from the active
NSScreen, handle displays without a notch, and re-layout on screen change,
resolution change and display connect.
7. Keep the panel below modal alerts and system permission prompts. Never use a
window level that can cover a security dialog.
8. The file shelf holds references, not copies, and must never move or delete
the original. Dropping a file out is a copy unless I explicitly say move.
9. Watch for retain cycles in the observers — this process runs for weeks. Give
me a way to see its memory use, and tell me which timers you started.
10. Assume no distribution: no auto-update, no telemetry, no licence check.
11. If I later ask to ship this to other people, tell me that notarisation, the
Accessibility prompt and macOS upgrades are the real cost, and that the
author of the app I am copying charges $19.99 once for exactly that work.That one keeps you out of trouble. For the prompt that actually builds it, canivibecodeit.com has one.
their build prompt ↗Or don’t build it
the boring option, and the way back out
$19.99 once, or $4.99 a month, and somebody else fixes it every time macOS moves the furniture. Build your own because you want to learn AppKit, or because the fifth tool should be something the author never wrote — not to save twenty dollars.
Delete the app. Nothing depends on it, nothing else stores its state, and the only file worth a thought on the way out is the clipboard database — remove that deliberately, rather than leaving a month of copied secrets sitting in Application Support long after you stopped using the thing that wrote them.
The app's own GPL-3.0 Swift codebase, still being pushed to. The notch geometry and window-level work you are about to redo is already readable here.
Popular open-source notch utility with media controls and a file shelf — the closest thing to a reference implementation for the fiddly parts.
Questions
The app's own source is on GitHub. Does that change the answer?
It is most of why this is SHIP IT rather than DEMO ONLY. The parts that usually stall a notch project — safe-area geometry, window levels, keeping a panel alive across display changes — are readable rather than guessable. Mind the licence: GPL-3.0 means copying from it makes your app GPL too, which is a non-issue for something you never distribute and a real decision if you do.
Is a clipboard manager honestly worth a credentials risk tag?
Ask what the last two hundred things you copied were. Somewhere in there is a password, a recovery code and an API key. A clipboard manager is a searchable archive of exactly that, and the difference between a fun utility and a bad day is whether the file is encrypted and whether it is in a synced folder.
Why isn't buildEase higher if this is only a weekend?
Because it is AppKit, not React. Models are noticeably weaker at Swift window management than at web work, and the notch specifically involves screen geometry that changes between machines and macOS versions. The existing open-source implementations are what pull this up from a slog to a weekend.
Every week, someone ships something they shouldn’t have.
New verdicts, the worst thing that landed in the trap, and the occasional incident report. No other email, ever.
Clipboard history is a keylogger you asked for. macOS marks password copies concealed; your version has to notice.
Speech in, text out, nothing leaves the machine. Go.
A launcher is a fuzzy search over things you already have. Nothing here can hurt you.
last reviewed 2026-08-04 · verdict is editorial and unsponsored · shared entry data from canivibecodeit under MIT · not legal advice