fix(frontend): respect workspace timezone setting in date formatters (#59)

lsoldado · Davidson Gomes · claude · web-flow · commit 4ba4034cd9c7 · 2026-04-27T12:56:40.000-03:00
* fix(telegram): remove reply() from prod-review-todoist skill Telegram notification was still in the skill file, causing the agent to call reply() multiple times per run (3x observed on 25/04 at 06:51). Notification now controlled by notify_telegram=True in review_todoist.py (gitignored custom routine, already updated on disk). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(chat-bridge): resolve agent file from WORKSPACE_ROOT, not session cwd Ticket threads pass workspace_path (e.g. workspace/personal/) as the session cwd. loadAgentFile was building the path relative to that cwd, so it looked for .claude/agents/ inside the ticket's folder instead of the workspace root — always failing for every agent. Fix: try WORKSPACE_ROOT/.claude/agents/{name}.md first, fall back to cwd for custom per-directory agents. Affected: kai-personal-assistant, flux-finance, and any ticket with a workspace_path set. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(telegram): eliminate duplicate notifications from inline reply() template Root cause: notify_telegram instruction showed reply(chat_id=..., text="...") as an inline code snippet, causing the agent to execute it immediately on reading the instruction AND again at the end — 2x per instruction. Financial Pulse was getting 4x because the skill's Step 8 also contained a reply() call instruction (2 instructions × 2 executions = 4 messages). Fixes: - runner.py: rewrite notify_telegram prompt to describe the action in plain text without an inline function-call template - fin-daily-pulse SKILL.md: remove Step 8 Telegram section — notification is handled by the routine caller via notify_telegram=True Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(telegram): remove all inline reply() calls from skill SKILL.md files Comprehensive sweep of all 175+ skills. Root cause of all duplicate Telegram notifications: skills contained inline reply(chat_id=...) code examples that Claude executed immediately on reading, then called again at the actual end-of-skill step — causing 2x (or 4x when combined with a second instruction from notify_telegram=True in the routine). Changes: - Removed "Notify via Telegram" sections entirely from 10 skills that have a corresponding routine using notify_telegram=True: fin-weekly-report, gog-email-triage, prod-dashboard, prod-trends, pulse-monthly, pulse-weekly, sage-strategy-digest, fin-monthly-close-kickoff, social-analytics-report, social-youtube-report - Rewrote Telegram instructions without inline reply() code in 4 skills that are called without notify_telegram (heartbeat or conditional): int-sync-meetings, int-github-review, int-linear-review (plain text), custom-getfy-sync, custom-omc-sync (plain text, local/gitignored) The corresponding routines (gitignored) were updated locally to add notify_telegram=True where the section was removed. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(frontend): respect workspace timezone setting in date formatters The workspace settings page exposes a timezone selector (Settings.tsx already saves `workspace.timezone` via /api/settings/workspace), but the four pages that render timestamps — Topics, TicketDetail, Tasks, and the "last seen" text on Settings itself — hardcoded `timeZone: 'America/Sao_Paulo'` in their local formatDate helpers. Effect: users outside São Paulo saw timestamps shifted by their local offset minus −03:00. A user in Europe/London (BST) saw all ticket timestamps 4 hours behind their wall clock. This patch centralises date formatting in `lib/format.ts`: - `loadWorkspaceTimezone()` fetches the workspace config once after login (called from App.tsx alongside the other hydrate calls) and caches the IANA tz in a module variable + localStorage so subsequent paints don't have to wait on the API. - `getTimezoneSync()` returns cache → localStorage → browser default, in that order, never throwing. - `formatDateTime(iso)` and `formatDate(iso)` use the cached tz. - `refreshWorkspaceTimezone(tz)` is called from the Settings save handler so the change is reflected without a hard reload. Topics.tsx, TicketDetail.tsx and Tasks.tsx now alias their local `formatDate` to the shared `formatDateTime`, removing the hardcoded São Paulo string. The behaviour is unchanged for users on São Paulo (workspace setting still defaults to that value); users on any other configured timezone now see correct timestamps. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(format): don't overwrite freshly-refreshed cache on slow API resolve Sourcery flagged a race in loadWorkspaceTimezone: if the user updated the timezone via Settings → refreshWorkspaceTimezone while the initial GET /settings/workspace was still in flight, the eventual resolution of that GET would overwrite cachedTz (and localStorage) with the stale server value, silently reverting the user's change until the next reload. Fix: in both the success and failure handlers, only write if cachedTz is still null. If anything else claimed the cache in the meantime, keep the fresher value. Reported-by: sourcery-ai[bot] on PR #59 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * chore: regenerate uv.lock after rebase on develop Develop bumped evo-nexus to 0.33.0 (release aa33f7d) and added flask-limiter / limits / wrapt / etc. via the rate-limit + plugin contract work. The branch's old uv.lock was carrying 0.32.2 which would regress the project version on merge. Re-running `uv lock` syncs the file with the current pyproject.toml and develop's deps. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Davidson Gomes <davidson.gomes@etus.com.br> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> Co-authored-by: Davidson Gomes <davidson.gomes@evofoundation.com.br>
diff --git a/.claude/skills/fin-daily-pulse/SKILL.md b/.claude/skills/fin-daily-pulse/SKILL.md
@@ -157,9 +157,9 @@ workspace/finance/reports/daily/[C] YYYY-MM-DD-financial-pulse.html
 
 Create the directory `workspace/finance/reports/daily/` if it does not exist.
 
-## Step 8 — Confirm and notify (ONE Telegram message only)
+## Step 8 — Confirm
 
-Output the completion summary, then send **exactly one** Telegram message. Do NOT call `reply` more than once per run.
+Output the completion summary in the terminal:
 
 ```
 ## Financial Pulse generated
@@ -171,6 +171,4 @@ Output the completion summary, then send **exactly one** Telegram message. Do NO
 **Alerts:** {N} attention points
 ```
 
-Call `reply` **once** with a short summary (do not send the full markdown above — send a compact version):
-
-- Format: `[emoji] Financial Pulse [date] | MRR: R$ X,XXX | Receita: R$ X,XXX | Churn: X% | [N] alertas`
+Do NOT send a Telegram message here — the caller handles notifications.
diff --git a/.claude/skills/fin-monthly-close-kickoff/SKILL.md b/.claude/skills/fin-monthly-close-kickoff/SKILL.md
@@ -182,9 +182,3 @@ Create the directory `workspace/finance/reports/monthly/` if it does not exist.
 **Checklist:** X/10 completed
 **Finance team pending items:** {N} items
 ```
-
-### Notify via Telegram
-
-Upon completion, send a short summary via Telegram to the user:
-- Use the Telegram MCP: `reply(chat_id="YOUR_CHAT_ID", text="...")`
-- Format: emoji + "Monthly Close" + month's result + pending items (2-3 lines)
diff --git a/.claude/skills/fin-weekly-report/SKILL.md b/.claude/skills/fin-weekly-report/SKILL.md
@@ -164,9 +164,3 @@ Create the directory `workspace/finance/reports/weekly/` if it does not exist.
 **MRR total:** R$ X,XXX (Stripe: R$ X,XXX | Evo Academy: R$ X,XXX) | **Projected 30d balance:** R$ XX,XXX
 **Alerts:** {N} overdue accounts | {N} pending invoices
 ```
-
-### Notify via Telegram
-
-Upon completion, send a short summary via Telegram to the user:
-- Use the Telegram MCP: `reply(chat_id="YOUR_CHAT_ID", text="...")`
-- Format: emoji + "Financial Weekly" + revenue vs expenses + MRR + alerts (2-3 lines)
diff --git a/.claude/skills/gog-email-triage/SKILL.md b/.claude/skills/gog-email-triage/SKILL.md
@@ -354,11 +354,3 @@ See `skills/gog/_shared/references/testing.md` for complete test plan.
 - If email subject/sender contains obvious credentials or secrets, redact in output
 
 - For recurring newsletters, suggest creating a filter/rule rather than manual archiving
-
-
-### Notify via Telegram
-
-Upon completion, send a short summary via Telegram to the user:
-- Use the Telegram MCP: `reply(chat_id="YOUR_CHAT_ID", text="...")`
-- Format: emoji + routine name + main result (1-3 lines)
-- If the routine had no updates, send anyway with "no updates"
diff --git a/.claude/skills/int-github-review/SKILL.md b/.claude/skills/int-github-review/SKILL.md
@@ -118,7 +118,6 @@ Create directory if it does not exist.
 
 ### Notify via Telegram
 
-Upon completion, send a short summary via Telegram to the user:
-- Use the Telegram MCP: `reply(chat_id="YOUR_CHAT_ID", text="...")`
-- Format: emoji + routine name + main result (1-3 lines)
-- If the routine had no updates, send anyway with "no updates"
+Upon completion, use the Telegram reply tool to send a short summary to the user.
+Format: emoji + routine name + main result (1-3 lines).
+If the routine had no updates, send anyway with "no updates".
diff --git a/.claude/skills/int-linear-review/SKILL.md b/.claude/skills/int-linear-review/SKILL.md
@@ -97,7 +97,6 @@ Create the directory `workspace/projects/linear-reviews/` if it does not exist.
 
 ### Notify via Telegram
 
-Upon completion, send a short summary via Telegram to the user:
-- Use the Telegram MCP: `reply(chat_id="YOUR_CHAT_ID", text="...")`
-- Format: emoji + routine name + main result (1-3 lines)
-- If the routine had no updates, send anyway with "no updates"
+Upon completion, use the Telegram reply tool to send a short summary to the user.
+Format: emoji + routine name + main result (1-3 lines).
+If the routine had no updates, send anyway with "no updates".
diff --git a/.claude/skills/int-sync-meetings/SKILL.md b/.claude/skills/int-sync-meetings/SKILL.md
@@ -186,12 +186,13 @@ Without listing tasks one by one — just counts. If the user wants details, the
 
 ### Step 9 — Notify via Telegram
 
-Send the Step 8 summary via Telegram to the user using the `/int-telegram` skill:
-- Chat ID: `YOUR_CHAT_ID`
-- Use `reply(chat_id="YOUR_CHAT_ID", text="...")` via MCP
-- Short format: emoji + title + meeting and task count
+Only send if at least one new meeting was processed (i.e., you did NOT stop at Step 2).
 
-If there are no new meetings (stopped at Step 2), do **NOT** send any Telegram message — stay silent. Only notify when at least one new meeting was processed.
+Use the Telegram reply tool with the user's chat_id and a short summary:
+- Format: emoji + title + meeting count + task count
+- One line only
+
+If there are no new meetings (stopped at Step 2), do **NOT** send any Telegram message — stay completely silent.
 
 ## Notes
 
diff --git a/.claude/skills/prod-dashboard/SKILL.md b/.claude/skills/prod-dashboard/SKILL.md
@@ -142,10 +142,3 @@ Present a short summary:
 **Health:** Product {status} | Community {status} | Financial {status} | Routines {status}
 **Alerts:** {N} attention points
 ```
-
-### Notify via Telegram
-
-Upon completion, send a short summary via Telegram to the user:
-- Use the Telegram MCP: `reply(chat_id="YOUR_CHAT_ID", text="...")`
-- Format: emoji + routine name + health status of each area (1-3 lines)
-- If there were no updates, send anyway with "no updates"
diff --git a/.claude/skills/prod-review-todoist/SKILL.md b/.claude/skills/prod-review-todoist/SKILL.md
@@ -124,10 +124,3 @@ If the user wants to see details of what changed, they ask.
 - **If unsure about the category**, use `[Operations]` as fallback
 - **Execute first, report after** — no intermediate report
 
-
-### Notify via Telegram
-
-Upon completion, send **exactly ONE** Telegram message — do NOT call `reply()` more than once per run:
-- Use the Telegram MCP: `reply(chat_id="YOUR_CHAT_ID", text="...")`
-- Format: emoji + routine name + main result (1-3 lines, all combined in a single message)
-- If the routine had no updates, send anyway with "no updates"
diff --git a/.claude/skills/prod-trends/SKILL.md b/.claude/skills/prod-trends/SKILL.md
@@ -163,11 +163,3 @@ Create `memory/trends/` if it does not exist.
 - **If a source has no data, skip** — do not block due to a missing report
 - **Focus on action** — each insight should lead to a concrete recommendation
 - **Do not alarm without evidence** — red only when the metric truly indicates risk
-
-
-### Notify via Telegram
-
-Upon completion, send a short summary via Telegram to the user:
-- Use the Telegram MCP: `reply(chat_id="YOUR_CHAT_ID", text="...")`
-- Format: emoji + routine name + main result (1-3 lines)
-- If the routine had no updates, send anyway with "no updates"
diff --git a/.claude/skills/pulse-monthly/SKILL.md b/.claude/skills/pulse-monthly/SKILL.md
@@ -178,9 +178,3 @@ Create the directory `workspace/community/reports/monthly/` if it does not exist
 **Sentiment:** {trend} | **Resolution:** {X}%
 **Highlights:** {N} features, {N} bugs, {N} docs gaps
 ```
-
-### Notify via Telegram
-
-Upon completion, send a short summary via Telegram to the user:
-- Use the Telegram MCP: `reply(chat_id="YOUR_CHAT_ID", text="...")`
-- Format: emoji + "Community Monthly" + MAM + sentiment + highlights (2-3 lines)
diff --git a/.claude/skills/pulse-weekly/SKILL.md b/.claude/skills/pulse-weekly/SKILL.md
@@ -111,11 +111,3 @@ Report saved to workspace/community/reports/weekly/
 - **Docs gap is gold** — each question without docs becomes a backlog item
 - **Comparison is fundamental** — always show trend vs previous week
 - **Product insights** — the most valuable section, handle with care
-
-
-### Notify via Telegram
-
-Upon completion, send a short summary via Telegram to the user:
-- Use the Telegram MCP: `reply(chat_id="YOUR_CHAT_ID", text="...")`
-- Format: emoji + routine name + main result (1-3 lines)
-- If the routine had no updates, send anyway with "no updates"
diff --git a/.claude/skills/sage-strategy-digest/SKILL.md b/.claude/skills/sage-strategy-digest/SKILL.md
@@ -96,11 +96,3 @@ Present a short and direct version.
 - **Opinions flagged** — when it is opinion vs data, make it clear
 - **One recommendation** — do not give 10 suggestions, give 1 clear one
 - **Connect the dots** — the value of the digest is crossing areas, not repeating individual reports
-
-
-### Notify via Telegram
-
-Upon completion, send a short summary via Telegram to the user:
-- Use the Telegram MCP: `reply(chat_id="YOUR_CHAT_ID", text="...")`
-- Format: emoji + routine name + main result (1-3 lines)
-- If the routine had no updates, send anyway with "no updates"
diff --git a/.claude/skills/social-analytics-report/SKILL.md b/.claude/skills/social-analytics-report/SKILL.md
@@ -137,16 +137,3 @@ workspace/social/reports/consolidated/[C] YYYY-MM-DD-social-analytics.html
 ```
 
 Create directory if it does not exist.
-
-### Step 9 — Telegram
-
-Notify: `reply(chat_id="YOUR_CHAT_ID", text="...")`
-Format:
-```
-📊 Social Analytics — {period}
-👥 Total followers: {N} ({delta})
-📹 YouTube: {subs} sub | {eng}% eng
-📸 Instagram: {followers} fol | {eng}% eng  
-💼 LinkedIn: profile connected
-🏆 Top: "{best content}" ({platform}, {eng}%)
-```
diff --git a/.claude/skills/social-youtube-report/SKILL.md b/.claude/skills/social-youtube-report/SKILL.md
@@ -64,8 +64,3 @@ workspace/social/reports/youtube/[C] YYYY-MM-DD-youtube-{period}.html
 ```
 
 Criar diretório if it does not exist.
-
-### Step 7 — Telegram
-
-Notify: `reply(chat_id="946857210", text="...")`
-Format: emoji + canal + inscritos + delta + melhor vídeo
diff --git a/ADWs/runner.py b/ADWs/runner.py
@@ -317,11 +317,13 @@ def run_skill(
         )
         if chat_id:
             prompt += (
-                f"\n\nAo concluir TODOS os passos acima, envie UMA única mensagem Telegram via:"
-                f'\nreply(chat_id="{chat_id}", text="...")'
-                f"\nFormato: emoji + nome da rotina + principais resultados em 2-3 linhas."
-                f"\nCRÍTICO: chame reply() EXATAMENTE UMA VEZ, somente aqui no final."
-                f" Não envie mensagens intermediárias nem de progresso."
+                f"\n\n---\n"
+                f"NOTIFICAÇÃO TELEGRAM — executar SOMENTE após concluir TODOS os passos acima.\n"
+                f"Use a ferramenta Telegram reply com chat_id={chat_id} e um texto compacto:\n"
+                f"  emoji + nome da rotina + data + principais resultados em 2-3 linhas.\n"
+                f"REGRA ABSOLUTA: chame a ferramenta reply UMA ÚNICA VEZ, no final de tudo.\n"
+                f"Nunca chame reply para progresso, confirmação intermediária ou teste.\n"
+                f"---"
             )
     return run_claude(prompt, log_name or skill_name, timeout, agent=agent)
 
diff --git a/dashboard/frontend/src/App.tsx b/dashboard/frontend/src/App.tsx
@@ -4,6 +4,7 @@ import { AuthProvider, useAuth } from './context/AuthContext'
 import { hydrateAgentMeta } from './lib/agent-meta'
 import { hydratePluginUiRegistry } from './lib/plugin-ui-registry'
 import { initEvoNexusSdk } from './lib/evonexus-sdk'
+import { loadWorkspaceTimezone } from './lib/format'
 import PluginPageHost from './pages/PluginPageHost'
 import { NotificationProvider } from './context/NotificationContext'
 import Sidebar from './components/Sidebar'
@@ -135,6 +136,7 @@ function AppContent() {
       hydrateAgentMeta()
       hydratePluginUiRegistry()
       initEvoNexusSdk()
+      loadWorkspaceTimezone()
     }
   }, [user])
 
diff --git a/dashboard/frontend/src/lib/format.ts b/dashboard/frontend/src/lib/format.ts
@@ -0,0 +1,105 @@
+// Shared date/time formatting that respects the workspace timezone setting.
+//
+// Order of preference for the IANA timezone:
+//   1. workspace.timezone from /api/settings/workspace  (the explicit user choice)
+//   2. localStorage cache (so the first paint isn't always wrong)
+//   3. Browser default (Intl.DateTimeFormat().resolvedOptions().timeZone)
+//
+// Previously every page hardcoded `America/Sao_Paulo`, which gave a 4h drift
+// for users in Europe and a different drift everywhere else.
+
+import { api } from './api'
+
+const STORAGE_KEY = 'evo:workspace-timezone'
+
+let cachedTz: string | null = null
+let inflight: Promise<string> | null = null
+
+function browserTz(): string {
+  try {
+    return Intl.DateTimeFormat().resolvedOptions().timeZone || 'UTC'
+  } catch {
+    return 'UTC'
+  }
+}
+
+/** Synchronously read whatever timezone we know right now. Never throws. */
+export function getTimezoneSync(): string {
+  if (cachedTz) return cachedTz
+  try {
+    const stored = window.localStorage.getItem(STORAGE_KEY)
+    if (stored) {
+      cachedTz = stored
+      return stored
+    }
+  } catch {
+    // localStorage unavailable (SSR, private mode) — ignore
+  }
+  return browserTz()
+}
+
+/** Fetch from API and cache. Subsequent callers reuse the in-flight promise.
+ *
+ * Race-safe with `refreshWorkspaceTimezone`: if the user updates the setting
+ * (or any other code path populates the cache) while this fetch is in flight,
+ * the resolved value is dropped — we never overwrite a fresher cache value
+ * with the stale server response. */
+export async function loadWorkspaceTimezone(): Promise<string> {
+  if (cachedTz) return cachedTz
+  if (inflight) return inflight
+  inflight = api
+    .get('/settings/workspace')
+    .then((data: any) => {
+      const tz: string = data?.workspace?.timezone || browserTz()
+      // Only write if nothing else claimed the cache in the meantime
+      // (e.g. a concurrent refreshWorkspaceTimezone from Settings save).
+      if (cachedTz == null) {
+        cachedTz = tz
+        try { window.localStorage.setItem(STORAGE_KEY, tz) } catch { /* noop */ }
+      }
+      return cachedTz!
+    })
+    .catch(() => {
+      const fallback = browserTz()
+      if (cachedTz == null) {
+        cachedTz = fallback
+      }
+      return cachedTz!
+    })
+    .finally(() => { inflight = null })
+  return inflight
+}
+
+/** Invalidate cache after the user updates the setting. */
+export function refreshWorkspaceTimezone(tz?: string): void {
+  if (tz) {
+    cachedTz = tz
+    try { window.localStorage.setItem(STORAGE_KEY, tz) } catch { /* noop */ }
+  } else {
+    cachedTz = null
+    try { window.localStorage.removeItem(STORAGE_KEY) } catch { /* noop */ }
+  }
+}
+
+/** Format an ISO timestamp using the workspace timezone (or fallback). */
+export function formatDateTime(iso: string | null | undefined): string {
+  if (!iso) return '--'
+  const d = new Date(iso)
+  if (Number.isNaN(d.getTime())) return '--'
+  return d.toLocaleString('pt-BR', {
+    timeZone: getTimezoneSync(),
+    day: '2-digit', month: '2-digit', year: '2-digit',
+    hour: '2-digit', minute: '2-digit',
+  })
+}
+
+/** Format an ISO timestamp date-only. */
+export function formatDate(iso: string | null | undefined): string {
+  if (!iso) return '--'
+  const d = new Date(iso)
+  if (Number.isNaN(d.getTime())) return '--'
+  return d.toLocaleDateString('pt-BR', {
+    timeZone: getTimezoneSync(),
+    day: '2-digit', month: '2-digit', year: 'numeric',
+  })
+}
diff --git a/dashboard/frontend/src/pages/Settings.tsx b/dashboard/frontend/src/pages/Settings.tsx
@@ -7,6 +7,7 @@ import {
   Camera, Users, Compass, Cog, type LucideIcon,
 } from 'lucide-react'
 import { api } from '../lib/api'
+import { refreshWorkspaceTimezone } from '../lib/format'
 import Markdown from '../components/Markdown'
 
 // ── Toggle (copied from Providers.tsx) ─────────────────────────────────────
@@ -184,6 +185,9 @@ function WorkspaceTab({ showToast }: { showToast: (msg: string, type?: ToastType
         },
         dashboard: { port: config.port },
       })
+      // Refresh the cached timezone so date formatting on other pages
+      // picks up the change without a hard reload.
+      refreshWorkspaceTimezone(config.timezone)
       showToast('Workspace saved successfully')
     } catch {
       showToast('Failed to save workspace config', 'error')
diff --git a/dashboard/frontend/src/pages/Tasks.tsx b/dashboard/frontend/src/pages/Tasks.tsx
@@ -3,6 +3,7 @@ import { useToast } from '../components/Toast'
 import { useConfirm } from '../components/ConfirmDialog'
 import { CalendarClock, Plus, Play, X, Eye, RefreshCw, Pencil, Trash2 } from 'lucide-react'
 import { api } from '../lib/api'
+import { formatDateTime } from '../lib/format'
 import { useTranslation } from 'react-i18next'
 
 interface Task {
@@ -54,11 +55,8 @@ const AGENT_LABELS: Record<string, string> = {
   'mentor-courses': '@mentor',
 }
 
-function formatDate(iso: string | null): string {
-  if (!iso) return '--'
-  const d = new Date(iso)
-  return d.toLocaleString('pt-BR', { timeZone: 'America/Sao_Paulo', day: '2-digit', month: '2-digit', year: '2-digit', hour: '2-digit', minute: '2-digit' })
-}
+// Use shared formatDateTime from lib/format.ts — respects workspace.timezone setting.
+const formatDate = formatDateTime
 
 const emptyForm = { name: '', description: '', type: 'skill', payload: '', agent: '', scheduled_at: '' }
 
diff --git a/dashboard/frontend/src/pages/TicketDetail.tsx b/dashboard/frontend/src/pages/TicketDetail.tsx
@@ -8,6 +8,7 @@ import {
   PanelLeft,
 } from 'lucide-react'
 import { api } from '../lib/api'
+import { formatDateTime } from '../lib/format'
 import AgentChat from '../components/AgentChat'
 import ThreadsSidebar from '../components/ThreadsSidebar'
 import { TS_HTTP } from '../lib/terminal-url'
@@ -77,15 +78,8 @@ const STATUS_STYLES: Record<TicketStatus, string> = {
 const ALL_STATUSES: TicketStatus[] = ['open', 'in_progress', 'blocked', 'review', 'resolved', 'closed']
 const ALL_PRIORITIES: TicketPriority[] = ['urgent', 'high', 'medium', 'low']
 
-function formatDate(iso: string | null): string {
-  if (!iso) return '--'
-  const d = new Date(iso)
-  return d.toLocaleString('pt-BR', {
-    timeZone: 'America/Sao_Paulo',
-    day: '2-digit', month: '2-digit', year: '2-digit',
-    hour: '2-digit', minute: '2-digit',
-  })
-}
+// Use shared formatDateTime from lib/format.ts — respects workspace.timezone setting.
+const formatDate = formatDateTime
 
 function actionLabel(action: string, payload: Record<string, any>): string {
   switch (action) {
diff --git a/dashboard/frontend/src/pages/Topics.tsx b/dashboard/frontend/src/pages/Topics.tsx
diff --git a/dashboard/terminal-server/package-lock.json b/dashboard/terminal-server/package-lock.json
diff --git a/dashboard/terminal-server/src/chat-bridge.js b/dashboard/terminal-server/src/chat-bridge.js
diff --git a/uv.lock b/uv.lock
