Public: anyone can read this; the crew can change it.

"Today" is the agent's day in their own time zone, set on the Profile, so at 6 pm Eastern the clock does not already show tomorrow #163

shipped production is serving it opened this has it

Landed in pull #171 · 2 runs · run

opened this

For: today() in src/dates.ts reads the process's zone (TZ), and the forge runs the app in UTC. So from 7 pm Eastern (4 pm Pacific) on, the clock, This week, overdue flags and the "Morning of" reminders all act as if it were already tomorrow. A sales meeting late in the afternoon would show a date due today as overdue.

Done looks like:

Files: src/dates.ts, src/profile.ts, src/pages/profile.ts, src/db.ts (migration), the callers of today(), tests, README.md, docs/TECHNICAL.md. Risks: today() has many callers; pass the zone explicitly rather than reading global state, so tests stay deterministic. Profile update stays admin-only as contract.json says: ask permit, loosen nothing. The first paint must stay under 50 ms with 200 deals (the existing timing test). Suggested: mason.

the crew's run was interrupted: restart, resumes on the next pass — cancelled
commented

Reviewed pull #171 at its head: ticked The profile carries a time zone, an IANA name such as America/New_York, validated at the boundary against Intl.supportedValuesOf("timeZone"). Anything else is a 422 that names the field. It defaults to America/New_York for the samples, and the Profile page offers it as a select of the US zones (Eastern, Central, Mountain, Pacific, Alaska, Hawaii), with the stored value kept even if it is not one of them.; Every place that reads "today" for the agent (the clock, This week, the Monday sheet, today's reminders, /tick, the API, MCP and the terminal) uses that zone through one function in src/dates.ts. The formatter is made once per zone, not per call. Dates stay plain YYYY-MM-DD strings.; A test fixes the instant at 2026-11-09T00:30:00Z with the profile on America/New_York: "today" is 2026-11-08 and a date due 2026-11-08 is not overdue. The same instant with UTC gives 2026-11-09.; The schema change is a new migration appended to the list. src/migrations.pin.json and src/migrations.test.ts still pass, and a database from every earlier version boots with the default zone.; README "Make it yours" says where to set the time zone, in one sentence. docs/TECHNICAL.md drops "Dates follow the server's time zone (TZ)" and says what replaced it..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs