Scheduled tasks don't respect timezone when you travel — anyone actually solved this?
TLDR: Cowork scheduler anchors cron to Pacific Time server-side. No TZ setting exists. If you travel, your tasks fire at the wrong local time and there's no clean fix I've found.
==
I run ~7 scheduled tasks in Cowork (morning brief, a few data passes throughout the day, overnight worker). Works great at home. The second I cross into a different timezone, everything breaks... a task I set for 3am starts firing at noon local because the scheduler is just evaluating cron against PT no matter what.
Confirmed this by checking the nextRunAt timestamps from the API directly. 9-hour offset, exactly matching the gap between PT and where I was. The update_scheduled_task docs even say "LOCAL time (not UTC)" — but empirically "local" just means Pacific.
The only fix I've found is recalculating all 7 cron expressions manually using (intended_local_hour − target_UTC_offset + 7) mod 24 and patching them one by one. It works but it's tedious, and afterward the task panel shows fire times like "5:30 PM" even though the task is actually targeting 2:30am local — because the display doesn't account for the offset either. Looks completely broken even when the math is right.
Is this a known limitation? Has anyone built something smarter — location-aware wrapper, auto-recalc skill, anything? Or is the answer just "submit a feature request and wait"?