unique-sdk 2026.44.0.dev9__tar.gz → 2026.44.0.dev10__tar.gz

{unique_sdk-2026.44.0.dev9 → unique_sdk-2026.44.0.dev10}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: unique-sdk
-Version: 2026.44.0.dev9
+Version: 2026.44.0.dev10
 Summary: 
 Author: Martin Fadler, Konstantin Krauss, Andreas Hauri
 Author-email: Martin Fadler <martin.fadler@unique.ch>, Konstantin Krauss <konstantin@unique.ch>, Andreas Hauri <andreas@unique.ch>

{unique_sdk-2026.44.0.dev9 → unique_sdk-2026.44.0.dev10}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "unique_sdk"
-version = "2026.44.0.dev9"
+version = "2026.44.0.dev10"
 description = ""
 readme = "README.md"
 license = { text = "MIT" }

{unique_sdk-2026.44.0.dev9 → unique_sdk-2026.44.0.dev10}/unique_sdk/api_resources/_scheduled_task.py

@@ -13,7 +13,8 @@ class ScheduledTask(APIResource["ScheduledTask"]):
     """Cron-tab style scheduled task that triggers an assistant on a recurring schedule.
 
     Each task defines a cron expression, an assistant to execute, an optional
-    chat to continue, and a prompt to send.
+    chat to continue, and a prompt to send. The cron is evaluated in
+    ``timezone`` when set, otherwise in UTC.
     """
 
     @classproperty
@@ -34,6 +35,7 @@ class ScheduledTask(APIResource["ScheduledTask"]):
         prompt: str
         name: NotRequired[str]
         chatId: NotRequired[str | None]
+        timezone: NotRequired[str]
         enabled: NotRequired[bool]
 
     class ModifyParams(RequestOptions):
@@ -42,6 +44,7 @@ class ScheduledTask(APIResource["ScheduledTask"]):
         prompt: NotRequired[str]
         name: NotRequired[str | None]
         chatId: NotRequired[str | None]
+        timezone: NotRequired[str | None]
         enabled: NotRequired[bool]
 
     class DeletedObject(TypedDict):
@@ -58,6 +61,7 @@ class ScheduledTask(APIResource["ScheduledTask"]):
     assistantId: str
     assistantName: str | None
     chatId: str | None
+    timezone: str | None
     prompt: str
     enabled: bool
     lastRunAt: str | None

{unique_sdk-2026.44.0.dev9 → unique_sdk-2026.44.0.dev10}/unique_sdk/cli/cli.py

@@ -1039,6 +1039,12 @@ def schedule_get(ctx: click.Context, task_id: str) -> None:
     required=True,
     help="Prompt text sent to the assistant on each trigger.",
 )
+@click.option(
+    "--timezone",
+    "-tz",
+    required=True,
+    help="IANA timezone the cron runs in, e.g. Europe/Zurich. Use UTC for UTC.",
+)
 @click.option(
     "--name",
     "-n",
@@ -1062,6 +1068,7 @@ def schedule_create(
     cron: str,
     assistant_id: str,
     prompt: str,
+    timezone: str,
     name: str | None,
     chat_id: str | None,
     disabled: bool,
@@ -1071,7 +1078,7 @@ def schedule_create(
     \b
     Defines a cron schedule, an assistant, and a prompt. The task
     will execute the assistant with the given prompt on every cron
-    match.
+    match. The cron is evaluated in --timezone.
 
     \b
     Cron expression format (5 fields):
@@ -1081,18 +1088,20 @@ def schedule_create(
     Examples:
       unique-cli schedule create \\
         --cron "0 9 * * 1-5" \\
+        --timezone Europe/Zurich \\
         --assistant clx1abc2d0001abcdef123456 \\
         --prompt "Generate the daily sales report" \\
         --name "Daily sales report"
 
       unique-cli schedule create \\
-        -c "*/15 * * * *" -a clx1abc -p "Check inbox" --disabled
+        -c "*/15 * * * *" -tz Europe/Zurich -a clx1abc -p "Check inbox" --disabled
     """
     output = cmd_schedule_create(
         LazyState.get(ctx),
         cron=cron,
         assistant_id=assistant_id,
         prompt=prompt,
+        timezone=timezone,
         name=name,
         chat_id=chat_id,
         enabled=not disabled,
@@ -1111,6 +1120,12 @@ def schedule_create(
 @click.option("--prompt", "-p", default=None, help="Updated prompt text.")
 @click.option("--name", "-n", default=None, help="Updated label (use 'none' to clear).")
 @click.option("--chat-id", default=None, help="Updated chat ID (use 'none' to clear).")
+@click.option(
+    "--timezone",
+    "-tz",
+    default=None,
+    help="IANA timezone the cron runs in (required with --cron).",
+)
 @click.option("--enable", is_flag=True, default=False, help="Enable the task.")
 @click.option("--disable", is_flag=True, default=False, help="Disable the task.")
 @click.pass_context
@@ -1122,6 +1137,7 @@ def schedule_update(
     prompt: str | None,
     name: str | None,
     chat_id: str | None,
+    timezone: str | None,
     enable: bool,
     disable: bool,
 ) -> None:
@@ -1130,10 +1146,11 @@ def schedule_update(
     \b
     TASK_ID is the scheduled task identifier. Only the fields you
     provide will be changed; everything else stays the same.
+    --timezone is required whenever --cron is given.
 
     \b
     Examples:
-      unique-cli schedule update clx3ghi4f --cron "0 9 * * 1-5"
+      unique-cli schedule update clx3ghi4f --cron "0 9 * * 1-5" --timezone Europe/Zurich
       unique-cli schedule update clx3ghi4f --disable
       unique-cli schedule update clx3ghi4f --enable --prompt "New prompt"
       unique-cli schedule update clx3ghi4f --chat-id none
@@ -1167,6 +1184,7 @@ def schedule_update(
         prompt=prompt,
         name=resolved_name,
         chat_id=resolved_chat_id,
+        timezone=timezone,
         enabled=enabled,
     )
     click.echo(output)

{unique_sdk-2026.44.0.dev9 → unique_sdk-2026.44.0.dev10}/unique_sdk/cli/commands/scheduled_tasks.py

@@ -46,6 +46,7 @@ def cmd_schedule_create(
     cron: str,
     assistant_id: str,
     prompt: str,
+    timezone: str,
     *,
     name: str | None = None,
     chat_id: str | None = None,
@@ -57,6 +58,7 @@ def cmd_schedule_create(
             "cronExpression": cron,
             "assistantId": assistant_id,
             "prompt": prompt,
+            "timezone": timezone,
             "enabled": enabled,
         }
         if name is not None:
@@ -84,9 +86,13 @@ def cmd_schedule_update(
     prompt: str | None = None,
     name: str | None = None,
     chat_id: str | None = None,
+    timezone: str | None = None,
     enabled: bool | None = None,
 ) -> str:
     """Update an existing scheduled task."""
+    if cron is not None and timezone is None:
+        return f"{SCHEDULE_ERROR_PREFIX} --timezone is required when changing --cron"
+
     try:
         params: dict[str, Any] = {}
         if cron is not None:
@@ -100,6 +106,8 @@ def cmd_schedule_update(
             params["name"] = name if name != "" else None
         if chat_id is not None:
             params["chatId"] = chat_id if chat_id != "" else None
+        if timezone is not None:
+            params["timezone"] = timezone
         if enabled is not None:
             params["enabled"] = enabled
 

{unique_sdk-2026.44.0.dev9 → unique_sdk-2026.44.0.dev10}/unique_sdk/cli/formatting.py

@@ -162,6 +162,7 @@ def format_scheduled_task(task: ScheduledTask) -> str:
         ["ID:", getattr(task, "id", "?")],
         ["Name:", getattr(task, "name", None) or "(falls back to prompt)"],
         ["Cron:", getattr(task, "cronExpression", "?")],
+        ["Timezone:", getattr(task, "timezone", None) or "UTC"],
         [
             "Assistant:",
             getattr(task, "assistantName", None) or getattr(task, "assistantId", "?"),
@@ -186,6 +187,7 @@ def format_scheduled_tasks(tasks: list[ScheduledTask]) -> str:
     for t in tasks:
         task_id = getattr(t, "id", "?")
         cron = getattr(t, "cronExpression", "?")
+        timezone = getattr(t, "timezone", None) or "UTC"
         enabled = "on" if getattr(t, "enabled", False) else "off"
         assistant = getattr(t, "assistantName", None) or getattr(t, "assistantId", "?")
         prompt = getattr(t, "prompt", "")
@@ -195,9 +197,20 @@ def format_scheduled_tasks(tasks: list[ScheduledTask]) -> str:
         # Mirrors the web UI: an unnamed task is identified by its prompt snippet.
         label = getattr(t, "name", None) or snippet
         last_run = _format_date(getattr(t, "lastRunAt", None))
-        rows.append([enabled, label, cron, assistant, snippet, task_id, last_run])
+        rows.append(
+            [enabled, label, cron, timezone, assistant, snippet, task_id, last_run]
+        )
 
-    header = ["STATUS", "NAME", "CRON", "ASSISTANT", "PROMPT", "ID", "LAST RUN"]
+    header = [
+        "STATUS",
+        "NAME",
+        "CRON",
+        "TIMEZONE",
+        "ASSISTANT",
+        "PROMPT",
+        "ID",
+        "LAST RUN",
+    ]
     lines = [f"{len(tasks)} scheduled task(s):\n"]
     all_rows = [header] + rows
     lines.extend(_pad_columns(all_rows))

{unique_sdk-2026.44.0.dev9 → unique_sdk-2026.44.0.dev10}/unique_sdk/cli/shell.py

@@ -1113,12 +1113,14 @@ class UniqueShell(cmd.Cmd):
           --cron / -c <expr>      Cron expression (required)
           --assistant / -a <id>   Assistant ID (required)
           --prompt / -p <text>    Prompt text (required)
+          --timezone / -tz <tz>   IANA timezone (required)
           --name / -n <text>      Short label shown in the UI (optional)
           --chat-id <id>          Chat to continue (optional)
           --disabled              Create in disabled state
 
         Update options:
           --cron / -c <expr>      Updated cron expression
+          --timezone / -tz <tz>   IANA timezone (required with --cron)
           --assistant / -a <id>   Updated assistant ID
           --prompt / -p <text>    Updated prompt
           --name / -n <text>      Updated label ('none' to clear)
@@ -1129,7 +1131,7 @@ class UniqueShell(cmd.Cmd):
         Examples:
           /> schedule list
           /> schedule get clx3ghi4f0003mnopqr345678
-          /> schedule create -c "0 9 * * 1-5" -a clx1abc -p "Daily report" -n "Daily report"
+          /> schedule create -c "0 9 * * 1-5" -tz Europe/Zurich -a clx1abc -p "Daily report" -n "Daily report"
           /> schedule update clx3ghi4f --disable
           /> schedule delete clx3ghi4f0003mnopqr345678
         """
@@ -1179,6 +1181,7 @@ class UniqueShell(cmd.Cmd):
         cron: str | None = None
         assistant_id: str | None = None
         prompt: str | None = None
+        timezone: str | None = None
         name: str | None = None
         chat_id: str | None = None
         disabled = False
@@ -1194,6 +1197,9 @@ class UniqueShell(cmd.Cmd):
             elif parts[i] in ("--prompt", "-p") and i + 1 < len(parts):
                 prompt = parts[i + 1]
                 i += 2
+            elif parts[i] in ("--timezone", "-tz") and i + 1 < len(parts):
+                timezone = parts[i + 1]
+                i += 2
             elif parts[i] in ("--name", "-n") and i + 1 < len(parts):
                 name = parts[i + 1]
                 i += 2
@@ -1207,10 +1213,10 @@ class UniqueShell(cmd.Cmd):
                 self._print(f"Unknown option: {parts[i]}")
                 return
 
-        if not cron or not assistant_id or not prompt:
+        if not cron or not assistant_id or not prompt or not timezone:
             self._print(
                 "Usage: schedule create --cron <expr> --assistant <id> --prompt <text> "
-                "[--name <text>] [--chat-id <id>] [--disabled]"
+                "--timezone <tz> [--name <text>] [--chat-id <id>] [--disabled]"
             )
             return
 
@@ -1220,6 +1226,7 @@ class UniqueShell(cmd.Cmd):
                 cron=cron,
                 assistant_id=assistant_id,
                 prompt=prompt,
+                timezone=timezone,
                 name=name,
                 chat_id=chat_id,
                 enabled=not disabled,
@@ -1233,6 +1240,7 @@ class UniqueShell(cmd.Cmd):
         prompt: str | None = None
         name: str | None = None
         chat_id: str | None = None
+        timezone: str | None = None
         enable = False
         disable = False
 
@@ -1247,6 +1255,9 @@ class UniqueShell(cmd.Cmd):
             elif parts[i] in ("--prompt", "-p") and i + 1 < len(parts):
                 prompt = parts[i + 1]
                 i += 2
+            elif parts[i] in ("--timezone", "-tz") and i + 1 < len(parts):
+                timezone = parts[i + 1]
+                i += 2
             elif parts[i] in ("--name", "-n") and i + 1 < len(parts):
                 name = "" if parts[i + 1].lower() == "none" else parts[i + 1]
                 i += 2
@@ -1282,6 +1293,7 @@ class UniqueShell(cmd.Cmd):
                 prompt=prompt,
                 name=name,
                 chat_id=chat_id,
+                timezone=timezone,
                 enabled=enabled,
             )
         )

{unique_sdk-2026.44.0.dev9 → unique_sdk-2026.44.0.dev10}/unique_sdk/cli/skills/unique-cli-scheduled-tasks/SKILL.md

@@ -73,31 +73,35 @@ months, after you have told the user it would not.
 
 ## Timezone handling (critical)
 
-**The platform runs all cron schedules in UTC.** The user almost certainly thinks in their local timezone. You **must** account for this difference or tasks will fire at the wrong time.
+**Write the cron in the user's local wall-clock time and always pass `--timezone`.** The
+platform evaluates the cron in that IANA timezone and keeps the local run time across daylight
+saving changes. Never convert local times to UTC. Never mention UTC equivalents or daylight
+saving shifts to the user.
 
-**Before creating or updating a schedule:**
-1. Check if you already know the user's timezone (from prior conversation, system info, or profile).
-2. If you do **not** know it, **ask**: "What timezone are you in? (e.g. Europe/Zurich, US/Eastern, Asia/Tokyo)"
-3. Convert the user's desired local time to UTC before building the cron expression.
-4. Confirm back in the **user's local timezone**, and mention the UTC equivalent.
+The CLI **rejects** `schedule create` without `--timezone`, and rejects `schedule update` that
+changes `--cron` without `--timezone`.
 
-**Conversion examples (Europe/Zurich, CET = UTC+1 / CEST = UTC+2):**
-
-| User says (local) | Season | UTC offset | Cron (UTC) |
-|--------------------|--------|------------|------------|
-| "9:00 AM" | Winter (CET) | UTC+1 | `0 8 * * *` |
-| "9:00 AM" | Summer (CEST) | UTC+2 | `0 7 * * *` |
-| "5:30 PM" | Winter (CET) | UTC+1 | `30 16 * * *` |
-| "midnight" | Winter (CET) | UTC+1 | `0 23 * * *` (previous day in UTC) |
+**Where the timezone comes from, in order:**
+1. The `User's timezone` line in the system prompt (browser-detected IANA name).
+2. A timezone already established earlier in the conversation.
+3. Otherwise, **ask**: "What timezone are you in? (e.g. Europe/Zurich, America/New_York, Asia/Tokyo)"
 
 **Rules:**
-- Always tell the user the schedule in **their local time** first, then add "(UTC: HH:MM)" in parentheses.
-- If the timezone has DST, warn the user: "Note: when daylight saving changes, the task will shift by one hour in your local time since the platform runs in UTC."
-- For interval-based schedules like "every 15 minutes" or "every 2 hours", timezone conversion is not needed — just mention that these run around the clock in UTC.
-- Store the user's timezone mentally for the rest of the conversation so you don't ask again.
+- Use **IANA names only** (`Europe/Zurich`, `America/New_York`, `Asia/Tokyo`). Never use
+  abbreviations (`CET`, `EST`) or UTC offsets (`+02:00`, `UTC+2`). The platform rejects them.
+- Pass `--timezone <IANA>` on every `create`, and on every `update` that changes `--cron`.
+- Write the cron for the user's local time. "9:00 AM in Zurich" → `-c "0 9 * * *"` `-tz Europe/Zurich`.
+- Confirm back in the user's local time only. Do **not** add "(UTC: …)" or warn about DST.
+- For interval schedules like "every 15 minutes", still pass `--timezone`.
+- Store the user's timezone for the rest of the conversation so you don't ask again.
+- To schedule explicitly in UTC, pass `--timezone UTC`.
+
+**Legacy tasks without a timezone:** If `schedule get` shows `Timezone: UTC` on a task the user
+thinks of in local time, any update to its schedule **must** pass the new local cron and
+`--timezone` together. Changing only the timezone reinterprets the old UTC cron as local time.
 
 **Example confirmation:**
-> "Done — scheduled to run **every weekday at 9:00 AM (your time, Europe/Zurich)**. That's 7:00 AM UTC in summer / 8:00 AM UTC in winter. Note: the exact local time will shift by 1 hour when daylight saving changes."
+> "Done — scheduled to run **every weekday at 9:00 AM your time (Europe/Zurich)**."
 
 ## Agent workflow for creating a task
 
@@ -114,11 +118,12 @@ Before running `schedule create`, **resolve / ask the user**:
 1. **Assistant** — Use `$UNIQUE_ASSISTANT_ID` (the current assistant). Do not
    ask. Do not run `unique-cli schedule list` to "find" one. Do not start an
    elicitation. If the env var is missing, surface that as an error and stop.
-2. **Timezone** — If not already known, ask for it first. You need this to convert times correctly.
+2. **Timezone** — Prefer the `User's timezone` line in the system prompt. If
+   missing and not already known, ask. You need an IANA name for `--timezone`.
 3. **New chat or existing chat?**
    - **New chat each run** (default) — omit `--chat-id`. Each execution creates a fresh chat.
    - **Continue an existing chat** — the user must provide a chat ID (starts with `chat_`). Pass it via `--chat-id`.
-4. **When should it run?** — Ask in plain language (e.g. "every weekday at 9 AM"). Convert to a UTC cron expression.
+4. **When should it run?** — Ask in plain language (e.g. "every weekday at 9 AM"). Translate to a **local-time** cron expression; do not convert to UTC.
 5. **Prompt text** — what the assistant should do on each trigger.
 6. **Name** — **you write it, do not ask for it.** Derive a short, descriptive label from the
    prompt (a few words, title-style, e.g. "Daily sales report", "Weekly pipeline review").
@@ -145,7 +150,7 @@ Only pass `--chat-id` when the user explicitly wants to continue a specific chat
 unique-cli schedule list
 ```
 
-Output shows a table with status, name, cron expression, assistant, prompt snippet, task ID, and last run time. A task saved without a name shows its prompt snippet in the name column.
+Output shows a table with status, name, cron expression, timezone, assistant, prompt snippet, task ID, and last run time. A task saved without a name shows its prompt snippet in the name column.
 
 ## Get Task Details
 
@@ -159,13 +164,14 @@ Shows full details of a single task including all fields.
 
 Always pass `--assistant "$UNIQUE_ASSISTANT_ID"` so the task runs on the
 current assistant. Do not substitute a literal `assistant_…` ID and do not
-ask the user to provide one.
+ask the user to provide one. Always pass `--timezone` with an IANA name.
 
 ### New chat each run (default — no `--chat-id`)
 
 ```bash
 unique-cli schedule create \
   --cron "0 9 * * 1-5" \
+  --timezone Europe/Zurich \
   --assistant "$UNIQUE_ASSISTANT_ID" \
   --prompt "Generate the daily sales report and email it to the team" \
   --name "Daily sales report"
@@ -176,6 +182,7 @@ unique-cli schedule create \
 ```bash
 unique-cli schedule create \
   --cron "0 9 * * 1-5" \
+  --timezone Europe/Zurich \
   --assistant "$UNIQUE_ASSISTANT_ID" \
   --chat-id chat_b7ze6mpv0edy324yhjj1d92t \
   --prompt "Append today's numbers to the running report" \
@@ -186,7 +193,8 @@ unique-cli schedule create \
 
 | Option | Short | Required | Description |
 |--------|-------|----------|-------------|
-| `--cron` | `-c` | Yes | 5-field cron expression |
+| `--cron` | `-c` | Yes | 5-field cron expression in the user's local time |
+| `--timezone` | `-tz` | Yes | IANA timezone the cron runs in (e.g. `Europe/Zurich`). Use `UTC` for UTC. |
 | `--assistant` | `-a` | Yes | Assistant ID to execute (starts with `assistant_`). **Always pass `"$UNIQUE_ASSISTANT_ID"`** — never ask the user. |
 | `--prompt` | `-p` | Yes | Prompt text sent each run |
 | `--name` | `-n` | No | Short label shown in the UI (≤128 chars). **Always pass one** — you generate it; without it the UI falls back to the prompt text |
@@ -195,7 +203,7 @@ unique-cli schedule create \
 
 ### Translating user requests to cron
 
-The user will describe schedules in plain language. Translate silently:
+The user will describe schedules in plain language. Translate silently into **local-time** cron:
 
 | User says | Cron expression |
 |-----------|-----------------|
@@ -230,10 +238,11 @@ Day-of-week mapping: 0=Sun, 1=Mon, 2=Tue, 3=Wed, 4=Thu, 5=Fri, 6=Sat, 7=Sun
 ## Update a Scheduled Task
 
 Only the fields you provide are changed; everything else stays the same.
+When changing `--cron`, you **must** also pass `--timezone`.
 
 ```bash
-# Change the schedule
-unique-cli schedule update <task_id> --cron "0 9 * * 1-5"
+# Change the schedule (timezone required with --cron)
+unique-cli schedule update <task_id> --cron "0 9 * * 1-5" --timezone Europe/Zurich
 
 # Disable a task
 unique-cli schedule update <task_id> --disable
@@ -249,7 +258,8 @@ unique-cli schedule update <task_id> --chat-id none
 
 | Option | Short | Description |
 |--------|-------|-------------|
-| `--cron` | `-c` | Updated cron expression |
+| `--cron` | `-c` | Updated cron expression (requires `--timezone`) |
+| `--timezone` | `-tz` | IANA timezone the cron runs in (required with `--cron`) |
 | `--assistant` | `-a` | Updated assistant ID (starts with `assistant_`) |
 | `--prompt` | `-p` | Updated prompt text |
 | `--name` | `-n` | Updated label (`none` to clear it and fall back to the prompt) |
@@ -271,40 +281,38 @@ This action cannot be undone.
 
 User: "Schedule a daily sales report every weekday at 9 AM"
 
-Agent (if timezone unknown): "What timezone are you in?"
-
-User: "Zurich"
-
-Agent thinks: Europe/Zurich, currently CEST (UTC+2), so 9:00 AM local = 7:00 AM UTC → cron `0 7 * * 1-5`. The assistant is the current one (`$UNIQUE_ASSISTANT_ID`); no need to ask.
+Agent thinks: System prompt has `User's timezone: Europe/Zurich`. Local cron is `0 9 * * 1-5`. The assistant is the current one (`$UNIQUE_ASSISTANT_ID`); no need to ask.
 
 Run:
 ```bash
 unique-cli schedule create \
-  -c "0 7 * * 1-5" \
+  -c "0 9 * * 1-5" \
+  -tz Europe/Zurich \
   -a "$UNIQUE_ASSISTANT_ID" \
   -p "Generate the daily sales report and email it to the team" \
   -n "Daily sales report"
 ```
 
-Respond: "Done — I created **Daily sales report**, running **every weekday (Mon–Fri) at 9:00 AM your time (Europe/Zurich)**. That's 7:00 AM UTC. A new chat will be created for each run. Note: when clocks change for daylight saving, the task will shift by one hour in your local time."
+Respond: "Done — I created **Daily sales report**, running **every weekday (Mon–Fri) at 9:00 AM your time (Europe/Zurich)**. A new chat will be created for each run."
 
 ### Set up a recurring task that continues the same chat
 
 User: "I want to add daily numbers to an existing report chat at 9 AM"
 
-Agent thinks: Already know timezone is Europe/Zurich (CEST), 9 AM local = 7 AM UTC. Assistant is the current one (`$UNIQUE_ASSISTANT_ID`).
+Agent thinks: Already know timezone is Europe/Zurich. Local cron is `0 9 * * 1-5`. Assistant is the current one (`$UNIQUE_ASSISTANT_ID`).
 
 Run:
 ```bash
 unique-cli schedule create \
-  -c "0 7 * * 1-5" \
+  -c "0 9 * * 1-5" \
+  -tz Europe/Zurich \
   -a "$UNIQUE_ASSISTANT_ID" \
   --chat-id chat_b7ze6mpv0edy324yhjj1d92t \
   -p "Append today's numbers to the running report" \
   -n "Running report top-up"
 ```
 
-Respond: "Done — I created **Running report top-up**, running **every weekday (Mon–Fri) at 9:00 AM your time** (7:00 AM UTC), continuing chat `chat_b7ze6mpv0edy324yhjj1d92t`."
+Respond: "Done — I created **Running report top-up**, running **every weekday (Mon–Fri) at 9:00 AM your time**, continuing chat `chat_b7ze6mpv0edy324yhjj1d92t`."
 
 ### Pause and resume a task
 
@@ -322,25 +330,25 @@ Respond: "The task is **active** again and will run on its next scheduled time."
 
 User: "Change it to run every hour instead"
 
-Agent thinks: "every hour" is interval-based, no timezone conversion needed.
+Agent thinks: Interval schedule; still pass the known timezone.
 
 Run:
 ```bash
-unique-cli schedule update <task_id> --cron "0 * * * *"
+unique-cli schedule update <task_id> --cron "0 * * * *" --timezone Europe/Zurich
 ```
 
-Respond: "Updated — the task now runs **every hour**, on the hour (UTC). Since this is interval-based, it runs at the same wall-clock intervals regardless of timezone."
+Respond: "Updated — the task now runs **every hour**, on the hour."
 
 User: "Actually, make it run at 6:30 PM my time on Fridays"
 
-Agent thinks: Europe/Zurich CEST (UTC+2), 6:30 PM = 16:30 UTC → cron `30 16 * * 5`
+Agent thinks: Europe/Zurich, local 6:30 PM → cron `30 18 * * 5`.
 
 Run:
 ```bash
-unique-cli schedule update <task_id> --cron "30 16 * * 5"
+unique-cli schedule update <task_id> --cron "30 18 * * 5" --timezone Europe/Zurich
 ```
 
-Respond: "Updated — the task now runs **every Friday at 6:30 PM your time** (4:30 PM UTC)."
+Respond: "Updated — the task now runs **every Friday at 6:30 PM your time**."
 
 ## SDK Usage (Python)
 
@@ -357,6 +365,7 @@ task = unique_sdk.ScheduledTask.create(
     user_id="user_123",
     company_id="company_456",
     cronExpression="0 9 * * 1-5",
+    timezone="Europe/Zurich",
     assistantId="assistant_cvj3fd7x8hpt1hfp0akqu1rq",
     prompt="Generate daily report",
     name="Daily report",
@@ -367,6 +376,7 @@ task = unique_sdk.ScheduledTask.create(
     user_id="user_123",
     company_id="company_456",
     cronExpression="0 9 * * 1-5",
+    timezone="Europe/Zurich",
     assistantId="assistant_cvj3fd7x8hpt1hfp0akqu1rq",
     chatId="chat_b7ze6mpv0edy324yhjj1d92t",
     prompt="Append today's data",
@@ -401,7 +411,8 @@ unique_sdk.ScheduledTask.delete(
 )
 ```
 
-All methods have `*_async` variants for async usage.
+All methods have `*_async` variants for async usage. Omitting `timezone` on create keeps
+UTC behaviour for backward compatibility; the CLI always requires it.
 
 ## Prerequisites