Clockee: a world clock in the corner of my screen

A native macOS world clock I built with Claude Code: a small card in the screen corner with my time and date, my next meeting in the client's time, and my 5 places in time order. It gets out of the way when the pointer comes near. 14 MB of memory.

The Clockee app icon: a white clock face with hour marks and a red edelweiss in the centre, on a red gradient square, with the name Clockee under it

18 Nov 2026 Clockee is the world clock on my Mac. It's a small card in the bottom-left corner of my main display, above every window, on every Space. It shows my own time and date in large type, and my next meeting with the client's local time. A click opens the time in the 5 places I work with: the West Coast, the East Coast, the UK, Israel and India, in time order, with a red line where I am.

When the pointer comes near, the card disappears and lets my clicks through to the window behind it. Only a thin bar with 3 controls stays.

Clockee replaces no app. The macOS menu bar clock stays where it is. I built Clockee with Claude Code: version 1.0 shipped on 28th October 2026. The app is 1 MB on disk and uses 14 MB of memory. The name follows the -ee family of my tools.

The screenshots in this note come from QA, with a fake clock, a fake meeting and 4 of the places.

The Clockee card in dark mode with its places open, in time order: West Coast 04:00 minus 8 h and Toronto East 07:00 minus 5 h in grey because they are outside working hours, UK 11:00 minus 1 h in white, a red line, Israel 13:00 plus 1 h, and at the bottom the local time 12:00 in large type with a red bar and the date Wed 28th

Why I built it

My week runs on 5 time zones. Before every call I did the same sum in my head: what time is it for them, are they still at work, is it a holiday there. The menu bar clock shows 1 time zone. A desktop widget sits under my windows, and I never see my desktop.

I wanted 3 things in 1 glance, without a click:

  • My time, large enough to read from across the desk.
  • My next meeting, with a countdown and the time for the client.
  • Who is at work: working hours, their own weekend, their public holidays.

Before the build, the agent reviewed 90 days of my calendar history, my displays and my window manager. 1 round of 29 questions set the design.

What Clockee does

The card

The card sits flush in the corner of my main display. Top to bottom:

Row Shows When
Next meeting Start time, subject, "in 25 min", and the client's local time A meeting in the next 12 h
Countdown Time left until a deadline another tool writes A countdown file is set
Places Label, time, offset from me ("−5 h", "+4½ h"), and the weekday if it differs After a click on the card
My time Large, no label, a red bar on the left and the date ("Wed 28th") on the right Always

30 Oct 2026 The places are now hidden until I click the card, and a 2nd click hides them again. The closed card is smaller, which matters more than a click saved. A click never takes the focus from the app I work in.

16 Nov 2026 The card moved to the bottom-left corner (a corner setting keeps bottom-right as an option). The grey weekday became the date in white, at 2x the small text: "Mon 16th". I left out the month so the card stays narrow.

Places in time order

18 Nov 2026 The places sort by their offset from me, the furthest behind at the top. A red line sits between the places behind me and the places ahead of me, so I see where I am in the day of the world. The order follows daylight saving by itself, whatever the order in the settings file.

The offsets are easier to read: larger, right-aligned in 1 column, with a true minus sign (−) and fractions for India's half hour ("+4½ h", not "+4:30 h", which looked like a time). When a place is already on another day, its weekday follows the offset.

Gone when the pointer comes near

15 Nov 2026 A card above every window sometimes covers the button I want. Now, when the pointer comes near, the card disappears and lets clicks through to the window behind it. A thin bar stays at its bottom edge with 3 controls:

The Clockee control bar in dark mode: a thin black bar with 3 grey controls, SHOW, PLACES and HIDE 1 MIN, separated by thin lines

  • Show brings the card back until the pointer leaves.
  • Places brings the card back with the places open.
  • Hide 1 min hides the card and the bar for 1 minute, for a longer look at what's behind.

The bar never takes the focus either. Version 1.0 let clicks through all the time; the 2nd November version faded the card to 15% and kept the clicks. The bar gives me both: the window behind is clickable, and the clock is 1 click away.

The closed Clockee card in dark mode: a fake meeting Acme quarterly business at 14:00, in 1 h, 13:00 UK, above the local time 13:00 in large type with a red bar and the date Wed 28th

Working hours and holidays

Each place has its own working days, start and end times, and holiday calendars. A place outside working hours turns grey. A place on a public holiday gets a red dot after its label.

Code Holidays
uk England and Wales bank holidays, with substitute days
us 9 federal holidays and the day after Thanksgiving
ca-on Ontario statutory holidays, with substitute days
il Rosh Hashanah to Shavuot, from Foundation's Hebrew calendar

The holidays come from rules in code, for any year, offline. No data file to go stale, no network. Israel's weekend is Friday and Saturday, so its work week starts on Sunday. A place with 2 calendars, like the East Coast with Ontario and the US, stays at work when only 1 of them has a holiday and gets the red dot.

The client's local time

Clockee reads my next meeting from a local calendar database that another tool syncs every hour. It skips declined, cancelled, all-day and focus blocks, and events I'm alone in.

For each external email domain in the meeting, Clockee guesses the client's country: the top-level domain first (.uk, .il, .ca), then my company database. It then shows the first time zone that differs from mine, for example "13:00 UK". The countdown turns red 5 minutes before the start.

The countdown

1 row counts down to any deadline that another tool writes to a JSON file. I use it for my work sign-in session: a script keeps the session alive and writes its expiry, and the row turns red in the last hour and says "sign in" when the session has ended. Clockee only reads the file, so it stays generic.

The 1-line strip

The first design was a 1-line strip along the bottom of the screen. I switched to the card on day 1, but the strip stays as an option. It has the same time order, with a red separator where I am:

The horizontal Clockee strip in dark mode: the local time 00:30 Thu 29th, then West Coast 16:30 minus 8 h WED, Toronto East 19:30 minus 5 h WED, UK 23:30 minus 1 h WED, a red separator, and Israel 01:30 plus 1 h

All features

  • Corner card. A small card flush in the bottom-left (or bottom-right) corner of 1 display, above every window, on every Space, never in ⌘Tab.
  • My time and date. Large type with a red bar and the date in white, "Wed 28th".
  • Places on a click. A click opens the time in each place. A 2nd click closes them. The card never takes the focus.
  • Time order. The places sort by offset, the furthest behind at the top, with a red line where I am. Daylight saving changes the order by itself.
  • Clear offsets. Right-aligned, a true minus, "+4½ h" for half hours, and the weekday when a place is on another day.
  • Gone near the pointer. Near the pointer, the card disappears and clicks go to the window behind it. A thin bar keeps Show, Places and Hide 1 min.
  • Working hours. Each place has its own working days and hours. A place outside them turns grey.
  • Public holidays. Rules in code for the UK, the US, Ontario and Israel, offline, for any year. A red dot marks a holiday.
  • Next meeting. Start time, subject, a countdown and the client's local time, guessed from the email domains. Red 5 minutes before.
  • Countdown row. Time left until a deadline that another tool writes to a JSON file.
  • Card or strip. A vertical card or a 1-line strip along the screen edge.
  • Look and type. Light, dark or follow macOS. Any installed font, Futura by default, with a size setting.
  • Settings file. 1 JSON file with comments, reloaded live. Places can be added, removed and renamed. The corner, the size, the font and the fade are settings too.
  • Light on resources. 14 MB of memory, 0.11% CPU at rest, no Dock icon, no permissions. A login agent restarts it after a crash.
  • Agent CLI. clockee status, at, next, holidays, places, hide and show, plus commands for places and looks, all with --json. clockee at 16:00 converts a time across every place.

Speed and footprint

Clockee has no old app to beat, so the spec set budgets and QA fails when one breaks:

Bar chart, Clockee against its own budgets, best value per row in bold. Footprint. Memory (footprint): Clockee 13.6 MB (best), Budget 30 MB; CPU, average at rest: Clockee 0.11% (best), Budget 0.2%. Speed. Launch to card drawn: Clockee 221 ms (best), Budget 300 ms; 1 redraw: Clockee 0.04 ms (best), Budget 2 ms.

The app I ran overnight used 31.8 s of CPU time in 7 h 43 min. That's 0.11% on average, with a memory footprint of 14 MB.

The rules that keep it there are in the spec:

  1. 1 timer, re-armed on each minute boundary from the wall clock. No repeating timer that drifts.
  2. Redraw on events only: the minute tick, wake, a clock change, a time zone change, a new day, a display change, a settings change, a new meeting.
  3. The main thread never touches the disk. Settings, state and the calendar load on a background queue.
  4. The calendar is read at most once a minute, with a 200 ms busy timeout. A locked file keeps the last meeting and never blocks.
  5. The panel never becomes key and never activates the app.

Correct beats fast. A clock that is 1 hour wrong once is worse than no clock, so QA checks the offsets and weekdays across the daylight saving weeks, and Clockee redraws within 1 s of a wake.

How it's built

  • Swift 6.3 and AppKit, 1 view drawn by hand. No SwiftUI.
  • 1 borderless, non-activating NSPanel at status-bar level: above normal and floating windows, below menus and Alfred. It joins every Space and stays out of ⌘Tab and Mission Control.
  • Foundation TimeZone for the time zones, so daylight saving is automatic.
  • Futura for a Bauhaus look, with Lato as the fallback. Any installed font works.
  • No Dock icon, no menu bar icon, no permissions. A bundled login agent restarts it after a crash, in about 3 s.
  • Settings in 1 JSON file with comments, reloaded live.
  • No dependencies.

Gotchas worth knowing

The agent interface

Every command takes --json, so NicAI can use Clockee inside a task (see What is NicAI). The calendar skill can use clockee at to propose times across my places:

clockee status --json                    # each place's time, offset and status
clockee at 16:00 --json                  # 16:00 here, in every place
clockee at 09:00 --from Toronto --json   # 09:00 in Toronto, here and everywhere
clockee next --json                      # the meeting on the card, with the client's time
clockee places toggle --json             # open or close the places
clockee hide 30 --json                   # hide the card for 30 minutes
clockee add Asia/Kolkata --label IST --json  # add a place

clockee status works when the app isn't running: it computes the times from the settings with Python's zoneinfo.

How it was built

Clockee followed my appee process for apps:

  1. Usage review: 90 days of calendar history, the displays, the window manager and the other apps.
  2. Questions: 29, each with a recommended answer, answered on 28th October 2026.
  3. Spec, build and QA: version 1.0 the same day. An independent review found 13 defects, all fixed. 2 examples: deleted calendar events showed as meetings, and clockee at used today's offset, so other dates were 1 hour off across daylight saving.
  4. Changes from use: on day 1, the vertical card and Futura. On 29th October, the countdown. On 30th October, the places behind a click. On 15th November, the card that disappears near the pointer, with its control bar. On 16th November, the bottom-left corner and the date. On 18th November, India, the time order, the red line and clearer offsets.

Each change from use took 1 short request in the same Claude Code session, and shipped the same day with its QA checks.

QA today: 20 unit tests and 125 end-to-end checks in 5 suites. QA runs the real app with a fake clock, fake displays and a fixture calendar, and renders the card off screen. It never touches my real screen, calendar or pointer.

Next

Version 2 candidates: shift the times by scrolling over the card, a daylight saving alert, the time for the person on a call, and a Stream Deck key with the times.

Further reading

The tool I built it with:

Apple's window class behind the card:

The project generator the build uses:

NicAI
Written by NicAI, Nic's AI assistant, for his personal knowledge base. Researched and drafted by the model, not hand-written by Nic. Verify anything you plan to act on.