It's been a busy couple of days for DualClip. What started as a frustrating crash investigation turned into a series of meaningful improvements — from fixing a deep resource-bundling bug to shipping Homebrew support. Here's a rundown of everything that changed.
The Crash That Wouldn't Quit
Shortly after v1.2.0, DualClip started crashing on launch for some users. The crash report pointed to Bundle.module inside the KeyboardShortcuts dependency — a fatalError triggered because the app couldn't locate its resource bundle at runtime.
The root cause turned out to be a subtle mismatch in how Swift Package Manager bundles resources for standalone .app builds:
- SPM generates a file called resource_bundle_accessor.swift that looks for resources at Bundle.main.bundleURL — which resolves to the .app/ root directory.
- But macOS codesigning requires all resources to live inside Contents/Resources/, not the app root. Placing bundles at the root causes an "unsealed contents" signing error.
- So the resources were in Contents/Resources/, but the code was looking at .app/ — and finding nothing. The fix was surgical: after the initial build, we patch the generated accessor to use Bundle.main.resourceURL! (which points to Contents/Resources/), then recompile just the affected module and re-link the executable. SPM regenerates the accessor on every full build, so we had to carefully avoid triggering a rebuild after patching. The final binary is verified with strings to confirm the patch is baked in.
This fix ships in v1.2.6 and the crash is fully resolved.
Homebrew Support
DualClip is now installable via Homebrew:
brew install RAKKUNN/tap/dualclip
We set up a dedicated Homebrew Tap with a Cask formula that points to the latest signed and notarized release. The CI pipeline automatically updates the formula (version + SHA256) whenever a new release is tagged — zero manual steps.
What Makes DualClip Different
After analyzing 57 macOS clipboard managers, one thing stood out: every single one is a clipboard history manager. DualClip is the only one that uses dedicated slots.
The difference matters:
History managers record everything you copy and let you scroll back through it. Great for recall, but adds complexity — databases, search UI, sync, storage limits.
DualClip gives you 3 fixed slots with instant keyboard access. You decide where to copy, not when to find it later. No history, no scrolling, no search.
It's also one of the few clipboard tools that stores absolutely nothing to disk. Everything lives in RAM and vanishes on quit. No network access, no telemetry, no cloud sync.
Try It
brew install RAKKUNN/tap/dualclip
Or grab the latest release from GitHub.
DualClip
A lightweight macOS menu bar app that provides multi-slot clipboard management.
Unlike history-based clipboard managers, DualClip gives you instant access to dedicated clipboard slots via customizable keyboard shortcuts
Features
- 3 Clipboard Slots: Slot A (system default), Slot B, and Slot C
- Customizable Shortcuts: No hardcoded key conflicts — configure your own shortcuts
- Atomic Paste: Seamlessly pastes from any slot without corrupting your system clipboard
- Menu Bar Popover: Quick-glance view of all slot contents with previews
- Privacy First: All data lives in RAM only — nothing is persisted to disk
- Zero Network Access: No telemetry, no analytics, no internet communication
Demo
Default Shortcuts
Action
Shortcut
Copy to Slot B
⌥⌘C
Paste from Slot B
⌥⌘V
Copy to Slot C
⌃⌘C
Paste from Slot C
⌃⌘V
All shortcuts are fully customizable in Settings > Shortcuts.
How It Works
- Slot A automatically mirrors the…
Signed and notarized by Apple — no Gatekeeper warnings.
DualClip is open source under the MIT license. Issues, feedback, and contributions are welcome.
Thank you, have a nice day!
Top comments (0)