Project-level account binding for teams using multiple Cursor subscriptions

Feature request for product/service

Cursor IDE

Describe the request

Many of us work with multiple organizations/clients, and thanks for implementing the account logout/login flow. It really helps.

At the moment, the active subscription is tied globally to the currently signed-in account in the IDE. Because of this, it’s quite easy to accidentally use the wrong account when working in a different project folder or workspace.

Is there any plan to support project/workspace-level subscription or account binding, so a specific Cursor account (or organization seat) is automatically used based on the opened folder/workspace?

For example:

Project_A → always use Company A subscription
Project_B → always use Company B subscription

This would:

Prevent accidental usage under the wrong organization
Avoid constant sign-in/sign-out
Be much safer for developers working with multiple clients

Even something like a .cursor project-level setting that stores the preferred account/org would solve this.

Is this on the roadmap, or is there a recommended workflow for handling this scenario?

Operating System (if it applies)

MacOS

1 Like