Repository navigation
feat(task_step): wake and delivered lines are labelled in the task's time zone - #723
Merged
earakely-scale merged 3 commits intoNov 16, 2026
Merged
Conversation
…time zone
always_on, prompt_agent's delivered lines and the advance-to-next-event hook labelled every line in UTC, so a person
in Denver whose first message came at 5:30 PM on Friday reached the agent as "Sat Feb 6, 12:30 AM UTC", while the
computer's screen showed Friday evening. Lines now read in the task's zone and name it ("Fri Feb 5, 5:30 PM MST"):
the user sim's zone, else the one sync_env_clock gave the world, else UTC, as before.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e's summary the run's own zone Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
earakely-scale
deleted the
edgararakelyan/wake-lines-in-the-tasks-zone
branch
November 16, 2026 23:45
Collaborator
Author
|
For the docs site: wherever the docs show what an agent receives between turns (always_on, prompt_agent's notifications/v1 delivery, the advance-to-next-event hook), the time labels now read in the task's time zone and name it, for example |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of FD-5419.
Why
The lines an agent receives between turns were always labelled in UTC: the user's messages in
always_on, what came due onnotifications/v1, and the hook's scheduled person messages. In the weekend-away task (HB1.12, runagent-jr2tl2un), Nora lives in Denver.[Sat Feb 6, 12:30 AM UTC] Nora: …, although for her it was Friday at 5:30 PM, and the computer's screen, set to Denver, showed Friday evening.UTC was chosen to match
get_timeandschedule_check.get_timenow answers in the universe's zone too (#702), andschedule_checktakes any offset, so a zone that names itself is just as unambiguous.What changes
label_time(at, zone="UTC")labels in an IANA zone and names it:Fri Feb 5, 5:30 PM MSTin standard time,MDTin daylight time. A zone with no abbreviation is named by its offset (UTC-03). With the default, the output is the same as before.always_onpasses its task zone (self.zone): the user sim's zone, else the onesync_env_clockgave the world.prompt_agentpasses its user sim's zone when it has a built-in one, else the one zonesync_env_clockgave the world (labels_zone). Each env's latest arm counts, so a re-arm in another zone wins, and a rate change (set_env_clock_rate) keeps the zone. Several zones, or none, means UTC.advance-to-next-eventhook labels the person's messages in the zone the env clock was armed in, so they agree with whatprompt_agentdelivers beside them.render_for_judge) reads the zone the run's record keeps, which survives a timeline cut to its tail.A task with no zone reads exactly as before, and that includes both integration tests.
Tests
prompt_agentlabelling in the zonesync_env_clockset, and in UTC without one;always_onunit tests' expected labels, whose test user lives in New York, and two opening-files tests, whose user lives in Los Angeles. The labels were converted by script from the same instants.tst/unit/task_steppasses: 3213 tests.🤖 Generated with Claude Code


Confidence Score: 5/5
The PR appears safe to merge, with no outstanding findings.Summary
Labels wake times and delivered messages in the task's time zone, with UTC as the fallback.
Reviews (5) · Last reviewed commit: "fix(task_step): a clock rate change keep..." · Reviewed by Greptile