Cursor is consuming Anthropic (Claude) usage even when Claude is disabled

Hey, thanks for the detailed report. With this setup it’s much easier to see what’s going on.

Short answer: Cursor is not using your personal Claude subscription. Cursor models (Composer, Auto, and others) are billed through Cursor, and there’s no way for Cursor to spend your personal Claude Pro or Max plan. There isn’t even a claude.ai login inside Cursor. On our side, your account shows zero Anthropic model calls in the last 10 days. The Composer you selected was running as Composer. Also, using your personal Claude Max inside Cursor is still just an open feature request: Allow Claude Max / Claude Code Subscription Access in Cursor

The Claude usage you see is almost certainly coming from a separate tool on your machine. Most likely sources:

  1. claude-mem. It has a resident background worker that asynchronously updates memory via the Claude API. Important detail: disabling it in the config doesn’t always stop a process that’s already running. The worker is Bun-managed and can show up as bun in the process list, not claude, so a simple grep claude can miss it.
  2. A Claude Code CLI session. The CLI uses your personal Anthropic Pro or Max plan and can burn quota much faster than the web chat.
  3. An MCP server or an extension configured with an Anthropic API key.

OpenUsage shows your whole Anthropic account, so any of these will look like Claude usage even if Cursor is just open.

What to check, in this order so you don’t get a false clean result:

  • claude-mem worker PID file: cat ~/.claude-mem/.worker.pid
  • By port: lsof -i :37777 (in some versions the port is computed as 37700 + (uid % 100))
  • General process scan: ps aux | grep -iE 'claude|bun' (keep in mind the worker can appear as bun)
  • Make sure the claude-mem daemon is actually stopped, not just disabled in config

Also, anything you run in Cursor’s integrated terminal is your own process on your own subscription. Cursor doesn’t take part in that and doesn’t bill it.

Send what those commands show. If there’s a live worker or a CLI session, that’s your source.