The Problem
Editing a crontab is five fields of whitespace-sensitive guesswork, with no validation, no preview, and no undo. And the moment you open a Windows machine, the entire mental model is replaced by Task Scheduler.
Most tools pick one platform and approximate the other. Approximation is how scheduled jobs silently stop running.
The Insight
Honesty beats approximation: implement each platform’s exact semantics — and refuse what can’t be represented.
The Instrument
crontui wraps real schedulers in a Bubble Tea interface with full CLI parity: live validation as you type, next-run previews before you save, stable job IDs, and an automatic backup before every single write.
Unix and WSL manage your real crontab; native Windows manages its own tasks under \CronTUI\ in Task Scheduler. Expressions Windows can’t represent — @reboot, */7 — fail loudly instead of being silently approximated.
Validated before it saves
$ crontui preview "0 9 * * 1-5" 3
Next 3 runs for: 0 9 * * 1-5
1. Mon Oct 26 09:00:00 2026 (in 3 days (Mon 09:00))
2. Tue Oct 27 09:00:00 2026 (in 4 days (Tue 09:00))
3. Wed Oct 28 09:00:00 2026 (in 5 days (Wed 09:00))
$ crontui add "0 9 * * 1-5" "./backup.sh" --desc "weekday backup"
Added job #4: 0 9 * * 1-5 ./backup.sh
$ crontui add "@reboot" "./startup.sh"
Unsupported schedule on this platform: windows backend does not support
@reboot without elevated Task Scheduler permissions
Representative session, captured Fri 23 Oct 2026 — every mutating write creates a backup first; the last command runs on native Windows.
Spec
- Platforms
- Linux · macOS · WSL2 cron · native Windows Task Scheduler
- Interface
- Bubble Tea TUI + every operation as a CLI subcommand
- Safety
- Backup before every write — including before restores
- Config
- ~/.config/crontui/config.json · CRONTUI_* env overrides
- Install
- go install · release binaries
- Quick start
go install github.com/meru143/crontui@latest
The Outcome
crontui v1.2.2 shipped on 19 March 2026 with binaries for Linux, macOS and Windows. Built so scheduling is something you can see: validated expressions, previewed runs, recoverable mistakes — on both sides of the Unix/Windows divide.