How to Connect Your Cursor Account to UsageBuddy

Last checked: September 25, 2026

Cursor has a desktop editor and a separate command-line tool. UsageBuddy's published release notes say its Add Account dialog checks for a provider's command-line tool, so install the Cursor CLI before connecting. UsageBuddy does not publish a minimum Cursor CLI version or say that the Cursor desktop editor is required.

⚠️ Important: UsageBuddy currently runs on 64-bit Windows 10 (version 1809 or later) and Windows 11. Its website says the Mac app is coming soon. You can install Cursor CLI on macOS, but you cannot run UsageBuddy there yet.

Install or update Cursor CLI

Cursor CLI works from a terminal and can be used with different editors. Installing it does not require replacing your current editor with Cursor Desktop.

Windows

  1. Open PowerShell from the Start menu.

  2. Paste the official installer and press Enter:

    irm 'https://cursor.com/install?win32=true' | iex

  3. Check the installed version:

    agent --version

macOS

  1. Open Terminal from Applications > Utilities.

  2. Paste the official installer and press Return:

    curl https://cursor.com/install -fsS | bash

  3. Check the installed version:

    agent --version

Cursor CLI tries to update itself automatically. To apply an update now, run agent update, then check the version again. The CLI supports browser sign-in and API-key authentication, but UsageBuddy's public documentation does not say whether you need to sign in to the CLI separately or whether its account connection supports API keys. For this guide, follow the browser authorization opened by UsageBuddy; do not paste an API key into the app unless it specifically asks for one.

Ask an AI assistant to check it for you

Paste this plain-English request into a coding assistant. It contains no terminal commands:

Check whether the official Cursor CLI is installed on this computer. If it is missing, install the latest version using Cursor's current instructions for this operating system. If it is installed, check whether a newer version is available and update it through the existing installation method. Do not change my editor or authentication method, and do not request or display API keys, tokens, or passwords. Verify the version afterward and report “old version -> new version”; if it was missing, report “not installed -> new version,” and if it was already current, say so. End with this exact line: “Now you’re ready to connect with UsageBuddy.”

Connect Cursor in UsageBuddy

  1. Open UsageBuddy.

  2. Click Add Account.

  1. Select Cursor.

  2. Enter an account name. Choose a label you will recognize later, such as “Personal Cursor” or “Work Cursor.”

  1. Click Continue.

  1. Complete Cursor authorization in the browser if UsageBuddy opens it. Sign in to the Cursor account you want to track and check that the browser is using the right account.

  1. Close the browser after authorization finishes.

  2. Return to UsageBuddy.

UsageBuddy can then show Cursor's reported usage and reset details beside your Codex and Claude Code accounts, so you can compare them from one dashboard.

Frequently asked questions

Do I need the Cursor desktop editor?

Cursor CLI can run from a terminal without replacing your editor. UsageBuddy's public materials mention checking for the provider CLI but do not list Cursor Desktop as a requirement. Install the CLI and follow UsageBuddy's browser authorization steps.

Do I need a Cursor API key?

The connection flow in this guide uses the browser authorization opened by UsageBuddy. Cursor CLI has a separate API-key option, but UsageBuddy has not published support for connecting accounts through that route.

Can I connect a Hobby, Start, Pro+, or Enterprise plan?

UsageBuddy's public sample shows Cursor Pro, Teams, and Ultra accounts. It does not publish compatibility details for Hobby, Start, Pro+, or Enterprise. Test your plan in the current app or ask UsageBuddy support before relying on it.

What if UsageBuddy says Cursor CLI is missing?

Open a new PowerShell window and run agent --version. If it does not print a version, complete the CLI installation above. If UsageBuddy shows I installed it, click it to check again.