Getting time zones right when Claude sets your calls

There is one detail that quietly decides whether your reminder call arrives at the right moment: the time zone. Get it wrong and an 8am wake-up can ring at 3am. ReminderIt uses IANA time zones precisely so this stays unambiguous, and Claude is built to confirm the zone before it schedules anything.

Why IANA zones, not just an offset

ReminderIt stores times against named IANA zones such as America/New_York, Europe/London or Asia/Kolkata, rather than a fixed offset like UTC+1. A named zone carries its own rules for daylight saving, so 8am stays 8am across the year without you touching anything.

If reminders were pinned to a raw offset, every spring and autumn clock change would drag your calls an hour out of place. The named zone is what keeps a morning call feeling like the morning.

America/New_York versus Europe/London in practice

Imagine you set "call me at 9am" but never say where. Nine in the morning in New York is two in the afternoon in London. That five-hour gap is exactly why Claude asks. Saying "9am America/New_York" or "9am Europe/London" leaves no room for the wrong interpretation.

The two cities also change their clocks on different dates, so for a couple of weeks each year the gap between them is four hours rather than five. Named zones absorb that automatically; you never have to track it.

Travel: your reminders do not follow your feet

A reminder set for Europe/London keeps ringing on London time even while you are in Tokyo. That is usually what a home routine needs, so your evening pill call still matches your household back home.

If instead you want a call to track where you are on a trip, tell Claude to update the reminder's zone: "Change my morning call to Asia/Tokyo for this week." It will use update_reminder to set the new zone, and you can switch it back afterwards.

Daylight saving, handled for you

Because the zone name encodes DST rules, you do not need to nudge your reminders when the clocks go forward or back. An 8am call in Europe/London is 8am in both winter and summer, even though the underlying UTC offset shifts by an hour.

This is one less thing to remember twice a year, and it is the main reason a plain offset is never a good substitute for a proper zone.

How to confirm the zone with Claude

Make the zone part of the request from the start: "Set a daily 8am reminder to take my tablets, Europe/London." Claude will echo the zone back before creating the call, which is your moment to catch a mistake.

Not sure which account default is in play? Ask "what time zone are my reminders using?" Claude can check with whoami and list_reminders, then confirm or change it. A ten-second check now saves a call at the wrong hour later.