budi

A quiet status bar item for VS Code and Cursor that shows your AI coding spend over the last 1 day / 7 days / 30 days, scoped to the IDE you're working in.

The extension is intentionally statusline-only:

• One status bar item. No sidebar, no session list, no tips feed.
• IDE-scoped. Always shows activity charged through the IDE you're using (Cursor, including Copilot-Chat-via-Cursor when present, or VS Code with Copilot Chat). If you use other AI tools outside the editor, those have their own surfaces; this extension does not blend them in.
• Rolling 1d / 7d / 30d windows. Three numbers, always current, always for this IDE.

Status bar at a glance

budi · \$2.34 1d · \$12.50 7d · \$48.10 30d

State	Status bar text	Meaning
healthy	budi · $X 1d · $Y 7d · $Z 30d	Daemon reachable, traffic recorded in the rolling window.
idle	budi · \$0.00 1d · \$0.00 7d · \$0.00 30d	Daemon reachable, no traffic in the rolling window (not an error).
offline	budi · offline	Daemon unreachable or api_version too old. Tooltip points to budi doctor.
loading	budi	Extension starting up, first reading not yet fetched.
setup	budi · setup	First run — daemon hasn't been installed yet. Click for the install flow.

Hover the item to see the rolling-window breakdown. The header reads budi — Cursor usage; if the daemon attributes a single non-Cursor sub-provider (e.g. Copilot-Chat-via-Cursor) it is parenthesised, and a Tracking: … line lists each contributing provider when more than one is in scope.

Click the item to open the budi cloud dashboard. When there is an active session it opens <cloud>/dashboard/sessions so you land on the live session; otherwise it opens <cloud>/dashboard for the rolling-window view.

Prerequisites

• budi installed and initialised (budi init).
• budi-daemon running (starts automatically after budi init).
• Use Cursor normally. No settings changes are required — the daemon tails Cursor's local session files and reconciles cost in the background.

First-run (no daemon installed yet)

If you discovered budi via the marketplace and haven't installed the daemon yet, the status bar shows budi · setup. Click it to open an in-editor welcome view that:

1. Pre-fills the one-line install command for your platform in the integrated terminal (you press enter yourself after reading it).
2. Offers a Finish setup in terminal button that pre-fills budi init && budi doctor once the daemon is detected.
3. Closes itself automatically on the first successful reading; the status bar starts reporting spend.

You can re-open the welcome view at any time with Cmd+Shift+P → Budi: Show Welcome / First-Run Setup.

Install

Search for "budi" in Cursor's extension panel — installs from Open VSX, which Cursor's extension panel uses by default. The extension also installs cleanly in VS Code / VSCodium for users who want their Cursor spend visible inside another editor.

Or install via the budi CLI:

budi integrations install --with cursor-extension

Run budi doctor to verify.

First-run smoke check

After install/reload, validate in under a minute:

1. Run budi doctor and confirm the daemon + tailer are healthy and your editor's transcripts are visible.
2. Send one prompt in Cursor's chat.
3. The status bar item should show a non-zero 1d spend within one poll cycle. Cursor cost can lag the Usage API by up to ~10 minutes, so seeing $0.00 1d in the first few minutes is normal on Cursor.
4. If 1d spend stays at $0.00, run Budi: Refresh Status once.

Manual install (build from source)

git clone https://github.com/siropkin/budi-cursor.git && cd budi-cursor
npm ci
npm test
npm run package

Then install the produced cursor-budi.vsix:

• Cursor — cursor --install-extension cursor-budi.vsix --force
• VS Code — code --install-extension cursor-budi.vsix --force

Reload your editor: Cmd+Shift+P → Developer: Reload Window.

Commands

Command	Description
Budi: Open Dashboard	Open the budi cloud dashboard (session list when a session is live).
Budi: Refresh Status	Force-refresh the status bar immediately.
Budi: Show Welcome / First-Run Setup	Re-open the onboarding welcome view (install + budi init hand-off).

Configuration

Setting	Default	Description
budi.pollingIntervalMs	15000	How often to refresh the status bar (ms).
budi.daemonUrl	http://127.0.0.1:7878	Local daemon base URL.
budi.cloudEndpoint	https://app.getbudi.dev	Cloud dashboard URL opened when the status bar item is clicked.

How it works

1. Local transcript tailers (no proxy, no editor settings changes). The budi daemon tails Cursor's local session files as they are written and reconciles cost/token totals from Cursor's own source on a pull cadence. All business logic — cost, classification, attribution — lives in the Rust daemon. Nothing is routed through an HTTP proxy and no editor base-URL override is involved.
2. Workspace signal. The extension writes the active workspace path to ~/.local/share/budi/cursor-sessions.json so the daemon can associate session activity with the workspace.
3. Cursor-scoped request. The extension always asks the daemon for ?surface=cursor, which scopes the response to activity routed through Cursor (including Copilot-Chat-via-Cursor when present). No client-side provider heuristic — the daemon's surface filter is the source of truth.
4. Shared rolling-window shape. The response is the rolling 1d / 7d / 30d shape the cloud dashboard also reads, so the number in the status bar and the number on the dashboard always agree for this IDE.

Troubleshooting

Status bar says budi · offline

1. Run budi doctor to check daemon + tailer health and transcript visibility.
2. Run budi init if the daemon is not running.
3. If you changed budi.daemonUrl, run Budi: Refresh Status (or reload the editor).

1d spend stays at $0.00 after sending prompts

1. Confirm the daemon is tailing your editor's transcripts (budi doctor shows transcript visibility).
2. Cursor cost comes from the Cursor Usage API on a pull cadence and can lag the chat by up to ~10 minutes. Wait a cycle and send a second message if today's value still reads zero.

Status bar says budi · update needed

The local daemon is older than this extension's required api_version. Run budi update (or brew upgrade budi) and reload the editor window. The tooltip names the installed daemon version, the required api_version, and the one-line upgrade command.

Ecosystem

• budi — Rust daemon + CLI (required).
• budi-jetbrains — JetBrains IDE plugin sibling.
• budi-cloud — Cloud dashboard and ingest API.
• homebrew-budi — Homebrew tap for the budi CLI.
• getbudi.dev — Public marketing site.