Long sessions
Focus timer.
Some work doesn't fit in twenty-five minutes. Reading a codebase, drafting a chapter, debugging something that only reveals itself an hour in — those need a long, uninterrupted block, and the first fifteen minutes of it are just the cost of getting in.
The clock above is set to 90 minutes: one ultradian cycle, the longest stretch most people can hold before attention genuinely needs feeding. Name the work, start it, and don't look at the clock again — the bar tells you where you are without you reading a digit.
Sitting with it
Built to be stared at for an hour.
01
Dark, and dim where it matters
Near-black background, one bright element per clock. At full laptop brightness in a dark room there's nothing to squint past, and the time still reads from three metres away.
02
Progress you read, not watch
A row of marks, one per minute, going out as you go. Full height means running, half height means paused, a flat rail means idle — readable across a room, and slow enough that it never pulls your eye mid-sentence.
03
The end time is printed
Under each clock is the wall-clock moment that session ends. That's the same absolute timestamp the worker counts against — the timer isn't estimating, it's reading.
FAQ
Questions.
How long should a focus session be?
Long enough to get past the warm-up, short enough that you don't end it exhausted. 45, 50 and 90 minutes are the common answers; 90 is the ceiling for most people.
Will it drift over 90 minutes?
No. The worker compares against a fixed end timestamp rather than adding up intervals, so a throttled or sleeping tab can't lose seconds. Whatever the browser does, the end time doesn't move.
Can I run more than one long session?
Up to four clocks at once, each with its own colour and its own end time. One sits large at the front and the rest wait in a strip below; spacebar controls the one at the front, and 1 to 4 promotes another.
Working in shorter sprints instead? Try the Pomodoro timer, or head back to the deep work timer.