budi — Cursor Extension

A quiet status bar for budi that shows your Cursor spend over the last 1d / 7d / 30d — byte-for-byte matching the Claude Code statusline.

The extension is intentionally statusline-only:

• One status bar item. No sidebar, no session list, no tips feed.
• Cursor-scoped. Always shows Cursor IDE activity (the daemon attributes Copilot-Chat-via-Cursor here too). Never blends Claude Code, Codex CLI, or JetBrains usage — those have their own statuslines / extensions.
• Rolling 1d / 7d / 30d windows. The same shape the Claude Code statusline uses, so every budi surface reads identically for its respective scope.

Status bar at a glance

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

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 cloud dashboard. When there is an active session it opens <cloud>/dashboard/sessions; otherwise it opens <cloud>/dashboard — the same click-through behaviour as the Claude Code statusline.

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

Configuration

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 status contract. The response is the same rolling 1d / 7d / 30d shape the CLI statusline and the cloud dashboard use, so all three surfaces read identically.
5. No re-implementation of cost logic. If Claude Code's statusline shows $X 1d · $Y 7d · $Z 30d, this extension shows the same thing scoped to Cursor.

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. v1.5.x requires a v8.4.2-or-newer daemon.

Ecosystem

• budi — Rust daemon + CLI (required).
• budi-cloud — Cloud dashboard and ingest API.
• getbudi.dev — Public marketing site.