Augmeter: Assistant Usage for VS Code

See local coding-assistant activity alongside usage reported by connected providers.

Augmeter reads local Claude Code, Codex, and GitHub Copilot activity, with optional Augment credit data.

Local activity counts are signals, not provider quotas. Claude Code, Codex, and local Copilot activity stays on this machine. Augmeter contacts Augment for credit data and contacts GitHub only when Copilot API tracking is enabled.

Claude Code and Codex counts exclude tool results, metadata, and agent/subagent sessions. The local Copilot counter is cumulative because VS Code does not provide a reliable time window for it.

Augmeter is independent and open source. It is not affiliated with or endorsed by Augment, Anthropic, OpenAI, GitHub, or Microsoft. Product names are trademarks of their respective owners.

This screenshot is rendered from the current dashboard with illustrative values. It contains no local history, provider account data, or credentials.

See Understanding assistant usage data for the exact source and limitations of every number.

Install

Install Augmeter from the VS Code Marketplace, or search for Augmeter in the VS Code Extensions view.

Getting started

Assistant activity

Local Claude Code, Codex, and GitHub Copilot tracking starts automatically when the workspace is trusted. No separate account sign-in is required.

• Use augmeter.providers.enabledIds to choose assistants.
• Local Copilot counting requires sqlite3 on your PATH. You can instead enable official GitHub API data in augmeter.providers.copilot.api.enabled.
• Local file and VS Code database reading is off in untrusted workspaces.

Augment credits

Open Augmeter: Open Assistant Usage or click the disconnected status-bar item, then choose Connect Augment. The same connection command remains available in the Command Palette.

If Auggie CLI is installed and already connected, Augmeter reads auggie account status. No additional Augment sign-in is required, and Augmeter never reads CLI credentials.

Current Auggie CLI output reports a remaining balance and monthly allowance, but not exact cycle consumption. Augmeter labels that data as balance-only and does not infer 0 used, a percentage, pace, or trends. Exact cycle metrics appear only when the connected source supplies them.

npm install -g @augmentcode/auggie
auggie login

If VS Code cannot find an installed CLI, set augmeter.auggieCli.path to its full path.

Session-cookie fallback

When Auggie CLI is unavailable, Augmeter can use your Augment _session cookie:

1. Run Augmeter: Connect Augment.
2. Sign in at app.augmentcode.com.
3. In browser developer tools, open Application or Storage, then Cookies.
4. Copy the value of _session.
5. Paste it into Augmeter if clipboard detection has not already completed the connection.

This example is fully redacted. Copy only the cookie value.

The cookie is stored in VS Code's secure storage and used only for Augment requests. Augmeter watches the clipboard only during the connection step. Choose auto, auggie-cli, or cookie with augmeter.dataSource.

Treat _session as a credential: never paste it into an issue, log, screenshot, or exported diagnostic. If it is exposed, sign out of Augment to invalidate the session before connecting again.

Usage

The status bar labels Augment credit values when connected. Its tooltip and the Assistant usage view put local assistant activity first, whether or not Augment is connected.

The dashboard provides Refresh, Settings, and Connect Augment actions. Exports and support contains CSV/JSON exports, copy actions, and disconnect. Updates preserve keyboard focus, scroll position, and expanded details. Unavailable sources keep their last recorded values with a visible status; paused collection is labeled explicitly.

Local activity is cached for up to five minutes during background polling. Refresh bypasses this cache, and overlapping refreshes share one collection.

Commands

• Augmeter: Refresh Assistant Activity and Augment Credits updates every enabled source.
• Augmeter: Connect Augment reads credits through Auggie CLI or a session cookie.
• Augmeter: Disconnect Augment removes Augmeter's connection. It does not sign out Auggie CLI.
• Augmeter: Copy Augment Credit Summary copies the current Augment balance and pace.
• Augmeter: Open Assistant Usage opens local activity and usage reported by connected providers.
• Augmeter: Export Augment Credit History (CSV) exports local Augment snapshots.
• Augmeter: Export All Usage Data (JSON) exports credits, assistant activity, health states, and relevant settings.
• Augmeter: Copy Diagnostics copies support information with configured paths and GitHub usernames redacted. It excludes raw provider messages and details; review usage figures before sharing.
• Augmeter: Open Settings opens all Augmeter settings.

Configuration

All settings live under augmeter.* in VS Code Settings. These are the most common controls:

The status bar uses one consistent presentation: current Augment cycle usage, credits left, and native VS Code warning colors. The tooltip and Assistant Usage view provide the detailed breakdown.

Data sources and privacy

• Augment credit requests use Auggie CLI or the Augment API.
• Session cookies are stored in VS Code's secure storage and redacted from logs.
• Claude Code and Codex user-turn counts come from local session logs; tool results, metadata, and Claude Code/Codex agent/subagent sessions are excluded.
• Local Copilot activity is a cumulative counter from VS Code's database through a fixed, read-only sqlite3 query. VS Code does not expose a reliable time window for this counter.
• Optional official Copilot data reads GITHUB_TOKEN from the extension host environment. The token is not persisted by Augmeter.
• Credit history, assistant activity, and diagnostics remain local unless you export or paste them.
• Augmeter does not send extension analytics or telemetry events.
• Local file and database reading is disabled in untrusted workspaces.

For counting rules, freshness semantics, and a source-by-source explanation of the dashboard, see Understanding assistant usage data.

Augmeter ships with zero runtime package dependencies. It can invoke the existing auggie and sqlite3 binaries for the sources described above. See SECURITY.md for the subprocess, secret, and Workspace Trust model.

Requirements

• VS Code >= 1.104.0
• sqlite3 on PATH for local GitHub Copilot counts
• Node.js >= 20.18.0 for development only

Troubleshooting

• Augment credits not connected: Run Augmeter: Connect Augment. If a saved cookie expired, copy a fresh _session value.
• Augment credits keep loading: Run Refresh Assistant Activity and Augment Credits, then check your network and Output > Augmeter.
• No Claude Code or Codex activity: Confirm the configured path contains session logs and the workspace is trusted.
• No local Copilot activity: Install sqlite3, confirm GitHub Copilot has recorded requests, and check providers.copilot.stateDbPath only if VS Code data is stored in a custom location.
• No status-bar item: Check augmeter.enabled and augmeter.showInStatusBar, then review Output > Augmeter.

Contributing

1. Fork and clone the repo
2. npm install
3. Development:
   • Run and Debug > "Run Extension" (uses npm run watch)
   • Tests: npm run test:all (unit + integration) or npm run test:unit
   • Lint/format: npm run lint / npm run format
4. Package: npm run package (produces a .vsix)

Testing conventions

• Unit tests live in src/unit/ as *.unit.test.ts, run by Vitest in a Node environment with the VS Code API mocked (test-setup/vitest-setup.ts).
• Integration tests live in src/test/suite/ as *.test.ts, run in a real extension host via @vscode/test-cli (configured in .vscode-test.mjs, compiled with tsconfig.test.json).

Please follow conventional commit messages and keep changes focused. Open an issue first to discuss substantial changes.

Releasing

Releases are automated via GitHub Actions. Pushing a vX.Y.Z tag triggers the workflow, which lints, tests, packages a .vsix, creates a GitHub Release, and (if VSCE_PAT is configured) publishes to the VS Code Marketplace.

Steps

1. Bump version (do not create a git tag yet):

   npm version patch --no-git-tag-version
   # or: npm version minor --no-git-tag-version
   

2. Update CHANGELOG.md with the new version and changes.
3. Commit and tag:

   git add package.json package-lock.json CHANGELOG.md
   git commit -m "Release vX.Y.Z"
   git tag vX.Y.Z
   git push origin main --tags
   

4. The release workflow handles the rest.

What happens automatically

• Linting and tests run
• Tag is verified against package.json version
• .vsix artifact is built and uploaded
• GitHub Release is created with the .vsix attached
• If VSCE_PAT secret is set, the extension is published to the VS Code Marketplace

Troubleshooting

Manual fallback

If the automated publish fails, download the .vsix from the GitHub Release and upload it manually at https://marketplace.visualstudio.com/manage/publishers/kamacode.

License

MIT. See LICENSE.

Changelog

See GitHub Releases.