I could never stick with work tracking apps because logging my work eventually started feeling like work itself. I spend most of my day in the terminal, so I wanted something that could become part of that workflow instead of pulling me out of it. Crona grew from that frustration.
Overview
Local-first work tracker with terminal UI, scriptable CLI, and background daemon
Local-first work tracking for people who live in the terminal.
From the maintainer
Create an issue with additional context assign it to your day, and start a focus session against it. Work normally, add a few notes as you go, then end the session and see it reflected in your daily timeline and momentum. That’s the core Crona loop.
Crona treats focused work sessions, rather than a task list, as the primary unit of work. Repositories and issues provide context, but the goal is to build a useful history of what you actually worked on. It’s also local-first and keyboard-driven, so the tracker stays out of the way and no data leaves your machine.
The immediate focus is polishing the core TUI and making work tracking feel increasingly effortless. I’m also building companion experiences around Crona, improving insights and reporting, and exploring optional sync while keeping the local-first experience intact.
Latest Release
Crona v1.8.0
Crona v1.8.0 adds daemon-owned day-boundary scheduling and the stepped TUI editor for configuring default and weekday-specific times.
Added
- Start of Day and End of Day schedules with local-time weekday overrides, durable occurrence deduplication, boundary events, and normal EOD alert routing.
- A stepped TUI editor for grouped multi-day overrides, editing and removal, disabled configured days, and all-days-covered safeguards.
- User-timezone-aware day-boundary display and daemon broadcasts while persisted schedule and occurrence timestamps remain UTC where applicable.
Changed
- The local IPC protocol version is now
1.1to identify the client-visible day-boundary scheduling contract. - TUI day-boundary settings now persist through the same daemon settings patch path used by other clients.
Compatibility
- Clients declaring local IPC protocol
1.0should not assume support for the day-boundary scheduling contract. - No storage migration is required; existing schedules are normalized using the existing defaults.
Discussions