main.js · part 36

60 text occurrences from desktop/Cursor.app/Contents/Resources/app/extensions/cursor-always-local/dist/main.js, part 36. Every entry preserves the shipped literal and its saved verdict or selection reason.

File contents and all parts · All files

The same admin policy read, returning an empty policy for users on no team instead of an error.

Extension hosts (agent host, MCP, agent exec) that read team policy through `vscode.cursor.getTeamAdminSettings()`.

Same as GetTeamAdminSettings; this variant lets extensions on personal accounts start without an error path.

One optional team id.

Reads the MCP server configuration stored with Cursor for the user or the team.

The MCP settings page and the MCP service, which merges team-managed servers with local `mcp.json`.

Team-managed MCP servers live in Cursor's control plane; without this read the editor cannot start them.

Whether to read the team's config instead of the user's.

The numeric id of the team the user has selected.

Whether the server should mask secret values in the returned config.

Two flags and a team id.

The response is the MCP configuration the customer stored with Cursor, as JSON. When `redact_secrets` is false it includes the stored values of MCP environment variables, which can be secrets. The editor's MCP service does not set `redact_secrets`.

Reads the merged user-plus-team MCP configuration with secrets masked.

Kept for the account and MCP settings surfaces that show the effective server list. No desktop editor code path issues it today.

Same control-plane read as GetMcpConfig with the server doing the merge and the masking; allowed so a settings surface that adopts it does not fail under lockdown.

The request message has no fields.

The response is the merged MCP configuration as JSON with secret values masked by the server.

Lists the plugins (skills, MCP servers, rules) installed for the user and pushed by the team, with their configured variables.

Plugin loading in the agent host and agent exec extensions at startup, and the plugin marketplace pages.

Team-installed plugins and their settings are stored with Cursor. The agent host needs them to start the MCP servers and skills the customer configured.

optional bool

Whether a read replica is acceptable (a freshness hint).

Whether to leave out decrypted plugin variables and inline plugin content. Configuration screens set it; the agent host leaves it unset.

Two flags and a team id.

The response returns each plugin's configured variables decrypted. Those are the MCP environment values the customer stored with Cursor — API keys and tokens for the customer's MCP servers — plus the inline content of plugins stored in Cursor's database. Nothing is sent up; secrets flow from Cursor to the editor, over TLS, so the plugins can run locally.

Returns the account's plan and billing period.

The plan badge and usage page in settings, and the `about` output of the CLI.

Plan type decides which usage limits and upgrade prompts apply; the editor cannot compute it locally.

The request message has no fields.

Returns usage for the current billing period.

The usage meter in settings and the warnings shown when a plan or spend limit is near.

Usage is metered by Cursor's billing system; the editor reads it back to show the user where they stand.

optional bool

Whether to compute the pooled (enterprise contract) reading instead of the per-user one.

One optional team id and one flag.

Returns whether usage-based (pay-as-you-go) requests are enabled for the team.

The usage settings toggle and the error actions offered when a request is refused for quota.

The setting is stored with billing; the editor reads it to explain a quota refusal and offer the right action.

The numeric id of the team the user has selected.

A single team id.

Returns the monthly spend limit the user or admin has set.

The spend-limit field on the usage page and the message shown when a request is stopped by the limit.

The limit is enforced by billing; the editor reads it to show the value and the remaining headroom.

One optional team id.

Returns the start and end of the current monthly billing cycle.

The Personal Usage section of settings for members of an enterprise team; the cycle bounds the usage totals and the daily-spend chart.

The cycle is anchored to the team's contract dates or the user's membership start, which only Cursor's billing system knows; the editor cannot derive it from the calendar.

One optional team id.

Returns usage totals for a billing period: tokens and cost per model, and whether the plan is request-based.

The Personal Usage section of settings for members of an enterprise team; the totals decide whether the chart shows all spend or on-demand spend only.

Usage is metered by Cursor's billing system; the editor reads the aggregate back to show the user where they stand.

The numeric id of the team the user has selected.

optional int64

Start of the billing period as epoch milliseconds, copied from the GetMonthlyBillingCycle response.

optional int64

End of the billing period as epoch milliseconds, copied from the GetMonthlyBillingCycle response.

optional int32

The numeric id of the signed-in user, so the totals are the user's own rather than the team's.

Two numeric ids and two timestamps.

Returns spend per day over a billing period, grouped by model, plus the effective spend limit.