Press the side button on your iPhone five times in quick succession, and your biometric authentication vanishes. Face ID and Touch ID go dark; only your passcode will do. Apple rolled out this panic button in 2017, a feature that became second nature for anyone who'd thought even briefly about what happens when a device falls into the wrong hands.
On a Mac? Nothing. No equivalent existed—until a security engineer decided he'd had enough of the gap.
PanicLock arrived in early February 2026 with no fanfare, just a GitHub repository and a simple pitch: one click to disable Touch ID and lock your Mac so only a password will unlock it again. Sean Byrne, who built it, has spent years in the trenches of security operations—first security engineer at Patreon, security leadership at Truework and Vannevar Labs, policy work at Dropbox. This wasn't his first rodeo with threat models, and PanicLock shows it. The tool is free, open-source, and does exactly one thing. Sometimes that's all you need.
By mid-April 2026, a new feature had landed: "Lock on Close," which disables Touch ID automatically when you shut the laptop lid. For a certain kind of user—journalists, researchers, anyone carrying sensitive data through airports or past unfriendly borders—that addition hit differently.
Why Now
Timing, in technology as in comedy, is everything. In January 2026, the FBI executed a search warrant at a Washington Post reporter's home and seized devices as part of a leak investigation. The Columbia Journalism Review and the Reporters Committee for Freedom of the Press both scrambled to publish guidance that same month. The message: if law enforcement gets physical access to your hardware, things get complicated fast. Especially when it comes to biometric unlocks.
The legal landscape here is, to put it mildly, a mess. In April 2024, the Ninth Circuit ruled in United States v. Payne that forcing someone to use their fingerprint to unlock a device didn't violate the Fifth Amendment. Less than a year later, the D.C. Circuit said the opposite in United States v. Brown, treating compelled biometric unlocks as testimonial—and therefore unconstitutional. No Supreme Court ruling has settled the question, which means your rights depend on where you happen to be standing when someone asks for your thumbprint.
Byrne's product page doesn't dance around this. "Use shutdown when you can, PanicLock when you can't," it reads. "Shutting down is the most secure option—but when you need your Mac locked now and you'll be back in five minutes, PanicLock is your answer." That's not marketing copy. That's a threat model.
Under the Hood
The mechanics won't win any complexity awards. PanicLock taps into macOS's built-in bioutil command to disable Touch ID temporarily and pmset to lock the screen. After you enter your password, Touch ID comes back to life with its original timeout settings intact. It requires macOS 14.0 or later and a Touch ID-equipped Mac. Installation comes via a code-signed and notarized DMG from GitHub Releases, or through a Homebrew tap if you prefer.
The app runs lean. According to the project's README, the helper process executes only bioutil and pmset—nothing else. No telemetry. No network requests. The source code lives under an MIT License, available for anyone who wants to audit it. For the paranoid (or merely careful), the signing and notarization process is documented in the release notes.
That "Lock on Close" feature, version 1.0.9 on April 17, came from a GitHub contributor named "baka-yuki." It listens for the lid-close state, disables Touch ID, locks the screen. On wake, after you've typed your password, Touch ID returns. The implementation handles wake event timing and relies on a private macOS notification—com.apple.screenIsUnlocked—to detect when you've successfully authenticated.
It's elegant in the way minimalist tools sometimes are: solving one problem without trying to solve twelve others.
The Builder
Byrne's resume reads like a map of security operations at companies that needed to get it right. After founding security and policy operations at Dropbox, he moved through leadership roles at startups working in national security AI and employment verification. His personal site lists PanicLock among current projects, with posts from February through March detailing aspects of the tool's development.
He posted PanicLock to Hacker News in early February with a title that could've been a commit message: "macOS has no Touch ID kill switch like iOS, so I built one." That thread gathered 10 points and four comments—respectable, but quiet. When it resurfaced in mid-April with a new title emphasizing "Lock on Close," the reception sharpened: 247 points, 30 comments, according to a third-party mirror snapshot from April 18.
The difference between those two receptions tells you something about how features land. The first version was useful. The second was useful and timely.
What It Can't Do
Byrne doesn't oversell the tool, which is perhaps the most reassuring thing about it.
In the February Hacker News thread, he noted plainly that PanicLock doesn't purge FileVault encryption keys from memory. Once you've unlocked a Mac after booting, it stays in "After First Unlock" (AFU) state—disk encryption keys remain accessible in memory until you fully shut down. Only a complete shutdown returns the system to "Before First Unlock" (BFU) and purges those keys entirely.
The README also acknowledges that PanicLock only disables Touch ID. Apple Watch unlock? Still works. Security keys? Also still active. If you need airtight security, you're told to disable those methods or just shut down.
This is the tension PanicLock exists inside. It's not a replacement for powering off—it's a compromise for moments when powering off isn't realistic. Maybe you're stepping away from your desk for five minutes. Maybe you need to hand your laptop to airport security without worrying they'll unlock it with your fingerprint while you're arguing about lithium batteries in your carry-on.
Real-world security, Byrne seems to understand, often means choosing the least-bad option in the time you have.
Quiet Growth
As of mid-April, PanicLock had accumulated around 300 stars on GitHub and released eight versions between February 4 and April 17. The release notes chart steady progress: initial icon rendering fixes, then major features like "Lock on Close." Mainstream tech outlets—MacRumors, 9to5Mac, The Verge, Ars Technica—haven't published dedicated coverage yet.
That visibility gap might not hold. The tool addresses a real friction point for a specific audience: security-conscious professionals, journalists handling sensitive sources, developers working with proprietary data, IT teams managing devices in environments where trust is a luxury. For enterprise setups, PanicLock's functionality overlaps with what MDM solutions can enforce through configuration profiles—Apple's deployment documentation includes restriction keys for disabling biometric authentication and enforcing Touch ID timeouts—but those require centralized management and buy-in from IT departments. PanicLock puts the control directly in users' hands, no permission required.
The Platform Question
The tool's existence raises a question Apple hasn't answered publicly: Why has iOS had a biometric kill switch for nearly eight years while macOS has not?
The answer probably involves different threat models and usage contexts. iPhones live in pockets, get pulled out at traffic stops, travel through borders. Macs sit on desks, live in backpacks, occupy a different risk profile. But the gap remains, and PanicLock doesn't ask Apple to close it.
It just closes it anyway.
For some users, that may be enough. For others, it's a starting point—a reminder that security tools don't always need to come from the platform vendor. Sometimes they come from someone who noticed a problem, knew how to fix it, and decided to share the solution.
Byrne built what he needed. That it turned out to be useful for others? Perhaps more than he expected, but not surprising. Good tools have a way of finding their audience.
