CLI tool
SelfControlApp/selfcontrol avatar
SelfControlApp/selfcontrol

SelfControl blocks your own Mac for a fixed window, and the repo contains the tools that undo it

:skull: Mac app to block your own access to distracting websites etc for a predetermined period of time. It can not be undone by the app or by a restart – you must wait for the timer to run out.

4,422 stars474 forksObjective-CGPL-3.0

At a glance

What is it?
SelfControlApp/selfcontrol is a macOS app that locks the user out of chosen sites until a timer expires. The interesting part for an engineer reading the repository is that the tree ships a killer app, a helper and a CLI alongside the blocking logic.
Who is it for?
Adopt SelfControl if you are one person on one Mac and you want a wall that survives a restart, and you accept that the same repository contains the code that removes it, namely SelfControl Killer and SCKillerHelper. Do not adopt it as a household or employer filter, because the README does not document the daemon's launchd plist or the kill switch's permissions.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 142 days ago.
What is it written in?
Mainly Objective-C, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • SelfControlApp/selfcontrol4,422 ★ · +21
Star history
Repository2026-09-232026-11-15
SelfControlApp/selfcontrol4.4k4.4k

21 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The product is a timer, a blocklist and one button

SelfControl solves a narrow problem: a person who keeps opening the same distracting sites during work hours and cannot stop by deciding not to. The app's own description says it blocks your own access to distracting websites and mail servers for a predetermined period, and that the block "can not be undone by the app or by a restart". The README makes the same promise: until the timer expires you cannot reach those sites, even if you restart the computer or delete the application.

That promise is the entire product. There is no account, no server, no sync. The audience is one person on one Mac, and the reader is deciding whether their own self-discipline can be outsourced to a timer. The desktop layout backs this up. AppController.m and TimerWindowController.m sit at the top level, DomainListWindowController.m owns the list of hosts, and SCConstants.m holds the shared values. PreferencesGeneralViewController.m and PreferencesAdvancedViewController.m split settings into a simple and an advanced pane, which is what a single-user tool looks like when it wants to stay out of the way.

A privileged Daemon sits between the app and the network

The repository is not a plain Cocoa application. Daemon/ sits beside SelfControl.xcodeproj/ in the top-level listing, and LaunchctlHelper.h and LaunchctlHelper.m are the seam between the user interface and that background component.

The reason for that split is visible in the file names around the block list. Block Management/ and Common/ sit beside them in the tree. NSString+IPAddress.h sits in the tree alongside that machinery, consistent with a block that is expressed in network terms rather than as a browser preference.

This matters for anyone evaluating the project. A preference pane in Preferences writes a file; a launchd helper writes a system-level state. The README does not describe the daemon's install path, its launchd plist, or how a user inspects the running state after the app has quit, so the parts of the architecture an adopter most needs to see are the parts the documentation leaves out.

Building from source needs CocoaPods and the workspace, not the project

The README tells users to download the latest version from the project's website and reserves the build steps for contributors, which means there is no command-line installer in the repository. Everything below is the contributor path, and it only runs on a Mac with a recent Xcode and the Xcode command-line tools.

Install CocoaPods first, the way the README spells it:

bash
sudo gem install cocoapods

Then run the dependency install from the cloned repository root:

bash
pod install

The Podfile at the top level is what pod install reads, and Sparkle.framework/ in the same directory is the update framework the project ships. Here is the step a skim misses. The README says to open selfcontrol.xcworkspace, with NOT set against selfcontrol.xcodeproj, because pod install generates the workspace and the Pods dependencies are only linked through it. The final README step warns that you may need to update or remove code signing settings.

The repository ships the code that removes its own block

Here is the contradiction worth sitting with. The description claims the block "can not be undone by the app or by a restart", yet the top-level file listing includes SelfControl Killer/ and SCKillerHelper/, whose names point at ending a block, alongside a command-line entry point, cli-main.m. There is also cheater-background.png, an image whose name says what it is for.

The design reason is defensible. Any blocker that cannot be stopped at all is a trapdoor into data loss, so the guarantee is really a claim about a specific enemy: the person who is tempted at 4pm and has no technical patience, not the person who opens a terminal. The README does not say this in so many words, and it does not document the kill switch, its permissions, or whether it prompts. For an engineer reading the tree, the honest summary is that SelfControl resists impulse, not an owner.

WhitelistScraper.h sits in the same listing.

Twelve languages are claimed, one localized bundle is visible

The README states that SelfControl is available in 12 languages and links to a wiki page for the translator credits. The top-level listing, however, shows Localizable.strings (Chinese).strings alongside DomainList.strings, MainMenu.strings and SCError.strings.

That gap is small but it is the kind of thing that matters when you decide whether to file an issue in your own language. The strings files present at the root are the ones a translator touches first: the domain list window, the main menu, the error messages the daemon returns. A block that refuses to start and reports the reason through SCError.strings is the moment where a missing translation costs you the only clue about what went wrong.

There is no localization guide in the repository listing and no documented workflow for adding a language, so a contributor who wants to add one starts from those .strings files with no stated instructions.

Compared with a DNS filter, SelfControl owns the wrong end of the problem

The usual alternative to a self-imposed Mac blocker is a DNS or hosts-file filter, the kind shipped as a profile by a family or an employer and enforced at the network layer. The difference in approach is not quality, it is scope. A network filter is administered from outside, applies to every browser and every app on the machine, and can be changed by whoever controls the network. SelfControl is administered from inside, by the user, from a Cocoa interface, and its persistence comes from a launchd helper rather than from the network.

There is also a timing difference that matters. DNS filtering works only while the block configuration is active, and the same reversibility problem appears there. SelfControl's differentiator is its promise that the state survives a restart of the computer, which is why the daemon and LaunchctlHelper exist at all.

Set against that, SelfControl gives up coverage. It blocks what you list, in the apps and protocols its own block mechanism handles.

The website is the distribution channel, the source tree is not

The last push to the repository was on 2026-06-26, and the repository is not archived. A .github/ directory and SelfControlTests/ sit in the tree, which is more than a hobby script would leave behind.

Even so, the README opens by telling users to download the latest version from selfcontrolapp.com rather than from the source. Contributors get four steps and a workspace; everyone else downloads the app from the website. Nothing in the documented path produces a distributable build, and the CocoaPods and workspace steps mean you cannot build on anything but a Mac. Licensing follows the same split: the code is free software under the GPL, with COPYING at the root, so redistribution obligations attach to a modified build rather than to your own use.

Editorial conclusion

Adopt SelfControl if you are one person on one Mac and you want a wall that survives a restart, and you accept that the same repository contains the code that removes it, namely SelfControl Killer and SCKillerHelper. Do not adopt it as a household or employer filter, because the README does not document the daemon's launchd plist or the kill switch's permissions. Before installing, read SCKillerHelper and SelfControl Killer to see exactly what a motivated person on the same login can do, then decide whether that balance still suits you.

Frequently asked questions

Is SelfControl safe to install on my Mac?

It is GPL-3.0 free software built from Objective-C sources with a CocoaPods dependency set, and the README states that a block continues even if you restart the computer or delete the application. Note that the repository ships a killer app and helper that exist to end a block early.

How do I use the SelfControl app?

Set a period of time to block for, add sites to your blocklist, and click Start Block. Until that timer expires you cannot reach those sites. Contributions require building from the source tree on a Mac with a recent Xcode.

Does SelfControl have a command line interface?

The repository includes a cli-main.m file at the top level, alongside ArgumentParser, so a command line entry point exists in the source. The README does not document how to build or invoke it.

Can the SelfControl block be stopped before the timer ends?

The project description states the block cannot be undone by the app or by a restart, and you must wait for the timer to run out. The source tree nevertheless contains SelfControl Killer and SCKillerHelper, and the README does not explain when or how those are meant to be used.

What does it take to build SelfControl for development?

Clone the repository, install a recent Xcode with its command line tools, install CocoaPods with sudo gem install cocoapods, then run pod install. Open selfcontrol.xcworkspace rather than selfcontrol.xcodeproj, and expect to adjust code signing settings.

Official sources

  1. Issues
  2. License: GPL-3.0
  3. Project website
  4. README
  5. SelfControlApp/selfcontrol on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/selfcontrolapp-selfcontrol.svg)](https://hysenlabs.com/projects/selfcontrolapp-selfcontrol)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/selfcontrolapp-selfcontrol.svg)](https://hysenlabs.com/projects/selfcontrolapp-selfcontrol)

Was this useful?