workbench.glass.main.js · part 253

60 text occurrences from desktop/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js, part 253. Every entry preserves the shipped literal and its saved verdict or selection reason.

File contents and all parts · All files

Updates automation ${i}: ${s}.

Failed to ${t} automation.

Error: ${s.error}

Error: ${s.error}

Automation not found.

Error: ${o.error}

Error: Invalid automation payload: ${c}

Automation creation cancelled by user.

Failed to create automation: backend returned no workflow

Error: ${o.error}

Error: Invalid automation payload: ${c}

Automation update cancelled by user.

Failed to update automation: backend returned no workflow

Error: ${r.error}

Error: Failed to build automation prefill URL: ${o}

The cursor-backend-control MCP calls Cursor backend APIs through the current user's authenticated Cursor session.

Cursor Automations product tools:
- list_automations lists minimal, non-author-text Cursor Automation rows visible to the current user. Its query matches only fields returned by the tool, such as IDs and trigger/action types.
- get_automation fetches one Cursor Automation by ID with stored author text redacted and workflow values returned only as a redacted shape. Use it only after the user selected or provided the exact automation ID.
- create_automation creates a Cursor Automation from a reviewed CreateAutomationRequest-shaped payload.
- update_automation updates a Cursor Automation from a reviewed UpdateAutomationRequest-shaped payload.
- build_automation_prefill_url builds a cursor.com Automations prefill URL from a reviewed Cursor Automation workflow JSON. Returns the URL string for the caller to open via open_resource or surface to the user.

Rules:
- These tools are only for Cursor's Automations product. Do not use them for GitHub Actions, CI pipelines, scripts, cron jobs, workflow engines, browser automation, or other generic automation tasks unless the user explicitly asks for Cursor Automations or confirms Cursor Automations is the intended surface.
- Only call create_automation or update_automation after the user has reviewed the automation draft or requested the exact change.
- Do not invent an automation ID. If the user did not provide an ID, resolve it with list_automations, ask the user to choose from the returned IDs, and only then call get_automation when needed.
- These tools are unavailable in UNSPECIFIED and NO_STORAGE privacy modes because automations require reconciled storage eligibility.
- list_automations and get_automation require a fresh read confirmation before reading automation metadata; responses are redacted.
- create_automation and update_automation show a compact payload check generated from the serialized request in a final confirmation modal before saving.
- build_automation_prefill_url is read-only and side-effect free; it does not call the backend, but still requires storage-eligible privacy mode because prefill serializes the draft outside the no-storage boundary.

Automations are not available until privacy mode is reconciled to a storage-eligible setting.

[stored automation name redacted]

[stored automation description redacted]

[stored automation field redacted]

[stored automation workflow details redacted]

Cursor Automation Workflow proto JSON. Include reviewed triggers, actions, prompts, model, git, memory, and workflow options.

Optional search text matched only against returned Cursor Automations list fields, such as automation ID, trigger/action types, scope, enabled state, URL, and timestamps.

Optional numeric team id used to scope team-visible automations.

When true, disabled automations are included. Omitted or false returns only enabled automations.

Automation ID (UUID) of the Cursor Automation to fetch.

Display name for the Cursor Automation.

Optional short description shown in the Cursor Automations UI.

Optional AutomationScope proto JSON value. When omitted, team members get their team's default automation visibility (team-visible unless an admin configured otherwise) and solo users get user scope. Pass an explicit scope when the user asked for a specific visibility.

Optional template id when creating from a template-like draft.

Optional numeric team id for team-scoped creation.

Reviewed Cursor Automation Workflow proto JSON. Include triggers, actions, prompts, model, gitConfig, agentOptions, memoryEnabled, etc. The exact same shape passed to create_automation.workflow.

Optional display name carried into the prefilled Automations form.

Optional short description carried into the prefilled Automations form.

Optional template id; passed through to the Automations form when prefilling from a template-like draft.

Automation ID (UUID) of the Cursor Automation to update.

Optional new display name for the Cursor Automation.

Optional new description shown in the Cursor Automations UI.

Optional complete replacement workflow in UpdateAutomationRequest proto JSON form. This replaces the entire stored workflow; set replaceWorkflow to true only after the user reviewed the complete replacement.

Must be true when workflow is provided, acknowledging that workflow replaces the entire stored workflow instead of patching it.

Optional enabled state for the automation.

Optional AutomationScope proto JSON value.

List Cursor Automations product entries visible to the current user. Use only when the user explicitly asks about Cursor Automations. Returns compact summaries and only searches fields included in those summaries.

Listing automations

Listed automations

Couldn't list automations

Fetch one Cursor Automations product entry by automationId. Use only when the user explicitly asks about Cursor Automations. Stored author text is redacted and workflow values are returned only as a redacted shape before entering chat context.

Fetching automation

Fetched automation

Couldn't fetch automation

Create a Cursor Automation product entry with the current user's authenticated Cursor session. Use only when the user explicitly asks for Cursor Automations. Call only after the user has reviewed the automation draft. Saving shows a compact payload check generated from the serialized request.

Creating automation

Created automation

Couldn't create automation

Update a Cursor Automation product entry with the current user's authenticated Cursor session. Use only when the user explicitly asks for Cursor Automations. Non-workflow fields can be patched independently. Workflow updates require a complete replacement workflow plus replaceWorkflow: true after the user reviewed the full replacement. Saving shows a compact payload check generated from the serialized request.

Updating automation

Updated automation

Couldn't update automation

Build a cursor.com Automations prefill URL from a reviewed Cursor Automation workflow JSON. Use only when the user explicitly asks for Cursor Automations. Returns the URL as plain text; the caller is expected to open it via open_resource or surface it to the user. Read-only: does not call the backend or create any automation.

Building automation prefill URL