-
Notifications
You must be signed in to change notification settings - Fork 37
Description
Description
My call-notes skill generates a transcript .docx file with a subtitle line that includes the meeting start time. This time is sourced from the codemie::msgraph /me/calendarView endpoint, which returns start.dateTime in UTC. The msgraph.js helper's fmtDt() function converts all times via .toISOString(), which always outputs UTC — discarding any original timezone context.
As a result, the subtitle in the generated transcript document shows UTC time with no timezone label, which is confusing for users in non-UTC timezones.
Example: A meeting that started at 12:00 local time (UTC+3, Belarus Standard Time) appears as Start: 09:00 with no timezone indicator.
Steps to Reproduce
- Have a Teams meeting with a transcript in a non-UTC timezone
- Run the
call-notesskill: "make summary for today's call" - Open the generated transcript
.docx - Observe the subtitle — start time is in UTC with no timezone label
Expected Behavior
The meeting start time in the transcript subtitle should either:
- Be converted to the user's local system timezone and labeled, e.g.
Start: 12:00 (UTC+3), or - Show the UTC time with an explicit label, e.g.
Start: 09:00 UTC
Actual Behavior
Subtitle shows Start: 09:00 — no timezone label, interpreted as local time by the reader.
Root Cause (identified)
fmtDt() in msgraph.js (line 244) always calls new Date(iso).toISOString() which strips timezone context and outputs UTC. The skill's transcript generator hardcodes the time string from this output without conversion or labeling.
Environment
| Field | Value |
|---|---|
| OS | MINGW64_NT-10.0-26200 3.6.4 x86_64 (Win 11) |
| Node.js | v24.14.0 |
| npm | 11.9.0 |
| CodeMie CLI | 0.0.52 |
| Shell | bash |
| Terminal | unknown |
Installed Agents
- CodeMie Code (0.0.46)
- Claude Code (2.1.78)
CodeMie Doctor Output
Full doctor output
Node.js: ✓ v24.14.0 npm: ✓ 11.9.0 Python: ✓ 3.14.3 uv: ✓ 0.9.13 AWS CLI: ⚠ not found (optional) Active Profile: AI Run for Sales Provider: ai-run-sso | CodeMie URL: https://codemie.lab.epam.com API Key: proxy-ha***dled | Model: claude-sonnet-4-6 CodeMie SSO: ✓ operational, session expires in 15h Installed Agents: CodeMie Code (0.0.46), Claude Code (2.1.78) ⚠ VCS provider not detected
Recent Errors
WARN/ERROR entries from recent logs (unrelated to this issue)
WARN: Local copy: 0 files copied from templates (possible Windows path separator issue) WARN: sso-session-sync - Sync had failures: Session not found ERROR: conversation-sync - Failed to sync conversation: API error 403