Skip to content

TokenGauge v0.0.4

Latest
Latest

Choose a tag to compare

View all tags
@Gares95 Gares95 released this 21 Aug 17:04
· 1 commit to main since this release
v0.0.4
c7e175b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Summary

TokenGauge v0.0.4 adds a guided setup path for the Claude Code statusLine, a compact terminal statusLine readout, and a substantial documentation pass, on top of the Codex weekly-window fix from v0.0.3.

This release keeps the existing package identity:

  • Publisher: gares-extensions
  • Name: tokengauge-vscode
  • Extension ID: gares-extensions.tokengauge-vscode
  • Version: 0.0.4

Added

  • TokenGauge: Set Up Claude statusLine writes the canonical Node statusLine writer, validates it, configures TokenGauge's snapshot path, and shows the exact Claude Code statusLine.command JSON to paste. TokenGauge still does not edit ~/.claude/settings.json.
  • A compact terminal statusLine readout from the canonical writer, so the same setup that feeds the cockpit can also show the provider-reported 5h and weekly windows in Claude Code's terminal status line.
  • Setup guidance for Windows and WSL workflows, while the README remains the concise setup authority.

Changed

  • The canonical statusLine writer body moved into docs/claude-statusline-writer.md, kept byte-identical to the shipped writer asset.
  • Clarified native-source freshness, multiple-writer behavior, missing rate_limits states, and why TokenGauge uses local native surfaces rather than provider credentials or conversation logs.
  • Reworked README, troubleshooting, SECURITY, and PRIVACY guidance for cleaner public onboarding and reader-first privacy/security reporting.

Fixed

  • The status bar now shows Codex's promoted weekly-only window when the local app-server reports weekly usage without a short window.
  • The setup command now reports writer, validation, and settings-scope failures more directly.
  • Release-documentation checks now protect the canonical writer location, freshness caveats, setup claims, packaged-link posture, and public-clean documentation boundaries.

Migration notes — action required for existing users

Re-copy your statusLine writer. The writer at ~/.tokengauge/claude/claude-statusline-writer.mjs is a copy-paste, not a dependency, so upgrading the extension does not update it. Until you refresh it, you keep the old TokenGauge snapshot updated output.

This applies whichever version you are coming from: Marketplace users have a writer copied from the 0.0.2 README, GitHub users from the 0.0.3 README. Both need to re-copy.

  • Run TokenGauge: Set Up Claude statusLine, or replace your local writer with the current copy from docs/claude-statusline-writer.md.
  • Review and merge the displayed statusLine.command into ~/.claude/settings.json yourself. TokenGauge does not edit that file.
  • The TokenGauge snapshot setting should point to the JSON snapshot file or per-session snapshot directory, not to the writer script.

Marketplace version jump

The Visual Studio Marketplace is on v0.0.2. v0.0.3 was published here on GitHub only and is not being published to the Marketplace.

  • Installing from the Marketplace: you move 0.0.2 to 0.0.4 and receive v0.0.3's changes in the same update — the Codex rateLimitsByLimitId acceptance fix and the Manual Refresh probe-state fix. The packaged changelog lists them under 0.0.3.
  • Installing from GitHub Releases: you already had v0.0.3, so this is a normal increment.

Security and maintenance

  • Full npm audit: zero vulnerabilities.
  • Production npm audit: zero vulnerabilities.

Install from GitHub Releases

Download the attached VSIX:

tokengauge-vscode-0.0.4.vsix

Verify its SHA-256:

d829190e31f5dfc762956139ddb7b92847f38f6dccc94e25f537e91af6176cde

Install from a terminal:

code --install-extension tokengauge-vscode-0.0.4.vsix

Visual Studio Marketplace

The permanent Marketplace identity remains:

gares-extensions.tokengauge-vscode

Marketplace publication of this exact v0.0.4 VSIX is a separate owner-authenticated upload step. Do not rebuild a different VSIX for Marketplace.

Validation

  • PR checks passed on Ubuntu, macOS, and Windows.
  • Post-merge checks passed on Ubuntu, macOS, and Windows.
  • CodeQL passed.
  • GitGuardian passed.
  • Local tagged-source validation passed with npm run check.
  • VSIX package audit passed with 13 entries.

Artifact provenance

  • Tag: v0.0.4
  • Commit: c7e175b3bb08b2012c1c61b4d9aac50310296809
  • Tree: d2551debcced7de483cf5a0d6f81f428570cef20
  • Final VSIX SHA-256: d829190e31f5dfc762956139ddb7b92847f38f6dccc94e25f537e91af6176cde
  • Packaged production extension/dist/extension.js SHA-256: 8ff971e2d64b7cc8a3c4c3145363ecf436618732d28d1daaaad06a09e24687b1
  • Packaged extension/dist/webview/cockpit.js SHA-256: 8a0f3c742efcb1cfdb5f719026efefa855ca60d09937ee9e547490632ae1a3b6
  • Packaged extension/dist/webview/assets/cockpit-CyFit-wK.css SHA-256: 16ae099ecea2b56ff1ac64e3f0fb63044080a5ad048bf1ce6c1567582aab92f0
Assets 4
Loading