workbench.desktop.main.js · part 485

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

File contents and all parts · All files

To work in ${i}, keep this agent where it is and run commands with that directory as the working directory (for example `git -C ${i} status`).

If the user asked to add that repository to this agent's workspace, call move_agent_to_root with rootPaths: [${n.map(r=>JSON.stringify(r)).join(", ")}].

Move the current agent to a new root workspace directory, updating the visible work surface and the default cwd for new terminals. ${e?"ALWAYS call this immediately after creating or selecting a worktree that you intend to make changes in, before making any changes. Also use this whenever the conversation should continue from a different workspace root.":"Use this after creating a worktree or whenever the conversation should continue from a different workspace root."} If the destination was just produced by `cursorfs-clone` (under `~/.cursor/cursorfs-clone/...`), use `move_agent_to_cloned_root` instead — this generic tool runs `git fetch origin <branch>` against the destination and will fail with "Remote branch not found on origin" on local-only branches.

ALWAYS call this immediately after creating or selecting a worktree that you intend to make changes in, before making any changes. Also use this whenever the conversation should continue from a different workspace root.

Use this after creating a worktree or whenever the conversation should continue from a different workspace root.

Switching workspace root

Switched workspace root

Couldn't switch workspace root

Move the current agent to a root workspace directory that is a verbatim clone of the current workspace (for example produced by `cursorfs-clone`) and is already on the agent's recorded branch. Skips the migration-path `git fetch` and ff-merge that `move_agent_to_root` performs. Use ONLY when you already know the target is a sibling clone of the current workspace on the same branch; otherwise use `move_agent_to_root`.

Switching to cloned workspace

Switched to cloned workspace

Couldn't switch to cloned workspace

Creates the folder and runs `git init` outside the sandbox. Use this instead of shell `git init`, which the sandbox blocks. Ask the user where the repo should go if they did not say.

Created repository at ${e} and moved the agent root to it.

Created repository at ${e}.

Created repository at ${e}. If the user will work in the new repo, call move_agent_to_root with rootPath ${JSON.stringify(e)}.

Absolute path where the new repository should be created (e.g. "/Users/name/code/my-new-app")

Creating repository

Created repository

Couldn't create repository

URI to open in Glass or through the default opener (e.g. file:///path/to/file.ts#L10, vscode-terminal:/workspaceId/3, output:channel-id, https://example.com)

Open a resource by URI: files in the Glass editor panel (with line/column from URI fragment when applicable), terminals, output channels, or http(s) URLs through the default workbench opener. File URIs must be in the agent workspace or under the user ~/.cursor directory. Command and product-protocol URI schemes are not supported.

Opening resource

Opened resource

Couldn't open resource

Optional existing automation id to open in the Automations UI.

Which existing automation view to open. Defaults to edit. Requires automationId.

Optional automation template id to preselect in the new automation form.

Optional workflow data JSON object used to prefill the new automation form. The payload is sent only to the active Glass view and is not put in a URL or browser storage.

view requires automationId

automationId cannot be combined with templateId

automationId cannot be combined with prefillWorkflowData

Open the Glass Automations UI, optionally opening an existing automation by automationId or starting a new automation from a templateId and/or structured prefillWorkflowData. Use this instead of opening cursor.com automation URLs or putting raw prefill data in cursor:// URLs. Calls with prefillWorkflowData require tool approval before the data is trusted by the form, and prefill data is sent only to the active Glass view.

Opening automation

Opened automation

Couldn't open automation

Short name for the local scheduled task.

Standalone instructions for each scheduled run.

Five-field cron schedule, such as "0 9 * * 1-5".

Optional IANA time zone. Defaults to the user's local time zone.

Open the Local Tasks editor in Cursor's Agent Window with a reviewed task draft. This only prefills the form; the user must press Create Task before anything is saved.

Opening local task

Opened local task

Couldn't open local task

Marketplace plugin to install. Prefer the kebab-case slug when known; display names also resolve.

Ask the user to install a first-party Cursor marketplace plugin. Prefer the kebab-case slug when known; display names also resolve. Opens the install confirm tray and BLOCKS until the user confirms or cancels, so call it only when the plugin is actually needed to continue. Unknown or ambiguous names fail without showing anything. Never claim a plugin was installed unless this tool reports it.

Installing plugin

Installed plugin

Plugin not installed

Fetch a bounded JSON snapshot of the current Cursor user state for Cursor-specific workflows.

Reading Cursor state

Read Cursor state

Couldn't read Cursor state

Rule id must be non-empty

The personal rule id returned by a previous list or add operation.

Title must be at most 200 characters

Optional short title for the personal rule.

Rule content must be at most 20000 characters

The personal rule content to store.

The rule scope to operate on. Only "user" is currently supported.