Bug: Cockpit is hardcoded to Europe/Berlin

[sclawer]

What broke

At several points, the Timezome is hardcoded to Europe/Berlin, rather than any local timezone

Where

Several points - Search for Europe/Berlin to find all references - some hardcoded, some as variables

What you tried

Asking claude to several times to search through the cockpit to find and update to local timezone

What you expected

As part of onboarding, either derive or ask for current timezone and update a single vairalbe and have that referenced through out the code - otherwise update as part of onboarding

Environment (if relevant)

• LLM tool: Claude Code / Codex CLI / Gemini CLI / Cursor / Obsidian + chat / other
• Model: e.g. Claude Opus 4.7, GPT-5
• OS: macOS / Linux / Windows

[sclawer]

Files affected: 5

---

server/connectors/types.js (root of the issue)

• • @Property {string} day 'YYYY-MM-DD' in display tz (Europe/Berlin) — the column key

• • @Property {string} day 'YYYY-MM-DD' in display tz (Australia/Brisbane) — the column key

• • computed against this one zone, server-side, exactly once. (Europe/Berlin per the
• • cockpit's existing clickupTasks.js / tasks.js convention.)

• • computed against this one zone, server-side, exactly once.
• • Australia/Brisbane (UTC+10, no DST — stable offset year-round).

• export const DISPLAY_TZ = 'Europe/Berlin';

• export const DISPLAY_TZ = 'Australia/Brisbane';

---

server/connectorAdmin.js

• import { DISPLAY_TZ } from './connectors/types.js';

• timeZone: 'Europe/Berlin', year: 'numeric', month: '2-digit', day: '2-digit',

• timeZone: DISPLAY_TZ, year: 'numeric', month: '2-digit', day: '2-digit',

---

server/connectors/clickupTasksConn.js

• function berlinToday() {

• function brisbaneToday() {

• function msToBerlinDay(ms) {

• function msToBrisbaneDay(ms) {

• const today = berlinToday();

• const today = brisbaneToday();

• const day = msToBerlinDay(t.dueDate);

• const day = msToBrisbaneDay(t.dueDate);

---

server/connectors/ical.js (comments only)

• // overrides, and bucket each instance into day/half by LOCAL Europe/Berlin start

• // overrides, and bucket each instance into day/half by LOCAL Australia/Brisbane start

• // events bucket by Berlin start hour and render all-day on subsequent spanned days.

• // events bucket by Brisbane start hour and render all-day on subsequent spanned days.

• // Timed event. Day 1 buckets by Berlin start hour; further spanned days render as

• // Timed event. Day 1 buckets by Brisbane start hour; further spanned days render as

---

server/connectors/todoistTasks.js

• function berlinToday() {

• function brisbaneToday() {

• const today = berlinToday();

• const today = brisbaneToday();

---

Suggested bug title: DISPLAY_TZ hardcoded to Europe/Berlin — should be read from env or cockpit settings

Suggested fix to propose: DISPLAY_TZ is already correctly centralised in types.js as a single constant — the fix is
simply to make that constant read from an env var with a Berlin fallback:

export const DISPLAY_TZ = process.env.COCKPIT_DISPLAY_TZ || 'Europe/Berlin';

No other file needs to change — all connectors already import DISPLAY_TZ from types.js. The env var would sit
alongside the existing ones in .env.example and expansion.yaml.