Skip to content

[Bug]: #80

Closed
Closed

Description

@nsevene

Preflight checklist

  • I searched existing issues and didn't find a duplicate.
  • I'm on the latest version of the extension, or I've written my version below.
  • I read the README's Troubleshooting section (proxies, history retention, the AI advice feature).

What happened?

version 2.2.1 is not working

What did you expect instead?

, after install 2.2.0 all works

Steps to reproduce

Open dashboard, and get error on 2.2.1 vers

Extension version

2.2.1

Claude Code version

No response

VS Code version

No response

Operating system

Windows

Model / proxy setup

No response

Diagnostic logs


Anything else?

No response

Activity

  1. github-actions commented on Jul 22, 2026

    @github-actions

    🤖 Automated first-pass reply

    TL;DR
    The report says the dashboard throws an error in 2.2.1 but works in 2.2.0. Without the exact error message or diagnostic logs, we can't tell where it breaks. Please share the concrete error text and the output of "Show Diagnostic Logs".

    Analysis
    The issue is a blank "after I upgraded, the dashboard errors" report with no error message, no logs, and no reproduction detail. The extension has many new features in 2.2.1 (Bahasa Indonesia, session filters, reset countdown formats, etc.) and while nothing in the changelog suggests an obvious crash bug, it's impossible to pinpoint a cause without seeing what actually happens.

    Suggested next step(s)

    1. Tell us exactly what you see when the dashboard opens — the full error message or a screenshot.
    2. Run "Claude Code Usage: Show Diagnostic Logs" from the Command Palette and paste the output here (it never contains prompts, paths, or personal data).
    3. Open VS Code’s Developer Tools (Help → Toggle Developer Tools → Console tab) and copy any red [Extension Host] errors related to Claude Code Usage.
    4. Try a clean reload (Reload Window) and confirm the VS Code version you are on (Help → About).

    Once we have that information we can track down what changed between 2.2.0 and 2.2.1 that causes the failure.


    🤖 Generated by DeepSeek as an automated first pass — not a maintainer decision.

  2. Carl723000 commented on Aug 1, 2026

    @Carl723000
    Collaborator

    v2.2.2 will include #79, which fixes a v2.2.1 regression where one unprobeable or unusual Claude JSONL file could make the entire Usage dashboard fail to open.

    Because this report does not include the original error or diagnostics, we cannot confirm that it has exactly the same cause. Please retest after v2.2.2 is published. If the dashboard still fails, run Claude Code Usage: Show Diagnostic Logs and share the refresh: lines plus the red Extension Host error from VS Code Developer Tools. We will keep the issue open until that result is known.


    🤖 Generated with OpenAI Codex

  3. Carl723000 commented on Aug 7, 2026

    @Carl723000
    Collaborator

    v2.2.2 has now been released and includes the fail-soft JSONL timestamp probe fix from #79. This addresses the v2.2.1 dashboard-startup regression we could identify from the available report.

    I’m closing this as fixed in v2.2.2. If the dashboard still fails on v2.2.2, please reopen this issue (or file a new one) with the refresh: diagnostic lines and the red Extension Host error so we can distinguish a different cause.


    🤖 Generated with OpenAI Codex

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions