fix(tools): require timezone on time tools, inject user timezone into the prompt by WSHAPER · Pull Request #257 · nextcloud/context_agent

WSHAPER · 2026-10-07T09:46:16Z

Fixes #3
Fixes #231

timezone is now a required, pytz-validated parameter on schedule_event / add_task / update_task and the scheduled-task tools; a missing or invalid IANA name returns an actionable error to the model instead of silently resolving the time in server/UTC. The system prompt now carries the requesting user's actual timezone (OCS /cloud/user) plus the current time in that tz.

The find_details_of_current_user instruction stays as a fallback for profiles without a timezone. freebusy_finder's naive utcnow() became tz-aware UTC.

For #231, schedule_event now builds the event with icalendar instead of the ics library (which serializes any aware datetime to UTC): DTSTART/DTEND keep the supplied timezone as DTSTART;TZID=…. The organizer's mailto tolerates profiles without an email, as before.

Heads-up: tool callers (incl. MCP) that omitted timezone previously got a silently mis-timezoned event; they now get an explicit error, which should be the canonical behavior, in my opinion.

Verified on stable35 / context_agent 2.9.1, user tz America/New_York on a CEST server: "tomorrow at noon" stores as 12:00 America/New_York (DTSTART:...T160000Z).

WSHAPER · 2026-10-12T14:49:42Z

round 3 @kyteinsky

all-day events now emit DTSTART;VALUE=DATE with dtend on the following day, the assistant chat on my instance ran and read the event back over caldav: DTSTART;VALUE=DATE:20261013 / DTEND;VALUE=DATE:20261014
let GLM 5.3 add a payload test pinning both the all-day and timed shapes, no server needed, if you'd rather keep tests out of this PR I'll drop it
timezone is back at the end of update_task, docstring order matches the args again
prompt is date-only now, tz stated next to the date, time moved to a small get_current_datetime tool (picks up the default-on seeding on re-enable, so no admin step)
the /cloud/user lookup is cached per user with timed_memoize(300), profile changes still propagate within 5 min

kyteinsky

the changes look good, thanks!
a few nits below but all good otherwise.
opened an issue for the flaky tests here: #269

WSHAPER · 2026-10-14T12:12:39Z

@kyteinsky Thanks again for the review!

FYI: I've opened another can of worms that surfaced after inspecting what would be optimal for conversation branching:

In light of that, we'd need to discuss how we'd like to proceed.
To avoid scope creep, I'd like to defer the nitpicks for now.

…server's Time-related tools treated the timezone parameter as optional and silently dropped it when the model omitted it, so "tomorrow at noon" resolved against server-local or UTC time. The system prompt tried to compensate by asking the model to discover the user's timezone through a find_details_of_current_user tool call first — that costs an extra agent round trip and still leaves the tools unvalidated, so any model that skipped the discovery step produced events at the wrong wall-clock time. Making the timezone a required, pytz-validated parameter on every tool that interprets a date moves the failure to the tool boundary, where a missing or invalid IANA name returns an actionable error to the model instead of silently scheduling six hours off. Injecting the requesting user's actual timezone (OCS /cloud/user) into the system prompt gives the model the correct value up front, keeping the tool-based lookup only as a fallback for profiles without a timezone set. Naive datetime.utcnow() in the free-slot search was replaced with timezone-aware UTC because mixing naive and aware comparisons produced wrong free/busy windows at DST boundaries. Verified end to end against a CEST server with the user's timezone set to America/New_York: the system prompt logs the current time in NY and "tomorrow at noon" is stored as DTSTART:20261007T160000Z (12:00 EDT). Assisted-by: opencode:zai/glm-5.3 Signed-off-by: WSHAPER <42714629+WSHAPER@users.noreply.github.com>

…g to UTC schedule_event built VEVENTs with the ics library, which serializes any aware datetime to UTC. The stored event kept the right instant but lost the timezone it was created in: edits across DST boundaries and anyone reading the raw ICS lost the anchor (issue nextcloud#231, same class as nextcloud#3 — correct data, wrong localization contract). Building the event with icalendar, already a dependency, keeps DTSTART/DTEND as DTSTART;TZID=… exactly as supplied. The organizer's email is optional in the user profile, so the mailto value must tolerate None the way the previous Organizer constructor did. Verified end to end: 'tomorrow at noon' from an America/New_York profile on a CEST server stores as DTSTART;TZID=America/New_York:…T120000. Assisted-by: opencode:zai/glm-5.3 Signed-off-by: WSHAPER <42714629+WSHAPER@users.noreply.github.com>

…f requiring it Signed-off-by: WSHAPER <42714629+WSHAPER@users.noreply.github.com>

…pper-level tz check Review round 2: the tz helpers move to all_tools/lib/tz.py (get_timezone, user_timezone, starts_at_timestamp) so calendar and assignments share one implementation, with type hints. Optional parameters carry explicit None defaults everywhere the agent can omit them. The async wrappers for schedule_event/add_task/update_task called the validation on the raw parameter, before the profile-timezone fallback in the sync bodies, so an omitted timezone errored even when the profile had one; the wrappers now only delegate. The scheduled-task starts_at docstring drops the stale find_details_of_current_user hint since the timezone defaults to the profile. Assisted-by: opencode:zai/glm-5.3 Signed-off-by: WSHAPER <42714629+WSHAPER@users.noreply.github.com>

Assisted-by: opencode:zai/glm-5.3 Signed-off-by: WSHAPER <42714629+WSHAPER@users.noreply.github.com>

Signed-off-by: WSHAPER <42714629+WSHAPER@users.noreply.github.com>

Assisted-by: opencode:zai/glm-5.3 Signed-off-by: WSHAPER <42714629+WSHAPER@users.noreply.github.com>

Signed-off-by: WSHAPER <42714629+WSHAPER@users.noreply.github.com>

Assisted-by: opencode:zai/glm-5.3 Signed-off-by: WSHAPER <42714629+WSHAPER@users.noreply.github.com>

Signed-off-by: WSHAPER <42714629+WSHAPER@users.noreply.github.com>

WSHAPER · 2026-10-19T12:17:59Z

rebased onto impulse-radius; tz semantics unchanged, tools ride the impulse classification now, payload tests still green.

Follow-up to nextcloud#257: - update_scheduled_task sent the profile timezone on every update, silently moving tasks stored in another timezone, and failed for users without a profile timezone. It now only sends a timezone when one is given explicitly. - create_scheduled_task failed for users without a profile timezone even when no starts_at was given. A timezone is now only required to interpret a starts_at without UTC offset. - update_task resolved the timezone inside a bare except, so an invalid or missing timezone was swallowed and reported as "task not found". It is now resolved before the loop. - The starts_at docs no longer show a UTC example, which made the model send local times with a Z suffix. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Signed-off-by: Marcel Klehr <mklehr@gmx.net>

github-actions · 2026-10-22T06:14:30Z

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)

WSHAPER requested a review from kyteinsky October 7, 2026 10:49

WSHAPER force-pushed the fix/timezone-handling branch from 45f2db4 to 5b0730a Compare October 7, 2026 10:55

kyteinsky reviewed Oct 7, 2026

View reviewed changes

Comment thread ex_app/lib/all_tools/assignments.py Resolved

kyteinsky reviewed Oct 7, 2026

View reviewed changes

Comment thread ex_app/lib/agent.py Resolved

kyteinsky reviewed Oct 7, 2026

View reviewed changes

kyteinsky reviewed Oct 12, 2026

View reviewed changes

kyteinsky reviewed Oct 14, 2026

View reviewed changes

Comment thread ex_app/lib/all_tools/calendar.py Resolved

Comment thread ex_app/lib/agent.py Resolved

Comment thread ex_app/lib/agent.py Resolved

Comment thread tests/test_schedule_event_payload.py Resolved

kyteinsky mentioned this pull request Oct 15, 2026

feat: add pytest as a dev dependency and a github CI workflow #270

Closed

kyteinsky approved these changes Oct 15, 2026

View reviewed changes

WSHAPER added 10 commits October 19, 2026 13:49

refactor(tools): default the timezone to the user's profile instead o…

178e3f8

…f requiring it Signed-off-by: WSHAPER <42714629+WSHAPER@users.noreply.github.com>

fix(tools): emit DATE values for all-day events with next-day DTEND

a26da61

Assisted-by: opencode:zai/glm-5.3 Signed-off-by: WSHAPER <42714629+WSHAPER@users.noreply.github.com>

refactor(tools): return timezone to its original position in update_task

e520460

Signed-off-by: WSHAPER <42714629+WSHAPER@users.noreply.github.com>

feat(agent): get_current_datetime tool, date-only system prompt

954172c

Assisted-by: opencode:zai/glm-5.3 Signed-off-by: WSHAPER <42714629+WSHAPER@users.noreply.github.com>

perf(agent): memoize the user timezone lookup per user

652b5ad

Signed-off-by: WSHAPER <42714629+WSHAPER@users.noreply.github.com>

test(tools): schedule_event payload tests for all-day and timed shapes

8aa9aec

Assisted-by: opencode:zai/glm-5.3 Signed-off-by: WSHAPER <42714629+WSHAPER@users.noreply.github.com>

docs(tools): state that schedule_event end_date is inclusive

ec291c0

Signed-off-by: WSHAPER <42714629+WSHAPER@users.noreply.github.com>

WSHAPER force-pushed the fix/timezone-handling branch from 15a86c0 to ec291c0 Compare October 19, 2026 12:16

WSHAPER merged commit e61f460 into nextcloud:main Oct 20, 2026
7 of 12 checks passed

marcelklehr mentioned this pull request Oct 20, 2026

fix(tools): only require a timezone where one is actually needed #277

Merged

WSHAPER mentioned this pull request Oct 20, 2026

all-day events can gain a day when the model passes an exclusive end date #279

Open

github-actions Bot added the feedback-requested label Oct 22, 2026

Conversation

WSHAPER commented Oct 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

WSHAPER commented Oct 12, 2026

Uh oh!

kyteinsky left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

WSHAPER commented Oct 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

WSHAPER commented Oct 19, 2026

Uh oh!

Uh oh!

github-actions Bot commented Oct 22, 2026

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

WSHAPER commented Oct 7, 2026 •

edited

Loading

WSHAPER commented Oct 14, 2026 •

edited

Loading