Closed
Conversation
WhatsApp provides message timestamps in UTC. When scheduling one-time tasks, Claude (Opus 4.5) often fails to convert to local time first, opting instead to just drop the Z suffix. Timestamps without “Z” are interpreted in the local timezone, leading to an incorrect offset. It’s more reliable to request a UTC timestamp, and convert to local when needed for Cron.
chidev
added a commit
to lev-os/nanoclaw
that referenced
this pull request
Feb 3, 2026
Enforces Z suffix on once-type schedule values to prevent timezone confusion. Updates tool descriptions and validation in both the agent-runner and main router. Cherry-picked from upstream PR qwibitai#21.
This was referenced Feb 3, 2026
chidev
added a commit
to lev-os/nanoclaw
that referenced
this pull request
Feb 3, 2026
Enforces Z suffix on once-type schedule values to prevent timezone confusion. Updates tool descriptions and validation in both the agent-runner and main router. Cherry-picked from upstream PR qwibitai#21.
|
Reviewed and tested on our fork. LGTM ✅ The Tested with Apple Container on macOS. Clean compile, no regressions. |
chidev
added a commit
to lev-os/nanoclaw
that referenced
this pull request
Feb 3, 2026
Enforces Z suffix on once-type schedule values to prevent timezone confusion. Updates tool descriptions and validation in both the agent-runner and main router. Cherry-picked from upstream PR qwibitai#21.
Collaborator
|
Changes needed:
|
Collaborator
|
This PR targets |
Collaborator
|
Closing due to no response to the rebase request from 7+ days ago. The contribution is appreciated — if you'd like to pick this up again, feel free to reopen with an updated branch against current main. Thanks! |
3 tasks
squarewings
pushed a commit
to squarewings/nanoclaw
that referenced
this pull request
Mar 15, 2026
…se-mode fix: sendMessage test expectations for parse_mode
om10001
pushed a commit
to om10001/nanoclaw
that referenced
this pull request
Mar 19, 2026
…se-mode fix: sendMessage test expectations for parse_mode
hamiz-ahmed
pushed a commit
to hamiz-ahmed/nanoclaw
that referenced
this pull request
Mar 24, 2026
…se-mode fix: sendMessage test expectations for parse_mode
SungWoon
pushed a commit
to SungWoon/nanoclaw
that referenced
this pull request
Mar 27, 2026
…se-mode fix: sendMessage test expectations for parse_mode
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
3 participants
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.
WhatsApp provides message timestamps in UTC.
When scheduling one-time tasks, Claude (Opus 4.5) often fails to convert to local time first, opting instead to just drop the Z suffix.
Timestamps without “Z” are interpreted in the local timezone, leading to an incorrect offset.
It’s more reliable to request a UTC timestamp, and convert to local when needed for Cron.