UsageDock for VS Code

Keep your AI coding usage visible without leaving the editor.

UsageDock adds a compact local usage monitor for Cursor, Claude, GitHub Copilot, Codex, and Windsurf directly inside VS Code. It reads the same local auth state and usage signals your tools already use, then presents them in a focused sidebar view and status bar summary.

No UsageDock account. No hosted dashboard. No provider credentials sent to a UsageDock backend.

Why Use It

Editor-native usage glance: Check AI coding limits from the VS Code Activity Bar.
Local-first by design: UsageDock reads local provider state on your machine.
Multi-provider view: Cursor, Claude, Copilot, Codex, and Windsurf in one place.
Manual-first refresh: Usage does not refresh on open by default. You control when scans run.
Configurable auto refresh: Enable periodic refresh only if you want it.
Status bar signal: See connected provider count and a headline usage metric at a glance.

Supported Providers

Provider	What UsageDock Reads	Requirement
Cursor	Local Cursor auth state and usage API	Cursor installed and signed in
Claude	Local Claude credentials	Claude CLI/app authenticated locally
GitHub Copilot	GitHub CLI auth token	`gh auth login` completed
Codex	Local Codex auth state	Codex authenticated locally
Windsurf	Local Windsurf state and language server	Windsurf running and signed in

Unavailable providers stay visible as connection states so you know what needs attention.

Privacy

UsageDock is built around a local-first model:

Provider credentials are read only from local files or local tools already present on your machine.
UsageDock does not ask you to paste provider tokens into the extension.
UsageDock does not operate a hosted backend for usage tracking.
Usage data is rendered inside VS Code.
Refresh behavior is controlled through VS Code settings.

Provider APIs may still receive requests required to fetch your usage, using the provider auth already available locally.

Getting Started

Install the extension from the VS Code Marketplace or from a .vsix file.
Open the UsageDock icon in the Activity Bar.
Click Refresh All Providers to load usage.
Sign in to any provider that appears as unavailable.
Optional: open UsageDock: Open Settings to configure refresh behavior.

To install from a local VSIX:

code --install-extension usagedock-0.1.0.vsix

Settings

UsageDock intentionally does not refresh on open by default. You can change that from VS Code settings.

{
  "usagedock.autoRefresh.enabled": false,
  "usagedock.autoRefresh.intervalMinutes": 15,
  "usagedock.refreshOnOpen": false,
  "usagedock.statusBar.enabled": true
}

Setting	Default	Description
`usagedock.autoRefresh.enabled`	`false`	Refresh usage on a timer.
`usagedock.autoRefresh.intervalMinutes`	`15`	Auto-refresh interval. Supported values: `5`, `10`, `15`, `30`, `60`.
`usagedock.refreshOnOpen`	`false`	Refresh when the UsageDock sidebar view opens.
`usagedock.statusBar.enabled`	`true`	Show UsageDock in the VS Code status bar.

Commands

Use these from the Command Palette:

UsageDock: Refresh All Providers
UsageDock: Open Panel
UsageDock: Open Settings

Notes

GitHub Copilot usage requires the GitHub CLI to be installed and authenticated.
Windsurf usage requires Windsurf to be running so its local language server can be reached.
Remote environments such as SSH, containers, or Codespaces may not have access to the same local provider files as your desktop session.

Development

npm install
npm run build
npx @vscode/vsce package

The generated .vsix can be installed locally or uploaded to the VS Code Marketplace.

License

MIT

Usage-Dock

Anshuman Singh