Docs

Getting started with Clauder

Install the extension, read your Claude Code limits in the status bar, and connect the web dashboard.

Install Clauder from the VS Code Marketplace or Open VSX and keep Claude Code signed in. The extension reads your 5-hour and weekly usage with that sign-in and shows it in the status bar. You do not need an API key or aClauder account for this.

This page covers installing the extension, what the status bar shows, how often it refreshes, and how to connect the Clauder dashboard for predictions.

How do I install Clauder?

Install it from the store your editor uses. Both listings publish the same extension, nrentas.clauder, which needs VS Code 1.85 or newer.

The extension starts when the editor finishes loading. On first run it offers to install the Claude Code statusline for your terminal.

What does Clauder need from Claude Code?

Clauder needs Claude Code installed and signed in. It reuses the sign-in token that Claude Code already stored and sends it only to Anthropic's usage endpoint, never to clauder.fyi.

The extension looks for the token in this order:

  • The system credential store, under the entry Claude Code-credentials: Keychain on macOS, Credential Manager on Windows, Secret Service (secret-tool) on Linux
  • The file ~/.claude/.credentials.json

If it finds neither, the status bar reads Claude: Not authenticated. Run claude in a terminal, finish signing in, then click the status bar item. The data and privacy page lists every request the extension makes.

What appears in the status bar?

A single item on the right side of the status bar shows your 5-hour usage and the time until that window resets. Its color moves from tan to red as usage climbs. Clicking it refreshes the numbers.

By default the item rotates through slides every 5 seconds. Slides with no data are skipped.

Slide idWhat it shows
session5-hour usage percentage and time until reset
weeklyW, weekly usage percentage, and the day and time the weekly limit resets
etaPredicted time left before the 5-hour limit (needs dashboard sync)
burnRateCurrent burn rate in percent per minute (needs dashboard sync)
pacingWhether you are on pace, ahead or behind an even spread across the 5-hour window

When you hit a limit, the item switches to an error color and shows when it resets. When Anthropic rate-limits the usage endpoint, it shows Claude: Rate limited with a retry countdown. Several Claude Code sessions share one usage budget, so this happens most with many windows open.

With the carousel turned off, the item shows the 5-hour slide and adds weekly usage once it passes clauder.weeklyHighlightThreshold (90% by default).

How often does Clauder refresh usage?

Every 60 seconds by default. Change it with clauder.refreshInterval (5 to 300 seconds). Each interval varies by up to 20% in either direction so that several windows do not call Anthropic at the same moment, and the interval grows after a rate-limit response.

Only one editor window fetches at a time. The others read the shared cache file ~/.claude/usage-cache.json. Set clauder.rateLimit.coordinationMode to per-instance to make every window fetch on its own. Run Clauder: Refresh to fetch now.

How do I connect the Clauder dashboard?

Paste your license key into the extension settings and turn on sync. Sync and predictions need an active Pro plan or trial; the server rejects keys from other accounts.

  1. Sign in at clauder.fyi with GitHub, Google or GitLab.
  2. Copy the license key shown on the dashboard.
  3. Open the editor settings, search for clauder, and paste the key into clauder.sync.licenseKey.
  4. Turn on clauder.sync.enabled.

The extension then syncs every 30 seconds (clauder.sync.interval, 15 to 120 seconds) and fetches a fresh prediction after each sync. For the terminal statusline, set LICENSE_KEY in ~/.claude/clauder.conf instead. See how predictions work and what sync sends.

Which settings can I change?

SettingDefaultWhat it does
clauder.refreshInterval60Seconds between usage fetches (5-300)
clauder.weeklyHighlightThreshold90Weekly percentage at which weekly usage joins the status bar (50-100)
clauder.statusDisplaybothShow usage in the status bar, the shell statusline, or both (vscode, shell, both)
clauder.carousel.enabledtrueRotate slides in the status bar
clauder.carousel.interval5Seconds per slide (3-15)
clauder.carousel.slidessession, weekly, eta, burnRate, pacingWhich slides to show, in order
clauder.sounds.enabledtruePlay sounds when Claude Code finishes and when you near or hit a limit
clauder.sounds.warningThreshold80Usage percentage for the warning sound (50-99)
clauder.sync.enabledfalseSend usage to the dashboard
clauder.sync.licenseKeyemptyYour Clauder license key
clauder.sync.interval30Seconds between syncs (15-120)
clauder.rateLimit.coordinationModesingle-writerOne window fetches and the rest read the cache, or per-instance

Which commands does Clauder add?

Open the Command Palette (Ctrl+Shift+P, or Cmd+Shift+P on macOS) and type Clauder.

  • Clauder: Refresh fetches usage now.
  • Clauder: Install Shell Integration runs the statusline installer in a new terminal.
  • Clauder: Toggle Progress Display turns the statusline on or off in ~/.claude/settings.json.
  • Clauder: Next Status Bar Slide jumps to the next slide.
  • Clauder: Toggle Sound Notifications mutes or unmutes sounds.
  • Clauder: Show Diagnostics opens a report with cache contents, lock state and platform details for bug reports.
  • Clauder: Open Dashboard and Clauder: Open Usage History open the web dashboard.