Activity

1. ekimminau

   added

   bugSomething isn't workingSomething isn't working

   on Jul 1, 2026
2. Carl723000 commented on Jul 1, 2026

   

   Carl723000

   on Jul 1, 2026

   Collaborator

   More actions

   Thanks @ekimminau — good catch, and you're right that it should never have been accepted. Fix is up in #52: the timezone setting is now validated and an invalid value falls back to your system zone instead of throwing, so the dashboard can't be bricked this way (and it'll auto-recover your current config on next load). To unstick it right now, set the Timezone setting back to empty (⚙ Settings → General) — empty = system zone. A proper validated dropdown of zones is a sensible follow-up.

   👎React with 👎1Reacted by Eric Kimminau
3. ekimminau commented on Jul 1, 2026

   

   ekimminau

   on Jul 1, 2026

   Author

   More actions

   I wrote a script to modify the vscode db to correct the time zone:
   `C:\tmp> cat .\fix-claude-usage-timezone.ps1
   <#
   Fixes a corrupted timezone value ("EST-5 Detroit") stored by the "Claude Code Usage"
   VS Code extension inside VS Code's global state database (state.vscdb).

   This value is not a valid IANA timezone identifier, which is why the extension keeps
   reporting a "time zone configuration issue" even after uninstall/reinstall - the bad
   value lives in VS Code's globalState (state.vscdb), not in the extension's own files,
   so it survives extension removal.

   MUST be run with VS Code fully closed (the sqlite db is locked while VS Code is running).
   Run this in an elevated (Administrator) PowerShell window.
   #>

   $ErrorActionPreference = "Stop"

   $stateDbPath = "$env:APPDATA\Code\User\globalStorage\state.vscdb"
   $key = "GrowthJack.claude-code-usage"
   $badValue = "EST-5 Detroit"
   $goodValue = "America/Detroit"

   1. Refuse to run while VS Code is open - the db file will be locked and/or VS Code

   could overwrite our change on exit.

   $vscodeProcs = Get-Process -Name "Code" -ErrorAction SilentlyContinue
   if ($vscodeProcs) {
   Write-Host "VS Code is still running (found $($vscodeProcs.Count) Code.exe process(es)). Close it completely and re-run this script." -ForegroundColor Red
   exit 1
   }

   if (-not (Test-Path $stateDbPath)) {
   Write-Host "State database not found at: $stateDbPath" -ForegroundColor Red
   exit 1
   }

   2. Back up the database before touching it.

   $backupPath = "$stateDbPath.bak-$(Get-Date -Format 'yyyyMMdd-HHmmss')"
   Copy-Item -Path $stateDbPath -Destination $backupPath
   Write-Host "Backup created at: $backupPath" -ForegroundColor Green

   3. Patch the value using Python's built-in sqlite3 module.

   $pythonScript = @'
   import sqlite3
   import json
   import sys

   db_path, key, bad_value, good_value = sys.argv[1:5]

   con = sqlite3.connect(db_path)
   cur = con.cursor()
   cur.execute("SELECT value FROM ItemTable WHERE key = ?", (key,))
   row = cur.fetchone()
   if row is None:
   print("KEY_NOT_FOUND")
   sys.exit(1)

   raw = row[0]
   if isinstance(raw, bytes):
   raw = raw.decode("utf-8")

   data = json.loads(raw)
   current_tz = data.get("ccu.setting.timezone")
   print(f"Current value: {current_tz}")

   if current_tz != bad_value:
   print(f"WARNING: current timezone value does not match expected bad value ({bad_value!r}). No change made.")
   sys.exit(2)

   data["ccu.setting.timezone"] = good_value
   new_raw = json.dumps(data)

   cur.execute("UPDATE ItemTable SET value = ? WHERE key = ?", (new_raw, key))
   con.commit()
   con.close()
   print(f"Updated value to: {good_value}")
   '@

   $pythonScriptPath = Join-Path $env:TEMP "fix-ccu-timezone.py"
   Set-Content -Path $pythonScriptPath -Value $pythonScript -Encoding UTF8

   python $pythonScriptPath $stateDbPath $key $badValue $goodValue
   $exitCode = $LASTEXITCODE

   if ($exitCode -eq 0) {
   Write-Host "Done. Start VS Code and check the Claude Code Usage extension." -ForegroundColor Cyan
   } else {
   Write-Host "Patch did not apply cleanly (exit code $exitCode). Database was NOT modified beyond what the script reports above." -ForegroundColor Yellow
   }

   Write-Host "If anything looks wrong afterward, restore the backup with:" -ForegroundColor Yellow
   Write-Host " Copy-Item '$backupPath' '$stateDbPath' -Force" -ForegroundColor Yellow`
4. Carl723000

   added a commit that references this issue on Jul 6, 2026

   feat: V2.2 — usage share card, conversation viewer, insights suite, h…

   ...

   3badd1c
5. Carl723000 commented on Jul 12, 2026

   

   Carl723000

   on Jul 12, 2026

   Collaborator

   More actions

   Fixed as of v2.2.0 — the Timezone setting is now a validated dropdown (Intl.supportedValuesOf) and a guard rejects any previously-persisted invalid value, so a hand-typed/bad zone can no longer make Intl throw and crash the dashboard (i18n.ts isValidTimeZone; see CHANGELOG 2.2.0, "Timezone is a validated dropdown … (#51)"). Closing as resolved — please reopen if it still reproduces on 2.2.0+.

   ---

   🤖 Generated with Claude Code
6. Carl723000

   closed this as completedon Jul 12, 2026