pickfit

BrowseOther

BreakTimer

Desktop app that manages and enforces periodic computer breaks.

BreakTimer running, recorded by pickfit on 2 Nov 2026 · 49 s

What it does

  • Set how long and how often breaks are
    How to use it
    1. Open the BreakTimer Settings window and go to the Breaks section.
    2. Change the break length with the slider or number field, for example to <minutes>.
    Watch it at 0:15
    Tested
  • Get reminders as a notification or a fullscreen window
    How to use it
    1. Open the BreakTimer Settings window.
    2. Find the option for how breaks are announced.
    3. Choose Notification for a simple notification, or the fullscreen popup window.
    Watch it at 0:31
    Tested
  • Limit reminders to your working hours
    How to use it
    1. Click the BreakTimer icon in the menu bar and choose Settings.
    2. Go to the Working Hours section.
    3. Use the Enabled toggle at the top to turn Working Hours on or off.
    Tested
  • Change the message shown during breaks
    How to use it
    1. Open the BreakTimer Settings window.
    2. Find the break message text field.
    3. Clear it and type <your text>.
    Watch it at 0:03
    Tested

Use it

Before you install: known vulnerabilities

pickfit found 1 known high or critical vulnerability in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.

  • npm:source-map-js 1.2.1 source-map-js allows event-loop denial of service through indexed source-map section offsets (GHSA-68fv-2mgg-jv7q, high, fixed in 1.2.2)

macOS arm64

  1. Install BreakTimer cask to ~/Applications

    mkdir -p ~/Applications && brew install --cask --appdir=$HOME/Applications breaktimer

Open BreakTimer from Applications; it runs from the menu bar, where you click its icon and choose Settings to open the full Settings window.

How far pickfit got

macOS arm64

  1. Installs
  2. Opens to its setup screen
  3. 4 of 4 features work
  4. Works offline

Linux and Windows: the project says it runs there; pickfit hasn’t tried it.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

macOS arm64

A feature worked when operated

  • Replayed from scratch
  • Checked on 1 Nov 2026
  • Version 2.0.3

When pickfit opened it, its first-run (setup) screen rendered. pickfit then used it, and this worked: Change the message shown during breaks; Set how long and how often breaks are; Get reminders as a notification or a fullscreen window; Limit reminders to your working hours. The launch passed again with the network off.

The clip was cut from these unedited recordings:

Differences the test machine hit

  • README: macOS - BreakTimer.dmg download
    In the test: brew install --cask --appdir=$HOME/Applications breaktimer (sbx cannot write /Applications; same 2.0.3 app, links /opt/homebrew/bin/breaktimer)
  • README: breaktimer disable / breaktimer enable
    In the test: On macOS do not run /opt/homebrew/bin/breaktimer headless (Electron FATAL: Unable to find helper app); start with open ~/Applications/BreakTimer.app and use Settings UI. README CLI disable/enable is Linux-only per FAQ.

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.